- Last Active
I did some more testing after a promt from Zyxel support. It seems like I get the volume down error on a new volume whenever I already have a volume created.1 disk in any slot with a basic volume -> No error2 disks in any slots with a raid1 volume -> No error2 or more disks in any slots with a basic volume each -> Error on…
Hmm, most have been some temporary thing. I was away for a day and retried your suggested commands today, and now everything worked. The only thing I got an error on was mdadm /dev/md0 --add missing where I got a message sayingmdadm: 'missing' only meaningful with --re-add which I tried instead, and gave no error.Here's my…
Many thanks for your continued help.I started to run the commands, but are getting stuck on readding sdc. When I run mdadm /dev/md0 --add /dev/sdc1 I get this message: mdadm: Cannot open /dev/sdc1: Device or resource busy I'm finding quite a few results with this error on Google, but am not really versed enough in Linux or…
And just because I'm a complete noob when it comes to stuff like this; will this touch the data on the disks in slot 1 and 2? I'm guessing not as I presume this will rebuild how the NAS sees drives and doesn't touch the actual drives, but I wanted to confirm before I do anything :smile:
~ $ cat /proc/mdstat<br>Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]<br>md4 : active raid1 sdc3<br> 240067392 blocks super 1.2 [1/1] [U]<br><br>md3 : active raid1 sdb3<br> 3902886720 blocks super 1.2 [1/1] [U]<br><br>md2 : active raid1 sda3<br> 3902886720 blocks super 1.2 [1/1]…
Unfortunately factory resettting did not do anything either. I still get a "Volume down" error when the NAS has restarted after creating a volume in slot 3 or 4. This is using one of the drives that I cleaned completely via Gparted.It might be worth noting that I don't get any volume name of the volume that is marked as…
That did unfortunately not work. Started up an instance of Gparted to format all of the disks (the 2TB and the two 250GB ones). Put one of the 250GB ones back in slot 3 of the NAS, created a basic volume one it, waited for the restart, and it shows up as crashed as soon as I can access the web UI again.