/hda to /sda

dodgydodgy · 10-19-2006, 12:57 PM

Hi,

I'm trying to move my linux server to a new machine, this machine only supports SATA drives rather than the PATA of my old machine.

I've cloned the disk image to the new SATA drive, but when I boot Fedora FC5 I get the following error and then a kernel panic:

Trying to resume from /dev/hda3
Unable to access resume device (/dev/hda3)

I've edited grub.conf and fstab (and did a grub-install /dev/sda), but I still have the error. I can get into the partition using the rescue CD to perform edits.

Would anyone be kind enough to point me in the direction of what I need to do to fix this?

uselpa · 10-19-2006, 01:01 PM

You must have missed something in grub.conf or menu.lst. It's probably a parameter of the kernel, look for "resume=/dev/hda3".

dodgydodgy · 10-19-2006, 01:11 PM

Hi,

I did a cat /boot/grub/* |grep rescue with no result, also the same with hda - nothing.

uselpa · 10-19-2006, 01:18 PM

try "grep -R resume /boot" or "grep -R hda /boot"

dodgydodgy · 10-19-2006, 01:27 PM

It reported nothing of any significance for 'resume' and nothing at all for 'hda'.

This is driving me crazy!

dodgydodgy · 10-19-2006, 01:36 PM

If it helps:

fdisk -l

Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225290 bytes

Device Boot Start End Blocks id System
/dev/sda1 * 1 13 104391 83 Linux
/dev/sda2 14 30393 244027350 83 Linux
/dev/sda3 30394 30515 979965 82 Linux swap / Solaris

more /boot/grub/device.map
(fd0) /dev/fd0
(hd0) /dev/sda

more /boot/grub/grub.conf

# grub.conf generated by anaconda
# ...
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/sda2
#boot=/dev/sda
default=0
timeout=10
splashimage=(hd0,0)/grub/splash.xpm.gz
title Fedora Core (2.6.17-1.2187_FC5)
root (hd0,0)
kernel /vmlinuz-2.6.17-1.2187_FC5 ro root=LABEL=/ rhgb
initrd /initrd-2.6.17-1.2187_FC5.img

dodgydodgy · 10-19-2006, 01:47 PM

This is the result of the boot:

Code:

Mounting sysfs filesystem
Creating /dev
Creating initial device nodes
Setting up hotplug
Creating block device nodes.
Loading jdb.ko module
Loading ext3.ko module
Trying to resume from /dev/hda3
Unable to access resume device (/dev/hda3)
Creating root device
Mounting root filesystem
mount: could not find filesystem '/dev/root/'
Setting up other filesystems
Setting up new root fs
setuproot: moving /dev failed: No such file or direcroty
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!

dodgydodgy · 10-19-2006, 01:57 PM

fstab:

Code:

LABEL=/              /              ext3         defaults        1 1
LABEL=/boot          /boot          ext3         defaults        1 2
none                 /dev/pts       devpts       gid=5,mode=620  0 0
none                 /proc          proc         defaults        0 0
none                 /dev/shm       tmpfs        defaults        0 0
/dev/sda3            swap           swap         defaults        0 0

dodgydodgy · 10-19-2006, 02:45 PM

Okay, in the end I used the FC5 DVD and did an 'upgrade' overwriting the boot records. As far as I can see it didn't change a thing in the files, but it worked.

Shade · 10-20-2006, 06:07 PM

Fedora uses the partition/Filesystem label with Grub to dictate which partition is which FS (/,/boot, etc). Likely, these didn't transfer with your image move.

You'll notice that the device column in your fstab uses labels, rather than device names to specify what is what (except the swap partition). Booting with a live CD and changing those to the actual device names would probably have solved this issue for you

-- Shade