These are long shots, but since nobody else answered: If the reboot after the power failure was the first reboot since upgrading a package like udev or installing a new kernel, it could be that your grub or lilo stanza is wrong, especially if you have more than one hard drive. It could also be an incorrect /etc/fstab. You can experiment with changing a grub stanza by using the 'e' option. You can check /etc/fstab using a rescue disk.
It could be that /dev/.static/dev was deleted because of a file system error due to the unclean shut down or a faulty hard drive. Good luck! Win On Mon, Nov 13, 2006 at 10:13:20AM -0600, helices wrote: > I have a dual Opteron box (Odin) that went down while I was gone, due to > an extended power failure. > > When it comes up, it fails to complete boot. Please, help me get this > system running again. > > uname -a > Linux (none) 2.6.17-2-amd64 #1 SMP ... > > Bootup sequence from obvious problems: > > ... > Success: loaded module raid10. > Done. > device-mapper: 4.6.0-ioctl (2006-02-17) initialised: ... > 1 logical volume(s) in volume group "VG2" now active > 7 logical volume(s) in volume group "VG1" now active > Done. > stdin: error 0 > Begin: Running /scripts/local-premount ... > kinit: name_to_dev_t(/dev/mapper/VG1-swap) = dm-3(253,3) > kinit: trying to resume from /dev/mapper/VG1-swap > Attempting manual resume > kinit: No resume image, doing normal boot ... > Done. > Usage: modprobe ... > ... > > Begin: running /scripts/init-bottom ... > mount: Mounting /root/dev on /dev/.static/dev failed: No such file or > directory > Done. > mount: Mounting /sys on /root/sys failed: ... > mount: Mounting /proc on /root/proc failed: ... > Target filesystem doesn't have /sbin/init > ... > > (initramfs)_ <blinking cursor> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
