Carlusha99  Freshman Member

Mijzelf: Hartelijk dank voor je hulp de afgelopen weken.De bestanden staan nog op hun plaats....moet even nog iets met de foldernamen doen. Nu even de vraag hoe nu verder met de Raid1 configuratie.De 1Tb WD10EFRX staat nu in raid1 en de 2TB nog in JBOD.Echter de optie Migrate is niet beschkbaar. Ik ga nu even de bestanden…

Mijzelf: I max sized md0......mdadm: component size of /dev/md0 has been set to 976244928K did the e2fsck e2fsck 1.41.14 (22-Dec-2010) /dev/md0: clean, 93128/61022208 files, 141480464/244061232 blocks I took out the external disk. looked at the GUI:see attachment.(Remark: i changed the name of the volume on disk1 to…

The files on md3 remain untouchable through the NAS however. Because the state of this md3 is unknown. I wonder if we do the same (grow action) with the original disk WD10EFRX who has the RAID1 and still is down, what will happen then.?

then i tried: mount /dev/md3 /mnt/mountpoint<br>~ # I looked at the GUI and saw this:<br>see attachment<br>

Mijzelf: I can see progress: # mdadm --grow --size=max /dev/md3 mdadm: component size of /dev/md3 has been set to 976244928K ~ # e2fsck.new /dev/md3 e2fsck 1.41.14 (22-Dec-2010) /dev/md3: clean, 93128/61022208 files, 141480464/244061232 blocks ~ # mount /dev/md3 /tmp/mountpoint mount: mount point /tmp/mountpoint does not…

Mijzelf: ~ # mdadm --grow /dev/md3 mdadm: no changes to --grow ~ # e2fsck.new /dev/md3 e2fsck 1.41.14 (22-Dec-2010) The filesystem size (according to the superblock) is 244061232 blocks The physical size of the device is 244061198 blocks Either the superblock or the partition table is likely to be corrupt! Abort<y>? no…

Mijzelf: I have done e2fsck on /dev/md3~ # e2fsck.new /dev/md3 e2fsck 1.41.14 (22-Dec-2010) The filesystem size (according to the superblock) is 244061232 blocks The physical size of the device is 244061198 blocks Either the superblock or the partition table is likely to be corrupt! Abort<y>? no /dev/md3 contains a file…

Mijzelf: This is the result: ~ # cat /proc/mounts rootfs / rootfs rw 0 0 /proc /proc proc rw,relatime 0 0 /sys /sys sysfs rw,relatime 0 0 none /proc/bus/usb usbfs rw,relatime 0 0 devpts /dev/pts devpts rw,relatime,mode=600 0 0 /dev/mtdblock8 /zyxel/mnt/nand yaffs2 ro,relatime 0 0 /dev/sda1 /zyxel/mnt/sysdisk ext2…

Mijzelf: after the assemble command this is the picture in the NAS. (see attachment)So maybe i should restart the NAS to get back the situation before the assembling.

~ # mkdir /mnt/mountpoint ~ # mount /dev/md3 /mnt/mountpoint mount: wrong fs type, bad option, bad superblock on /dev/md3, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so

~ # mdadm --assemble /dev/md3 /dev/sdc -- rune2fsck.net -f /dev/md3 mdadm: /dev/md3 has been started with 1 drive (out of 2).

Mijzelf: # e2fsck.new -f /dev/sdc e2fsck 1.41.14 (22-Dec-2010) e2fsck.new: Superblock invalid, trying backup blocks... e2fsck.new: Bad magic number in super-block while trying to open /dev/sdc The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an…

so it seems not mountable.

I reconnected the external hdd to the NAS, but it is not recognized as a external volume.

Hello Mijzelf, After more than 8 hours the copy-process has ended. sync 59585+1 records in 59585+1 records out 999675855360 bytes (931.0GB) copied, 29220.648631 seconds, 32.6MB/s You mentioned i should first disconnect it from the NAS and then reconnect it.I presume you meant the external drive. After reconnection it…