Package: update-initramfs Version: update-initramfs Severity: normal
my / is on sdb; sda+sdc are set up as RAID=>/dev/md0 At the moment, I boot my system on sdb; file systems of sdb have been copied to md0. After booting sdb, I can run successfully: mount -o offset=2564014080 /dev/md0 /mnt/whatever So, to boot and use md0 as root, I changed the boor arguments from /vmlinuz ro initrd=/initrd.img root=/dev/sdb3 to /vmlinuz ro initrd=/initrd.img root=/dev/md0 rootflags=offset=2564014080 In short, at bot time I am said that md0 is not mountable; then, I fallback to some prompt. Ther, I try to mount md0 manually, running exactly the same command: mount -o offset=2564014080 /dev/md0 /mnt/ and I am said from memory "invalid argument". After 2 weeks trying EVERY THING I could think of, I have embedded losetup from the main system in the ramdisk; once in the prompt, the procedure became: - losetup -o 2564014080 /dev/loop4 /dev/md0 - /scripts/dhp/losetup -o 2564014080 /dev/loop6 /dev/md0 - mount -o ro /dev/loop4 /root - mount -o ro /dev/loop6 /root First call is using losetup from the ramdisk made by update-initramfs; the second one is using losetup I put in the ramdisk. 3rd call fails, 4th works. This means losetup actually embedded in initramdisk does not support properly the offset option. The result is that loop device can not be set up, and everything fails. I do not know if other scripts also have this failure (to assume that the offset option is never passed), but please, check so. I will do more testing within days, to see if rebuilding the ramdisk manually and swicthing the losetup binary solves the problem; if yes, then other scripts are OK. -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: alpha Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-alpha-smp Locale: LANG=en_GB.ISO-8859-15, LC_CTYPE=en_GB.ISO-8859-15 (charmap=ISO-8859-15) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
