Tried out PATA to no success- hangs on fsck

toofishes · 2006-12-11 06:31:34

This is a pretty big post but I want to get anything relevant included. We'll start with the problem, and then the files.
I've upgraded to 2.16.19 with no problems, boots fine using the IDE hook in mkinitcpio.conf. However, if I build another image substituting the PATA hook, I begin to have problems. The boot process is all good though the initial ramdisk, and if I tack a 'break=y' line onto the kernel in grub, I can stop at the dash shell there and check out the devices. It hangs when fsck runs- it correctly checks the 'hdroot' device, but shows nothing for 'hdboot'.

For IDE at the dash shell, all relevant disks are present in /dev/disk/by-label. There are also entries in /dev for hda and its respective partitions, 1-6.
For PATA at the dash shell, all relevant disks are present in /dev/disk/by-label. There are entries in /dev for sda and its respective partitions, 1-6. This is obviously the same disk as the IDE hda.

Here is the relevant part of fstab:

LABEL=hdroot       /          ext3     defaults,noatime             0      1
LABEL=hdboot       /boot      ext2     defaults                     0      2
LABEL=swapspace    swap       swap     defaults                     0      0

Grub menu.lst (for PATA, i simply change the initrd to kernel26-pata.img):

title  Arch Linux
root   (hd0,2)
kernel /vmlinuz26 root=/dev/disk/by-label/hdroot ro vga=773
initrd /kernel26.img

kernel26.preset:

########################################
# DO NEVER EDIT THIS LINE:
source /etc/mkinitcpio.d/kernel26.kver
########################################

PRESETS=('default' 'fallback' 'pata')

default_config="/etc/mkinitcpio.conf"
default_image="/boot/kernel26.img"

fallback_config="/etc/mkinitcpio.d/kernel26-fallback.conf"
fallback_image="/boot/kernel26-fallback.img" 

pata_config="/etc/mkinitcpio.d/kernel26-pata.conf"
pata_image="/boot/kernel26-pata.img"

Respective lines from mkinitcpio.conf and kernel26-pata.conf:

HOOKS="base udev autodetect ide filesystems"
HOOKS="base udev autodetect pata filesystems"

And finally, the output of 'mkinitcpio -v -p kernel26' for the pata image:

==> Building image "pata"
==> Running command: /sbin/mkinitcpio -v -k 2.6.19-ARCH -c /etc/mkinitcpio.d/kernel26-pata.conf -g /boot/kernel26-pata.img
:: Begin build
:: Parsing hook [base]
  adding  dir /proc
  adding  dir /sys
  adding  dir /dev
  adding node /dev/null
  adding node /dev/zero
  adding node /dev/console
  adding  dir /lib
  adding file /lib/klibc-C2z_DMnqPyftZCYmjdWTcAM2woc.so
  adding  dir /bin
  adding file /bin/cat
  adding file /bin/chroot
  adding file /bin/dd
  adding file /bin/false
  adding file /bin/fstype
  adding file /bin/gunzip
  adding file /bin/gzip
  adding file /bin/halt
  adding file /bin/insmod
  adding file /bin/ipconfig
  adding file /bin/kill
  adding file /bin/kinit
  adding file /bin/kinit.shared
  adding file /bin/ln
  adding file /bin/losetup
  adding file /bin/mdassemble
  adding file /bin/minips
  adding file /bin/mkdir
  adding file /bin/mkfifo
  adding file /bin/mknod
  adding file /bin/moddeps
  adding file /bin/modprobe
  adding file /bin/mount
  adding file /bin/nfsmount
  adding file /bin/nuke
  adding file /bin/parseblock
  adding file /bin/pivot_root
  adding file /bin/poweroff
  adding file /bin/readlink
  adding file /bin/reboot
  adding file /bin/replace
  adding file /bin/resume
  adding file /bin/run-init
  adding file /bin/sh
  adding file /bin/sleep
  adding file /bin/true
  adding file /bin/umount
  adding file /bin/uname
  adding file /bin/zcat
  adding file /init
  adding file /config
:: Parsing hook [udev]
  adding  dir /sbin
  adding file /sbin/udevd
  adding file /sbin/udevtrigger
  adding file /sbin/udevsettle
  adding  dir /etc
  adding  dir /etc/udev
  adding  dir /etc/udev/rules.d
  adding file /etc/udev/rules.d/udev.rules
  adding file /etc/start_udev
  adding  dir /lib/udev
  adding file /lib/udev/firmware.sh
  adding file /lib/udev/cdrom_id
  adding file /lib/udev/ata_id
  adding file /lib/udev/dasd_id
  adding file /lib/udev/usb_id
  adding file /lib/udev/edd_id
  adding file /lib/udev/scsi_id
  adding file /lib/udev/vol_id
  adding file /lib/udev/load-modules.sh
  adding file /etc/udev/udev.conf
  adding  dir /hooks
  adding file /hooks/udev
:: Parsing hook [autodetect]
:: Parsing hook [pata]
  adding  dir /lib/modules
  adding  dir /lib/modules/2.6.19-ARCH
  adding  dir /lib/modules/2.6.19-ARCH/kernel
  adding  dir /lib/modules/2.6.19-ARCH/kernel/drivers
  adding  dir /lib/modules/2.6.19-ARCH/kernel/drivers/ata
  adding file /lib/modules/2.6.19-ARCH/kernel/drivers/ata/libata.ko
  adding file /lib/modules/2.6.19-ARCH/kernel/drivers/ata/pata_sis.ko
  adding file /lib/modules/2.6.19-ARCH/kernel/drivers/ata/ata_generic.ko
  adding  dir /lib/modules/2.6.19-ARCH/kernel/drivers/scsi
  adding file /lib/modules/2.6.19-ARCH/kernel/drivers/scsi/sd_mod.ko
  adding  dir /lib/modules/2.6.19-ARCH/kernel/drivers/cdrom
  adding file /lib/modules/2.6.19-ARCH/kernel/drivers/cdrom/cdrom.ko
  adding file /lib/modules/2.6.19-ARCH/kernel/drivers/scsi/sr_mod.ko
:: Parsing hook [filesystems]
  adding  dir /lib/modules/2.6.19-ARCH/kernel/fs
  adding file /lib/modules/2.6.19-ARCH/kernel/fs/mbcache.ko
  adding  dir /lib/modules/2.6.19-ARCH/kernel/fs/ext2
  adding file /lib/modules/2.6.19-ARCH/kernel/fs/ext2/ext2.ko
  adding  dir /lib/modules/2.6.19-ARCH/kernel/fs/jbd
  adding file /lib/modules/2.6.19-ARCH/kernel/fs/jbd/jbd.ko
  adding  dir /lib/modules/2.6.19-ARCH/kernel/fs/ext3
  adding file /lib/modules/2.6.19-ARCH/kernel/fs/ext3/ext3.ko
  adding file /hooks/filesystems
:: Generating module dependencies
  adding file /lib/modules/2.6.19-ARCH/modules.dep
  adding file /lib/modules/2.6.19-ARCH/modules.alias
  adding file /lib/modules/2.6.19-ARCH/modules.symbols
:: Generating image '/boot/kernel26-pata.img'...SUCCESS

brain0 · 2006-12-11 10:44:02

So you are saying it just stops when hdboot has been checked and doesn't continue booting? Are there any further messages that might be of relevance?

Right now I can only say this: You could't have done it better (adding a separate image for testing is the way to go) and I see no problem with the image itself. Also using label based naming is a cool thing. I don't know how the LABEL= thing works, therefore I use /dev/disk/by-label in my fstab as well (maybe that makes a difference).
But pata support is experimental, and although pata_sis works perfectly for me, it may be broken on your controller.

toofishes · 2006-12-11 15:27:59

Yeah, it is interesting that it just hangs and does nothing. I think I forgot to write that it first correctly checks hdroot, and then moves (or I know it should be next) onto hdboot, where there are no messages at all. I can't really think of anything else relevant. As you could see above, both partitions are on the same drive. The messages at startup before init begins indicate that my two hard drives and two optical drives have been detected, so I don't know that the kernel driver is the problem.

I like how the 'LABEL=' syntax is a bit shorter, so thats why I use it. It works for booting IDE, I guess I could give it a try when I have some time to kill and see if /dev/disk/by-label/ entries in my fstab would change anything.

toofishes · 2006-12-13 23:14:01

I think I'll hold off on switching to PATA until it matures a bit more. I tried changing my fstab entries to /dev/disk/by-label/ paths, and that didn't change a thing. Still no obvious error messages, it just hangs on the second fsck.

brain0 · 2006-12-13 23:51:42

If you still want to try, then change /etc/rc.sysinit: There is a line with "dmesg -n 3" in it, change this to a higher value (maybe 9). This way you will get the kernel messages printed to the console. Maybe there will be an error message then.

It may also be a good idea to try again when 2.6.20 comes out.

toofishes · 2006-12-14 03:54:41

I tried again with dmesg -n 9, and after letting it sit long enough, it did boot. Here is the dmesg output after it booted: http://pastebin.archlinux.org/405

You'll notice some exceptions down there, it looks like it errors 4 times before it continues the boot process. Once booted, it is also weird that two drives that are not in my fstab get mounted (and don't normally mount when using IDE)...I don't know if that is due to some udev rules or something, but that is a separate issue.

brain0 · 2006-12-14 18:54:21

Looks quite buggy to me, so stick with IDE for now. But thanks for the dmesg.

Arch Linux

#1 2006-12-11 06:31:34

Tried out PATA to no success- hangs on fsck

#2 2006-12-11 10:44:02

Re: Tried out PATA to no success- hangs on fsck

#3 2006-12-11 15:27:59

Re: Tried out PATA to no success- hangs on fsck

#4 2006-12-13 23:14:01

Re: Tried out PATA to no success- hangs on fsck

#5 2006-12-13 23:51:42

Re: Tried out PATA to no success- hangs on fsck

#6 2006-12-14 03:54:41

Re: Tried out PATA to no success- hangs on fsck

#7 2006-12-14 18:54:21

Re: Tried out PATA to no success- hangs on fsck

Board footer