[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Help: NO longer boots ;<



On 11/11/06 08:29:02PM -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>
> 

First see if anything is in /root, it looks like it's attempts to mount the
root filesystem there so if something is there it'll tell you if it just
mounted the wrong filesystem or if there's a real problem with your root
filesystem. If there's nothing at all there just run 'mount' and see if it
thinks something is mounted there, if not look in /dev/mapper and see if
there's a LVM volume for your root, considering that your swap is called
VG1-swap it'll probably be VG1-root or VG2-root. If it's there try mounting
it, although I'm not totally sure all of what capabilities you'll have in
the initramfs.

It might also be a good idea to look around for a Knoppix, Ubuntu LiveCD,
etc so that you can have more tools handy in case there is a real problem
with your disks.

Jim.



Reply to: