You are not logged in.
I have two SATA II drives and two IDE drives (one HDD and one optical) in my box. I had Arch installed on first SATA II drive (/dev/sda). I changed the mkinitcpio files to load sata modules before pata, and that works okay. So, my IDE HDD is now /dev/sdc
However, I installed a second Arch onto the /dev/sdc (IDE) and it won't boot. It goes through booting process and hangs at checking the drives claiming that the /dev/sda3 has bad superblock. Now, this is really odd, because /dev/sda3 is a SWAP partition, and the init script is trying to run e2fsck on it.
How do I fix this? Should I simply (somehow) disable the filesystem check?
(Before you ask, I need the second Arch to build a LiveCD.)
Offline
Maybe the filesystem id is not correct. Look with cfdisk how it's identified. If it's wrong, change it.
Offline
It's correctly identified as Linux Swap partition. Besides, the first Arch install is still working with that swap partition reporting no problems at boot time.
Here's the output of fdisk -l:
Disk /dev/sda: 160.0 GB, 160040803840 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x4a424a41
Device Boot Start End Blocks Id System
/dev/sda1 * 1 3824 30716248+ 7 HPFS/NTFS
/dev/sda2 3825 7654 30764475 83 Linux
/dev/sda3 7655 7903 2000092+ 82 Linux swap / Solaris
/dev/sda4 7904 13982 48829567+ 5 Extended
/dev/sda5 7904 13982 48829536 83 Linux
Disk /dev/sdb: 400.0 GB, 400088457216 bytes
255 heads, 63 sectors/track, 48641 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x4fa7b7a5
Device Boot Start End Blocks Id System
/dev/sdb1 1 48641 390708801 42 SFS
Disk /dev/sdc: 81.9 GB, 81964302336 bytes
255 heads, 63 sectors/track, 9964 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xec0c2373
Device Boot Start End Blocks Id System
/dev/sdc1 * 1 5 40162 83 Linux
/dev/sdc2 6 136 1052257+ 82 Linux swap / Solaris
/dev/sdc3 137 1666 12289725 83 Linux
/dev/sdc4 1667 9964 66653685 83 Linux
And just in case, the menu.lst used to boot both Arches:
# (0) Arch Linux
title Arch Linux
root (hd0,1)
kernel /boot/vmlinuz26 root=/dev/sda2 ro vga=791
initrd /boot/kernel26.img
# (1) Arch Linux
title Arch Linux Fallback
root (hd0,1)
kernel /boot/vmlinuz26 root=/dev/sda2 ro
initrd /boot/kernel26-fallback.img
# (1) Windows
title Windows XP
rootnoverify (hd0,0)
makeactive
chainloader +1
# (2) Arch Linux
title ArchGem
root (hd1,0)
kernel /vmlinuz26 root=/dev/sdc3 ro vga=791
initrd /kernel26.img
# (3) Arch Linux
title ArchGem Fallback
root (hd1,0)
kernel /vmlinuz26 root=/dev/sdc3 ro
Offline
Have you considered using uuid-assignments instead? This solved a random swapping of diskorder for me since I apparently had 2 diffrent sata controllers on my board. It would atleast eliminate one potential source of trouble.
http://wiki.archlinux.org/index.php/Per … ice_naming
Offline