https://bugzilla.novell.com/show_bug.cgi?id=760859 https://bugzilla.novell.com/show_bug.cgi?id=760859#c7 --- Comment #7 from Volker Kuhlmann <volker3204@paradise.net.nz> 2012-06-27 20:04:15 NZST --- Thanks Neil! If you have an mdadm fixing the second problem I'll be happy to test. Re first problem: [0:0:0:0] disk ATA SAMSUNG HD103UJ 1AA0 /dev/sda [4:0:0:0] disk Generic IC1210 CF 1.9C /dev/sdb [4:0:0:1] disk Generic IC1210 MS 1.9C /dev/sdc [4:0:0:2] disk Generic IC1210 MMC/SD 1.9C /dev/sdd [4:0:0:3] disk Generic IC1210 SM 1.9C /dev/sde [5:0:0:0] disk ATA ST3120026A 3.06 /dev/sdf sda reliably remains to be the Samsung. The Seagate PATA randomly gets inserted as sdb (before) or sdf (after the card reader drives). The card reader is internal; USB connected. My uneducated guess for the delay of sd[bf] is that the kernel has pushed initialisation of PATA right to the end, after SATA and USB. Combined with systemd there's not much telling of timing... I don't see any boot script affecting access to sd[bf]. That disk is old, and contains 2 swap partitions and 2 raid partitions (for / and /home). The rootfs surely must be started first, it never has any problems, and it would start sd[bf] IIUC. Both raids are raid1, booting is with setup --stage2=/boot/grub/stage2 --force-lba (hd0) (hd0,4) setup --stage2=/boot/grub/stage2 --force-lba (hd1) (hd1,4) quit The only non-SuSE init scripts I use are using these dependencies # Provides: boot.local-rc # Required-Start: $local_fs boot.rootfsck # Should-Start: boot.quota boot.cleanup # Required-Stop: $null # Should-Stop: $null # Default-Start: B # Default-Stop: and they call env SYSTEMD_NO_WRAP=1 /etc/init.d/boot.cleanup to get the usual cleanup behaviour with systemd, and they create a few files in /tmp. All of this is operates on the rootfs, not on /home. The /home raid is the one which isn't behaving. The details of the home array are identical to the ones for the rootfs, but I had to create them manually. When I installed oS 12.1 (fresh install) yast was giving me some problems with superblock versions. I didn't want 0.9, and 1.2 didn't work so I had to manually force the use of 1.0. The system boots from the rootfs raid1. (I must be using this type of setup for almost 10 years now.) If there's any other useful information I can provide I'd be happy to. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.