Hello -- I have recently lost quite a bit of electronics around the house to a power surge/lightning strike (all items were on APC backups). The drives from my server were undamaged and I have a new server to host them in.
I am having a hard time getting the new server to boot up with the old drives (trying to avoid a fresh install/rebuild of server). The hardware is very similar but not identical. At this point it gets to the following during the boot process:
[code]
Scanning and configuring dmraid support devices
md: Autodetecting RAID arrays
MD: autorun ...
MD: ... autorun DONE.
MD: Autodetecting RAID arrays.
MD autorun ...
md: ... autorun Done.
Trying to resume from /dev/md2
Creating root device.
Mounting root filesystem.
EXT3-fs: unable to read superbock
mount: error mounting /dev/root on /sysroot as ext3: Invalid argument
Setting up other filesystems.
Setting up new root fs
setuproot: moving /dev failed: No such file or directory
no fstab.sys, mounting internal defaults
setuproot: error mounting /proc: No such file or directory
setuproot: error mounting /sys: No such file or directory
Switching to new root and running init.
unmounting old /dev
unmounting old /proc
unmounting old /sys
switchroot: mount failed: No such file or directory
Kernel panic - not syncing: Attempted to kill init!
[/code]
I'd really appreciate any help in making this transition successful.
Thanks!!!
Help moving drives to new hardware
Help moving drives to new hardware
The error is there:
[code]Mounting root filesystem.
EXT3-fs: unable to read superbock[/code]
Either the device names have changed, and 'init' within initrd-*.img uses
wrong names, or filesystem has suffered corruption. Those are my first
guesses.
Boot from CD/USB to rescue mode. That's what I would try first to see
what I have.
[code]Mounting root filesystem.
EXT3-fs: unable to read superbock[/code]
Either the device names have changed, and 'init' within initrd-*.img uses
wrong names, or filesystem has suffered corruption. Those are my first
guesses.
Boot from CD/USB to rescue mode. That's what I would try first to see
what I have.
Re: Help moving drives to new hardware
The main problem I have when moving disks from one server to another at work is the SATA controller.. So I figure out what module I need (ahci) and add it to the current list (ata_piix), then rebuild initrd:
/etc/modprobe.conf
[code]alias scsi_hostadapter ata_piix
alias scsi_hostadapter1 ahci[/code]
[quote][root@host ~]# mkinitrd /boot/initrd-`uname -r`.img `uname -r`[/quote]
If this is the problem you're having and the old system isn't working anymore you'll probably need to boot up a rescue cd, mount/chroot the fs on the disk(s), update etc/modprobe.conf, rebuild initrd, then reboot. If you're not sure what module is needed you can look at the output of [i]lsmod[/i] when up on the rescue cd.
/etc/modprobe.conf
[code]alias scsi_hostadapter ata_piix
alias scsi_hostadapter1 ahci[/code]
[quote][root@host ~]# mkinitrd /boot/initrd-`uname -r`.img `uname -r`[/quote]
If this is the problem you're having and the old system isn't working anymore you'll probably need to boot up a rescue cd, mount/chroot the fs on the disk(s), update etc/modprobe.conf, rebuild initrd, then reboot. If you're not sure what module is needed you can look at the output of [i]lsmod[/i] when up on the rescue cd.