Comments
-
Hello Mijzelf, I have connected the 2TB external drive to the NAS as external volume.
-
Hi Mijzelf, It is possible that I first time activated the NAS some where in 2017 with the old firmware. I cannot remember it well. But it is strange though that such deep-impacted update of firmware is not done before the first activation of the NAS.
-
Mijzelf, I presume an USB 3.0. external HDD of 2TB would be well enough. Connected through USB connection of the NAS.
-
Hi Mijzelf, Unfortunately i don't have a freee external disc available right now. But i will purchase one this week as soon as possible. I will come back to you when it has arrived. Thank you for your help so far.
-
Mijzelf: Here is the output: /dev/sda2: Magic : a92b4efc Version : 1.2 Feature Map : 0x0 Array UUID : fe6cce5e:c2787799:d330641f:892b916a Name : NSA325-v2:0 (local to host NSA325-v2) Creation Time : Sat Jun 15 10:49:19 2019 Raid Level : raid1 Raid Devices : 2 Avail Dev Size : 976244928 (931.02 GiB 999.67 GB) Array Size :…
-
Hoi Mijzelf: BusyBox v1.17.2 (2017-06-23 10:40:08 CST) built-in shell (ash) Enter 'help' for a list of built-in commands. ~ # mdadm --stop /dev/md0 && mount -t ext2 /dev/sda2 /mnt/mountpoint mdadm: stopped /dev/md0 mount: wrong fs type, bad option, bad superblock on /dev/sda2, missing codepage or helper program, or other…
-
Hi Mijzelf I have entered ~ # mkdir /mnt/mountpoint mkdir: can't create directory '/mnt/mountpoint': File exists ~ # mdadm --stop /dev/md0 && mount -t ext4 /dev/sda2 /mnt/mountpoint mdadm: stopped /dev/md0 dmesg mount: wrong fs type, bad option, bad superblock on /dev/sda2, missing codepage or helper program, or other…
-
Just to clarify this was the original return information /mnt/mountpoint # mdadm --stop /dev/md0 && mount -t ext4 /dev/sda2 /mnt/mountpoint mdadm: stopped /dev/md0 mount: wrong fs type, bad option, bad superblock on /dev/sda2, missing codepage or helper program, or other error In some cases useful info is found in syslog -…
-
/mnt/mountpoint # mdadm --stop /dev/md0 && mount -t ext4 /dev/sda2 /mnt/mountpoidmesntmdadm: stopped /dev/md0 mount: wrong fs type, bad option, bad superblock on /dev/sda2, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so /mnt/mountpoint #…
-
I did:mkdir ~ # mkdir /mnt/mountpoint ~ # su BusyBox v1.17.2 (2017-06-23 10:40:08 CST) built-in shell (ash) Enter 'help' for a list of built-in commands. ~ # mdadm --stop /dev/md0 && mount /dev/sda2 /mnt/mountpoint mdadm: stopped /dev/md0 mount: you must specify the filesystem type <== <Did i forget something to enter?> ~…
-
Hi Mijzelf: Attached are the results of cat /proc/mdstat and cat /proc/mountsdev/md1 is the mounted one i believe, because it has i-data/3cc8587e md0 is the one with problems and is in raid1. If i copy the data from md0 to md1 and put a raid1 over both discs, won't i lose data then? Either way can you give me the command…
-
Dear Mijzelf, Thank you so far your support. This evening i will first investigate the arrays and partitions of both disks in the NAS. I will come back to you with the results and hopefully you can help me with right mounting command afterwards.
-
how can i copy data to another disk?
-
I shut the NAS down and restarted the NAS again....by the power button. When i run the fsck.new another time i got the report as attached.
-
is it possible to resize the filesystem to the format of the psysical size of the device?I have tried resize2fs -f /dev/md0 but got a reply that one of the blocks returned a short read.and that i have to do e2fsck.new -fy /dev/md0