[solved] problems mounting raid5 in dual boot

[dbc]

This is driving me nuts. I have a dual-boot system where I am trying to get a fresh "Funtoo stable" version of Gentoo installed. Mostly, everything is OK. But this is a dual boot system with Archlinux, and /home is a raid5/ext3 partition that I want to mount on both systems. The raid was created and initialized on Arch, and now I'm tyring to get Gentoo to see it. I get the dreaded: "wrong fs type, bad option, bad superblock on /dev/md0..." message whenever a mount command is issued. I have a raid0/ext2 partition that both systems mount quite happily.

Arch's /etc/fstab:

Code: Select all

[root@i7arch etc]# cat /etc/fstab
# 
# /etc/fstab: static file system information
#
# <file system>        <dir>         <type>    <options>          <dump> <pass>
none                   /dev/pts      devpts    defaults            0      0
none                   /dev/shm      tmpfs     defaults            0      0

/dev/cdrom             /media/cd   auto    ro,user,noauto,unhide   0      0
#/dev/dvd               /media/dvd  auto    ro,user,noauto,unhide   0      0
#/dev/fd0               /media/fl   auto    user,noauto             0      0

/dev/sda2 		/ 		ext3 		defaults 0 1
/dev/sda1 		/boot 		ext3 		defaults 0 1

/dev/sdb1 		swap 		swap 		defaults 0 0

/dev/md0 		/home 		ext3 		defaults 0 1
/dev/md1 		/tmp2 		ext2 		defaults 0 1

Gentoo's /etc/fstab:

Code: Select all

/dev/sda1		/boot		ext3		noauto,noatime	1 2
/dev/sda3		/		ext3		noatime		0 1
/dev/sda2		none		swap		sw		0 0
/dev/cdrom		/mnt/cdrom	auto		noauto,ro,user	0 0
/dev/fd0		/mnt/floppy	auto		noauto,user	0 0
#
/dev/md0		/home		ext3		noatime		0 1
/dev/md1		/tmp2		ext2		noatime		0 1

Everything is build on raid auto-detect partitions.

Arch's mdadm.conf:

Code: Select all

[root@i7arch /]# cat /etc/mdadm.conf | grep ^DEVICE
DEVICE /dev/sdb2 /dev/sdc2 /dev/sdd2 /dev/sdb4 /dev/sdc4 /dev/sdd4
[root@i7arch /]# cat /etc/mdadm.conf | grep ^ARRAY
ARRAY /dev/md0 devices=/dev/sdb2,/dev/sdc2,/dev/sdd2
ARRAY /dev/md1 devices=/dev/sdb4,/dev/sdc4,/dev/sdd4

Gentoo's mdadm.conf:

Code: Select all

[root@i7arch /]# cat /mnt/gentoo/etc/mdadm.conf | grep ^DEVICE
DEVICE /dev/sdb2 /dev/sdc2 /dev/sdd2 /dev/sdb4 /dev/sdc4 /dev/sdd4
[root@i7arch /]# cat /mnt/gentoo/etc/mdadm.conf | grep ^ARRAY
ARRAY /dev/md0 level=5 devices=/dev/sdb2,/dev/sdc2,/dev/sdd2
ARRAY /dev/md1 level=0 devices=/dev/sdb4,/dev/sdc4,/dev/sdd4

Arch's happy mdstat:

Code: Select all

[root@i7arch /]# cat /proc/mdstat
Personalities : [raid0] [raid6] [raid5] [raid4] 
md1 : active raid0 sdb4[0] sdd4[2] sdc4[1]
      310761024 blocks 64k chunks
      
md0 : active raid5 sdb2[0] sdd2[2] sdc2[1]
      292961152 blocks level 5, 64k chunk, algorithm 2 [3/3] [UUU]
      
unused devices: <none>

This is what dmesg has to say. If there's a clue in there, I ain't seein' it.

Code: Select all

[root@i7arch log]# pwd
/mnt/gentoo/var/log
[root@i7arch log]# tail -170 dmesg 
[    5.107996] Bluetooth: RFCOMM TTY layer initialized
[    5.108186] Bluetooth: RFCOMM ver 1.10
[    5.108373] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    5.108562] Bluetooth: BNEP filters: protocol multicast
[    5.108751] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[    5.109148] RPC: Registered udp transport module.
[    5.109338] RPC: Registered tcp transport module.
[    5.114151] registered taskstats version 1
[    5.114484]   Magic number: 1:891:401
[    5.114742] md: Waiting for all devices to be available before autodetect
[    5.114933] md: If you don't use raid, use raid=noautodetect
[    5.115241] md: Autodetecting RAID arrays.
[    5.127019] usb 8-1: new low speed USB device using uhci_hcd and address 2
[    5.216623] md: Scanned 6 and added 6 devices.
[    5.216817] md: autorun ...
[    5.217003] md: considering sdd4 ...
[    5.217193] md:  adding sdd4 ...
[    5.217381] md: sdd2 has different UUID to sdd4
[    5.217570] md:  adding sdc4 ...
[    5.217757] md: sdc2 has different UUID to sdd4
[    5.217947] md:  adding sdb4 ...
[    5.218135] md: sdb2 has different UUID to sdd4
[    5.218416] md: created md1
[    5.218602] md: bind<sdb4>
[    5.218793] md: bind<sdc4>
[    5.218982] md: bind<sdd4>
[    5.219171] md: running: <sdd4><sdc4><sdb4>
[    5.219516] md: personality for level 0 is not loaded!
[    5.219705] md: do_md_run() returned -22
[    5.219892] md: md1 stopped.
[    5.220081] md: unbind<sdd4>
[    5.224193] md: export_rdev(sdd4)
[    5.224386] md: unbind<sdc4>
[    5.228192] md: export_rdev(sdc4)
[    5.228386] md: unbind<sdb4>
[    5.232192] md: export_rdev(sdb4)
[    5.232407] md: considering sdd2 ...
[    5.232595] md:  adding sdd2 ...
[    5.232783] md:  adding sdc2 ...
[    5.232970] md:  adding sdb2 ...
[    5.233157] md: created md0
[    5.233345] md: bind<sdb2>
[    5.233535] md: bind<sdc2>
[    5.233724] md: bind<sdd2>
[    5.233913] md: running: <sdd2><sdc2><sdb2>
[    5.234248] md: personality for level 5 is not loaded!
[    5.234437] md: do_md_run() returned -22
[    5.234624] md: md0 still in use.
[    5.234810] md: ... autorun DONE.
[    5.271773] usb 8-1: skipped 1 descriptor after interface
[    5.271777] usb 8-1: skipped 1 descriptor after interface
[    5.276769] usb 8-1: default language 0x0409
[    5.286770] usb 8-1: New USB device found, idVendor=05c7, idProduct=2012
[    5.286967] usb 8-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[    5.287159] usb 8-1: Product: USB Keyboard + Mouse
[    5.287377] usb 8-1: uevent
[    5.287403] usb 8-1: usb_probe_device
[    5.287405] usb 8-1: configuration #1 chosen from 1 choice
[    5.289769] usb 8-1: adding 8-1:1.0 (config #1, interface 0)
[    5.289786] usb 8-1:1.0: uevent
[    5.289839] usbhid 8-1:1.0: usb_probe_interface
[    5.289840] usbhid 8-1:1.0: usb_probe_interface - got id
[    5.298643] kjournald starting.  Commit interval 5 seconds
[    5.298648] EXT3-fs: mounted filesystem with ordered data mode.
[    5.298657] VFS: Mounted root (ext3 filesystem) readonly on device 8:3.
[    5.298671] Freeing unused kernel memory: 552k freed
[    5.298724] Write protecting the kernel read-only data: 7048k
[    5.366115] khelper used greatest stack depth: 5536 bytes left
[    5.366312] input: USB Keyboard + Mouse as /devices/pci0000:00/0000:00:1d.2/usb8/8-1/8-1:1.0/input/input3
[    5.370201] uhci_hcd 0000:00:1d.2: reserve dev 2 ep81-INT, period 8, phase 4, 118 us
[    5.374276] generic-usb 0003:05C7:2012.0001: input,hidraw0: USB HID v1.10 Keyboard [USB Keyboard + Mouse] on usb-0000:00:1d.2-1/input0
[    5.374667] usb 8-1: adding 8-1:1.1 (config #1, interface 1)
[    5.374678] usb 8-1:1.1: uevent
[    5.374713] usbhid 8-1:1.1: usb_probe_interface
[    5.374714] usbhid 8-1:1.1: usb_probe_interface - got id
[    5.400924] input: USB Keyboard + Mouse as /devices/pci0000:00/0000:00:1d.2/usb8/8-1/8-1:1.1/input/input4
[    5.405201] uhci_hcd 0000:00:1d.2: reserve dev 2 ep82-INT, period 8, phase 4, 99 us
[    5.411277] generic-usb 0003:05C7:2012.0002: input,hidraw1: USB HID v1.10 Mouse [USB Keyboard + Mouse] on usb-0000:00:1d.2-1/input1
[    5.415492] drivers/usb/core/inode.c: creating file '002'
[    5.705012] usb usb3: suspend_rh (auto-stop)
[    5.705033] usb usb4: suspend_rh (auto-stop)
[    5.705051] usb usb5: suspend_rh (auto-stop)
[    5.705073] usb usb6: suspend_rh (auto-stop)
[    5.705090] usb usb7: suspend_rh (auto-stop)
[    5.787551] init-early.sh used greatest stack depth: 3912 bytes left
[    7.144923] usb usb3: uevent
[    7.144941] usb 3-0:1.0: uevent
[    7.145024] usb usb4: uevent
[    7.145046] usb 4-0:1.0: uevent
[    7.145126] usb usb5: uevent
[    7.145142] usb 5-0:1.0: uevent
[    7.145225] usb usb1: uevent
[    7.145241] usb 1-0:1.0: uevent
[    7.145941] usb usb6: uevent
[    7.145958] usb 6-0:1.0: uevent
[    7.146048] usb usb7: uevent
[    7.146065] usb 7-0:1.0: uevent
[    7.146150] usb usb8: uevent
[    7.146168] usb 8-0:1.0: uevent
[    7.146204] usb 8-1: uevent
[    7.146220] usb 8-1:1.0: uevent
[    7.146330] usb 8-1:1.1: uevent
[    7.146521] usb usb2: uevent
[    7.146538] usb 2-0:1.0: uevent
[    7.336010] ohci1394 0000:0b:04.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
[    7.389110] ohci1394: fw-host0: OHCI-1394 1.0 (PCI): IRQ=[19]  MMIO=[fbeff000-fbeff7ff]  Max Packet=[2048]  IR/IT contexts=[8/8]
[    7.689133] hub 1-0:1.0: hub_suspend
[    7.689140] usb usb1: bus auto-suspend
[    7.689142] ehci_hcd 0000:00:1a.7: suspend root hub
[    7.689165] hub 3-0:1.0: hub_suspend
[    7.689168] usb usb3: bus auto-suspend
[    7.689171] usb usb3: suspend_rh
[    7.689185] hub 4-0:1.0: hub_suspend
[    7.689188] usb usb4: bus auto-suspend
[    7.689190] usb usb4: suspend_rh
[    7.689203] hub 5-0:1.0: hub_suspend
[    7.689204] usb usb5: bus auto-suspend
[    7.689205] usb usb5: suspend_rh
[    7.689218] hub 6-0:1.0: hub_suspend
[    7.689219] usb usb6: bus auto-suspend
[    7.689220] usb usb6: suspend_rh
[    7.689233] hub 7-0:1.0: hub_suspend
[    7.689234] usb usb7: bus auto-suspend
[    7.689235] usb usb7: suspend_rh
[    7.689248] hub 2-0:1.0: hub_suspend
[    7.689249] usb usb2: bus auto-suspend
[    7.689251] ehci_hcd 0000:00:1d.7: suspend root hub
[    8.653111] ieee1394: Host added: ID:BUS[0-00:1023]  GUID[001e8c0001ef26fa]
[    8.737784] md: raid1 personality registered for level 1
[    8.750954] md: raid0 personality registered for level 0
[    8.778495] xor: automatically using best checksumming function: generic_sse
[    8.783001]    generic_sse:  9972.000 MB/sec
[    8.783002] xor: using function: generic_sse (9972.000 MB/sec)
[    8.784466] async_tx: api initialized (sync-only)
[    8.833010] raid6: int64x1   2871 MB/s
[    8.850010] raid6: int64x2   3402 MB/s
[    8.867018] raid6: int64x4   2335 MB/s
[    8.884017] raid6: int64x8   2265 MB/s
[    8.901006] raid6: sse2x1    6621 MB/s
[    8.918007] raid6: sse2x2    7734 MB/s
[    8.935001] raid6: sse2x4    8843 MB/s
[    8.935002] raid6: using algorithm sse2x4 (8843 MB/s)
[    8.935004] md: raid6 personality registered for level 6
[    8.935005] md: raid5 personality registered for level 5
[    8.935006] md: raid4 personality registered for level 4
[    9.136738] md: md1 stopped.
[    9.140287] md: bind<sdc4>
[    9.140417] md: bind<sdd4>
[    9.140547] md: bind<sdb4>
[    9.141128] md1: setting max_sectors to 128, segment boundary to 32767
[    9.141130] raid0: looking at sdb4
[    9.141131] raid0:   comparing sdb4(103587008)<6> with sdb4(103587008)
[    9.141133] raid0:   END
[    9.141134] raid0:   ==> UNIQUE
[    9.141135] raid0: 1 zones
[    9.141136] raid0: looking at sdd4
[    9.141137] raid0:   comparing sdd4(103587008)<6> with sdb4(103587008)
[    9.141138] raid0:   EQUAL
[    9.141139] raid0: looking at sdc4
[    9.141140] raid0:   comparing sdc4(103587008)<6> with sdb4(103587008)
[    9.141142] raid0:   EQUAL
[    9.141143] raid0: FINAL 1 zones
[    9.141144] raid0: done.
[    9.141145] raid0 : md_size is 621522048 sectors.
[    9.141146] raid0 : conf->spacing is 621522048 sectors.
[    9.141147] raid0 : nb_zone is 1.
[    9.141148] raid0 : Allocating 8 bytes for hash.
[    9.141774]  md1: unknown partition table
[    9.452320] EXT3 FS on sda3, internal journal
[    9.567875] EXT3-fs: unable to read superblock

I'm thinking since the raid0/ext2 system mounts OK, that raid is correctly built into my kernel. Since Gentoo mounts it's own ext3 file systems, it should be able to mount the raid5/ext3. Somehow it just doesn't seem to detect the raid5 superblocks. Possibilities:

1) The raid5 file layout is different between the two systems.
2) The Gentoo kernel still is not built correctly
3) Some configuration file is missing a critical piece some place.
4) <your idea here>

-dave

[desultory]

Moved from Installing Gentoo to Unsupported Software.

[Sysa]

1. Please check you have the same kernel and system utilities (util-linux, e2fsprogs etc) versions for both systems.
2. Try to include UUID (mdadm -D --scan) into both /etc/mdadm.conf

This is driving me nuts. I have a dual-boot system where I am trying to get a fresh "Funtoo stable" version of Gentoo installed. Mostly, everything is OK. But this is a dual boot system with Archlinux, and /home is a raid5/ext3 partition that I want to mount on both systems. The raid was created and initialized on Arch, and now I'm tyring to get Gentoo to see it. I get the dreaded: "wrong fs type, bad option, bad superblock on /dev/md0..." message whenever a mount command is issued. I have a raid0/ext2 partition that both systems mount quite happily.
...
I'm thinking since the raid0/ext2 system mounts OK, that raid is correctly built into my kernel. Since Gentoo mounts it's own ext3 file systems, it should be able to mount the raid5/ext3. Somehow it just doesn't seem to detect the raid5 superblocks. Possibilities:

1) The raid5 file layout is different between the two systems.
2) The Gentoo kernel still is not built correctly
3) Some configuration file is missing a critical piece some place.
4) <your idea here>

-dave

[dbc]

Thanks for the clue about version checking. Raid versions don't seem to be as forward/backward compatible as I imagined them to be. The key to my problem is the raid metatdata versions, there are 4 running around and are quite different. Also, something in the boot process is a little different between the two systems, in that even after getting all the metadata sync'ed up, I still have to manually start the array before it will mount. That could still be a problem in my init scripts.

In any case, since the purpose of this system is to run various experiments on several different flavors of Linux, I decided that putting a commonly-visible /home in a difficult to mount partition is one of my all-time dimmer ideas, so I'm backing off of raid for that. I'm mainly using raid for the performance boost from striping anyway, and I can get that without putting /home behind a giant speed bump.

thanks,
dave