2010/2/22 Edgard Pineda <epineda.contact@xxxxxxxxx>: > RESOLVED!! thank you a lot Ryusuke! the problem was the re-creation of well... sorry, not all resolved at all... when I tried the devices order combinations there are 4 combinations with which when I try to mount in read only mode I got "warning: broken superblock. using spare superblock.", and other 2 combination where I only got "warning: Checksum error in segment payload". Then my problem now is how I can detect which of these 2 combination is the correct and how I can fix the checksum error in segment payload?? When mounting with the following command: mount -t nilfs2 -r /dev/md0 /mnt/d1 I got in dmesg: NILFS: INFO: recovery required for readonly filesystem. NILFS: write access will be enabled during recovery. NILFS: warning: Checksum error in segment payload. NILFS: error searching super root. And the partition don't get mounted. any ideas? Regards, Edgard. > my raid5 array with 1 missing device in other server: I had to try > many combinations creating the array, for example: > > mdadm --create /dev/md0 --assume-clean --level=5 --raid-devices=4 > /dev/sdb1 /dev/sdc1 /dev/sdd1 missing > then... > mdadm --stop /dev/md0 > mdadm --create /dev/md0 --assume-clean --level=5 --raid-devices=4 > /dev/sdb1 /dev/sdd1 /dev/sdc1 missing > then... > mdadm --stop /dev/md0 > mdadm --create /dev/md0 --assume-clean --level=5 --raid-devices=4 > /dev/sdb1 /dev/sdd1 /dev/sdc1 missing > > Finally with "hd /dev/md0 | less" I got: > > 00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| > * > 00000400 02 00 00 00 00 00 34 34 00 01 00 00 94 f1 52 4b |......44......RK| > 00000410 e6 94 e9 bd 02 00 00 00 44 75 05 00 00 00 00 00 |........Du......| > 00000420 00 00 16 a2 ba 02 00 00 01 00 00 00 00 00 00 00 |................| > 00000430 00 08 00 00 05 00 00 00 50 ef 02 00 00 00 00 00 |........P.......| > 00000440 00 f8 c1 1e 00 00 00 00 68 4d 09 00 00 00 00 00 |........hM......| > 00000450 00 e8 c7 27 00 00 00 00 98 f6 4a 4a 00 00 00 00 |...'......JJ....| > 00000460 5f ea 0b 4b 00 00 00 00 2e 17 2c 4b 00 00 00 00 |_..K......,K....| > 00000470 09 00 32 00 00 00 01 00 98 f6 4a 4a 00 00 00 00 |..2.......JJ....| > 00000480 00 4e ed 00 00 00 00 00 00 00 00 00 0b 00 00 00 |.N..............| > 00000490 80 00 20 00 c0 00 10 00 48 55 07 21 83 15 41 bc |.. .....HU.!..A.| > 000004a0 a1 bf 15 04 c9 27 77 98 00 00 00 00 00 00 00 00 |.....'w.........| > 000004b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| > * > 00001000 1a 08 ef 53 b1 23 1e af 11 fa af 1e 38 00 10 00 |...S.#......8...| > 00001010 36 75 05 00 00 00 00 00 a5 64 de 4a 00 00 00 00 |6u.......d.J....| > 00001020 00 08 00 00 00 00 00 00 ff 07 00 00 01 00 00 00 |................| > 00001030 c0 7f 00 00 00 00 00 00 9b 35 00 00 00 00 00 00 |.........5......| > 00001040 46 02 00 00 00 00 00 00 f7 07 00 00 f7 07 00 00 |F...............| > 00001050 e4 15 19 01 00 00 00 00 ba 1c 00 00 00 00 00 00 |................| > 00001060 e5 15 19 01 00 00 00 00 bb 1c 00 00 00 00 00 00 |................| > > references about linux raid5: > http://ubuntuforums.org/archive/index.php/t-410136.html > http://www.intelligentedu.com/how_to_recover_from_a_broken_raid5.html > > Regards, > Edgard. > > 2010/2/22 Ryusuke Konishi <ryusuke@xxxxxxxx>: >> Hi, >> On Mon, 22 Feb 2010 13:44:46 -0300, Edgard Pineda wrote: >>> Hi, >>> >>> I just had a 4 harddrives in raid5 with nilfs2 (kernel 2.6.32 and >>> nilfs-utils 2.0.15) and I've got a power cut, then I rebuilt the >>> array, but when I tried to mount the nilfs2 partition I've got: >>> "NILFS: Can't find nilfs on dev md0" (in dmesg) after execute >>> "mount.nilfs2: Error while mounting /dev/md0 on disk: Invalid >>> argument". >>> >>> Any idea? can I mount as "read only" to rescue some files? any tools >>> to "see" the files and fix the partition? >>> >>> Regards, >>> Edgard. >> >> Umm.., sounds serious. The message "NILFS: Can't find nilfs on xxx" >> is output when both of the two super blocks are broken. >> >> Can you dump the partition with hd command? >> >> # hd /dev/md0 | less >> >> If the partition is not filled yet, it would look like this: >> >> 00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| >> * >> 00000400 02 00 00 00 00 00 34 34 00 01 00 00 7b 93 80 d4 |......44....{...| >> 00000410 50 09 11 38 02 00 00 00 17 11 00 00 00 00 00 00 |P..8............| >> 00000420 00 5e 8f 8b 08 00 00 00 01 00 00 00 00 00 00 00 |.^..............| >> 00000430 00 08 00 00 05 00 00 00 79 00 00 00 00 00 00 00 |........y.......| >> 00000440 25 70 00 00 00 00 00 00 0e 00 00 00 00 00 00 00 |%p..............| >> 00000450 00 88 88 00 00 00 00 00 bb fb 7c 4b 00 00 00 00 |..........|K....| >> 00000460 71 d4 7f 4b 00 00 00 00 85 d4 7f 4b 00 00 00 00 |q..K.......K....| >> 00000470 03 00 32 00 01 00 01 00 bb fb 7c 4b 00 00 00 00 |..2.......|K....| >> 00000480 00 4e ed 00 00 00 00 00 00 00 00 00 0b 00 00 00 |.N..............| >> 00000490 80 00 20 00 c0 00 10 00 8f d2 a7 e6 99 7a 41 e8 |.. ..........zA.| >> 000004a0 ae 88 26 e1 48 0c a5 f4 00 00 00 00 00 00 00 00 |..&.H...........| >> 000004b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| >> * >> 00001000 dd 21 ee fe 80 ad 4e a1 11 fa af 1e 38 00 07 00 |.!....N.....8...| >> 00001010 00 00 00 00 00 00 00 00 bb fb 7c 4b 00 00 00 00 |..........|K....| >> ... >> >> >> where "34 34" at offset 0x0406 is the magic number of NILFS. >> >> Regards, >> Ryusuke Konishi >> > -- To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
