Re: rescue bootable cd ???
On 10/02/07 03:43:56PM -0400, Douglas A. Tutty wrote: > On Tue, Oct 02, 2007 at 07:08:11AM -0500, helices wrote: > > > Unfortunately, both systems on which I experienced such calamity ran lvm > > over software raid 5. In fact, both systems ran lilo, not grub; and > > everything was under lvm, including root and boot. Under these > > circumstances, there is specific configuration information missing, and > > that prevents the debian install cd, and knoppix, from being able to > > read my disks ;< > > I thought that grub's support of LVM and any raid other than raid1 > wasn't either supported or ready for prime-time? > AFAIK there will never be any real RAID or LVM support in GRUB, it only sort of supports RAID1 because both volumes have the full filesystem on them. Jim. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
cheap sluts
best wh0res list www spellonme dot com sutures goloshes eastern diverticulate demultiplex oxozonide target thromboses -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: rescue bootable cd ???
I suppose is possible to make an USB-flash bootable eable to assemble the raid/lvm in boot time ready to repair the faulty system, is n't it? the floppy equivalent just to bring up the old system, or work with it in a chroot... On 10/2/07, Lennart Sorensen <[EMAIL PROTECTED]> wrote: > On Tue, Oct 02, 2007 at 07:08:11AM -0500, helices wrote: > > Unfortunately, both systems on which I experienced such calamity ran lvm > > over software raid 5. In fact, both systems ran lilo, not grub; and > > everything was under lvm, including root and boot. Under these > > circumstances, there is specific configuration information missing, and > > that prevents the debian install cd, and knoppix, from being able to > > read my disks ;< > > > > When I started this thread, I was thinking about the olden days, when I > > (tried to remember to) ma[dk]e a boot floppy after each new kernel ;> > > Of course in those days you didn't run software raid5 and lvm either, so > perhaps that is why those boot disks worked in the first place. > > Nothing prevents you from assembling a raid using mdadm and scanning for > lvm volumes and bringing those up from a knoppix dvd. I have done it > and it can be done. Try not to screw up badly enough to need it, since > it is a bit of a pain. :) > > Just don't touch mdadm --create and you should be safe. You just want > to assemble the raid, and then find the PVs, bring up the VG and then > activate the volumes and mount the LVs. > > -- > Len Sorensen > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > -- Perhaps the depth of love can be calibrated by the number of different selves that are actively involved in a given relationship. Carl Sagan (Contact) Jaime Ochoa Malagón Integrated Technology Tel: (55) 52 54 26 10
armful westinghouse westinghouse;
As a business you have been preapproved to receive 46474 USD TODAY! No hassle at all, completely unsecured. There are no hidden costs or fees. Worried that your credit is less than perfect? Not an issue. Give us a ring, now.. 8772926894 Turn your dream into a reality. 8772926894 Once she was off 9, the way into the hills was by little-travelled meadow-line roads, many fallen into casual disuse as grazing cattle this high up became a rarity. Geoffrey went back inside, already forgetting the doctors odd remark, already chalking Shinnys equally odd behavior off to age, weariless, and his own sort of grief. Rene Crowell -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: rescue bootable cd ???
On Tue, Oct 02, 2007 at 02:31:19PM -0500, C M Reinehr wrote: > > Unfortunately, both systems on which I experienced such calamity ran lvm > > over software raid 5. In fact, both systems ran lilo, not grub; and [snip] > You may still be able to access your hard disks with Knoppix. After booting > Knoppix you first must load the md driver & raid drivers: `modprobe raid5` > should do it. Then, use the mdadm command to query the raid information > written to the hard drives, i.e., `mdadm --detail /dev/sdx`. Once you think > you have the right configuration start your raid array with > `mdadm -A /dev/mdx /dev/sdy ...`. Finally, once your raid array is up & > running you can bring up lvm. Knoppix comes with a script called mdrun (IIRC), the only thing it doesn't do is modprobe the various raidX modules. So: $ modprobe raid5 $ mdrun is all you need to do to get raid5 to run on knoppix. Like you said lvm is simple to jumpstart (I guess there is a script fo this as well). The only thing knoppix failed to do for my raid5/lvm system was to restore grub, it segfaulted but a chroot to the systems root disk was enough to fix. -- When you do things right, people won't be sure you've done anything at all. Daniel Tryba -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: apt-get autoremove
Hans-J. Ullrich([EMAIL PROTECTED]) is reported to have said:
> Hi all,
> since when does the option "autoremove" exist in apt-.get ?
> I found nothing about it in the changelogs. Did I miss something ?
>
> Is "apt-get autoremove" intend to replace "orphaner" ?
>
dpkg -l apt
ii apt 0.7.6
man apt-get
APT-GET(8)
<>
SYNOPSIS
apt-get [-hvs] [-o=config string] [-c=file] {[update] |
[upgrade] | [dselect-upgrade] | [install pkg...] | [remove
pkg...] | [purge pkg...] | 17:46:34
[source pkg...] | [build-dep pkg...] | [check] |
[clean] | [autoclean] | [autoremove]}
^^^
Tschess
WT
--
A computer's attention span is as long as its power cord.
___
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: rescue bootable cd ???
On Tue, Oct 02, 2007 at 07:08:11AM -0500, helices wrote: > Unfortunately, both systems on which I experienced such calamity ran lvm > over software raid 5. In fact, both systems ran lilo, not grub; and > everything was under lvm, including root and boot. Under these > circumstances, there is specific configuration information missing, and > that prevents the debian install cd, and knoppix, from being able to > read my disks ;< > > When I started this thread, I was thinking about the olden days, when I > (tried to remember to) ma[dk]e a boot floppy after each new kernel ;> Of course in those days you didn't run software raid5 and lvm either, so perhaps that is why those boot disks worked in the first place. Nothing prevents you from assembling a raid using mdadm and scanning for lvm volumes and bringing those up from a knoppix dvd. I have done it and it can be done. Try not to screw up badly enough to need it, since it is a bit of a pain. :) Just don't touch mdadm --create and you should be safe. You just want to assemble the raid, and then find the PVs, bring up the VG and then activate the volumes and mount the LVs. -- Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
apt-get autoremove
Hi all, since when does the option "autoremove" exist in apt-.get ? I found nothing about it in the changelogs. Did I miss something ? Is "apt-get autoremove" intend to replace "orphaner" ? Greetings Hans -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: rescue bootable cd ???
On Tue, Oct 02, 2007 at 07:08:11AM -0500, helices wrote: > Unfortunately, both systems on which I experienced such calamity ran lvm > over software raid 5. In fact, both systems ran lilo, not grub; and > everything was under lvm, including root and boot. Under these > circumstances, there is specific configuration information missing, and > that prevents the debian install cd, and knoppix, from being able to > read my disks ;< I thought that grub's support of LVM and any raid other than raid1 wasn't either supported or ready for prime-time? > > When I started this thread, I was thinking about the olden days, when I > (tried to remember to) ma[dk]e a boot floppy after each new kernel ;> Bootfloppies aren't an option due to the size of the kernel and ramdisks. Here's my suggestion: I hope you have good backups: reinstall, raid1 partition for /boot or if your drives are big enough anyway, just a 400 or 500 MB / on raid1. Put the same partition at the beginning of each of your drives and put them all into the raid1 array. That way, no single drive failure can cause failure of your /boot or / If you must use raid5 for the rest, OK, but since drives are cheap, I'd suggest raid1. Use LVM overtop of this second raid array, one LV for each of the standard partitions (/usr, /home/, /var, possibly /tmp [or use tmpfs for /tmp]). Use Grub. Install grub in the MBR of all drives. Manually put an entry in grub that looks to each drive in the raid1 array (with co-responding root= kernel option if / is on raid1 instead of LVM). In this way, any single drive failure will still allow a full boot. If you need the performance of raid0 across a raid1 (non /boot, preferably non / too), e.g. for /var or /home, make new LVs after install that do striping. Good luck, Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: rescue bootable cd ???
On Tuesday 02 October 2007 07:08, helices wrote: > * "Gudjon I. Gudjonsson" <[EMAIL PROTECTED]> [2007:10:02:05:20:25+0200] scribed: > > Hi > >It is also possible to use the install disk. You just stop after > > detecting the hard disk (don't reformat it :) Then you do: > > #mkdir /mnt > > #mount /dev/sda1 /mnt > > #chroot /mnt > > and then you can do whatever you need to fix your system. > > > > Hope it helps > > Gudjon > > Unfortunately, both systems on which I experienced such calamity ran lvm > over software raid 5. In fact, both systems ran lilo, not grub; and > everything was under lvm, including root and boot. Under these > circumstances, there is specific configuration information missing, and > that prevents the debian install cd, and knoppix, from being able to > read my disks ;< > > When I started this thread, I was thinking about the olden days, when I > (tried to remember to) ma[dk]e a boot floppy after each new kernel ;> > > Any other ideas? You may still be able to access your hard disks with Knoppix. After booting Knoppix you first must load the md driver & raid drivers: `modprobe raid5` should do it. Then, use the mdadm command to query the raid information written to the hard drives, i.e., `mdadm --detail /dev/sdx`. Once you think you have the right configuration start your raid array with `mdadm -A /dev/mdx /dev/sdy ...`. Finally, once your raid array is up & running you can bring up lvm. Again, learn your configuration with pvdisplay, vgdisplay & lvdisplay. Then, make your logical volumes active with `lvchange -ay vgx/lvx ...` Once your logical volumes are active you can mount them, i.e., `mount -t ext3 /dev/vg0/lv_root /mnt`. Of course, use whatever details are appropriate for your system. Good luck! cmr -- Debian 'Etch' - Registered Linux User #241964 "More laws, less justice." -- Marcus Tullius Ciceroca, 42 BC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: rescue bootable cd ???
* "Gudjon I. Gudjonsson" <[EMAIL PROTECTED]> [2007:10:02:05:20:25+0200] scribed: > Hi >It is also possible to use the install disk. You just stop after > detecting the hard disk (don't reformat it :) Then you do: > #mkdir /mnt > #mount /dev/sda1 /mnt > #chroot /mnt > and then you can do whatever you need to fix your system. > > Hope it helps > Gudjon Unfortunately, both systems on which I experienced such calamity ran lvm over software raid 5. In fact, both systems ran lilo, not grub; and everything was under lvm, including root and boot. Under these circumstances, there is specific configuration information missing, and that prevents the debian install cd, and knoppix, from being able to read my disks ;< When I started this thread, I was thinking about the olden days, when I (tried to remember to) ma[dk]e a boot floppy after each new kernel ;> Any other ideas? -- Best Regards, helices - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- signature.asc Description: Digital signature
Re: rescue bootable cd ???
On Monday 01 October 2007 23:13, Jim Crilly wrote: > On 10/01/07 05:15:27PM -0500, C M Reinehr wrote: > > I've seen the term before but don't understand exactly what COW means, > > but I think I know what you're talking about. I had a failing disk drive > > last Friday and had to boot my system off of a Knoppix disk to see what I > > could salvage from my raid-1 array. Knoppix didn't seem to include the > > smartmontools package but I was able to use apt-get to install it on the > > fly and use it to diagnose which disk was failing. > > COW stands for copy on write, whenever a change is made to a block (or > file maybe, I don't know what granularity unionfs uses) that block is > copied somewhere else and the original left in place so that the update > can succeed and the original still exists. Sort of like an LVM snapshot > only instead of being backed by a LVM volume the changes are only stored in > memory. > > But yea, the short answer is that it allows you to make changes and install > software on read-only medium like CDs. =) > > Jim. Thanks, Jim! :-) -- Debian 'Etch' - Registered Linux User #241964 "More laws, less justice." -- Marcus Tullius Ciceroca, 42 BC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
