Losing Volume on Raid 0 #24221687

Yes, you have (I think) textbook symptoms of locked drives which I think mdgm suspected earlier on.
See this thread:
viewtopic.php?f=24&t=78843
There are few ssh commands later down in the thread and it's possible that someone from the forum may be able to help you if you're not confident with that. Wait a bit.

If you have a known good drive you could test this hypothesis by factory defaulting the nas with this known good drive, setting it up then rebooting.

Hi

Ok, I put my 4 drives back in the NAS, did a factory reset, installed SSH, restarted and lost my volume as expected...all 4 drives are visible by the NAS and reporting with no faults.

Ran the commands on the link that you referred to but received the below errors:

login as: root root@NASBackup's password: Linux NASBackup 2.6.31.8.nv+v2 #1 Thu Apr 18 17:40:54 HKT 2013 armv5tel GNU/Linux Last login: Sat Dec 6 17:04:59 2014 from surfacepro root@NASBackup:~# hdparm --security-unlock NETGEAR /dev/??? security_password="NETGEAR" /dev/bus: Issuing SECURITY_UNLOCK command, password="NETGEAR", user=user SECURITY_UNLOCK: Inappropriate ioctl for device root@NASBackup:~# hdparm --security-disable NETGEAR /dev/??? security_password="NETGEAR" /dev/bus: Issuing SECURITY_DISABLE command, password="NETGEAR", user=user SECURITY_UNLOCK: Inappropriate ioctl for device root@NASBackup:~#

Is ~# normal for the shell that the ARM ReadyNAS uses? I’m guessing it is as the commands run, I used mobaxterm and putty just to make sure that it wasn’t the client software.

Also for anyone else installing the SSH add-on for the NV+V2, it doesn’t show in the installed add-on list for some reason... took 4 hours to figure that one out, as I assumed that the install kept failing.

Any idea what this “Inappropriate ioctl for device” error is in relation the ReadyNAS? Any other pointers?

I’m at a loss at this point.

Once again, thanks for your time guys. It’s people like you that donate your free time to help others that makes the internet.

A very kind community member of the NAS Elite as offered to remote on to my NAS to see what they can find. I'll not post who this individual is to prevent people private messaging this person for the same service. But they know who they are, and they have my thanks.

I'll post back what is found.

Yes, you needed to replace the ??? in the commands with the drive identifier. That's probably the reason your attempt failed.

Hi

Ahhh. I thought that it was some kind of crazy wildcard for the command.

The only drive identifier that I have is md0, keeping in mind that I'm raid 0 (4x4TB all recognised in the dashboard).

Linux NASBackup 2.6.31.8.nv+v2 #1 Thu Apr 18 17:40:54 HKT 2013 armv5tel GNU/Linux Last login: Sat Dec 6 19:14:30 2014 from 192.168.0.19 root@NASBackup:~# df -h Filesystem Size Used Avail Use% Mounted on /dev/md0 4.0G 535M 3.3G 14% / tmpfs 16K 0 16K 0% /USB tmpfs 50M 0 50M 0% /var/replicate/shm root@NASBackup:~# fdisk -l WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted. Disk /dev/sda: 4000.8 GB, 4000787030016 bytes 256 heads, 63 sectors/track, 484501 cylinders Units = cylinders of 16128 * 512 = 8257536 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sda1 1 266306 2147483647+ ee GPT Disk /dev/md0: 4293 MB, 4293906432 bytes 2 heads, 4 sectors/track, 1048317 cylinders Units = cylinders of 8 * 512 = 4096 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Disk /dev/md0 doesn't contain a valid partition table Disk /dev/md1: 536 MB, 536858624 bytes 2 heads, 4 sectors/track, 131069 cylinders Units = cylinders of 8 * 512 = 4096 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Disk /dev/md1 doesn't contain a valid partition table root@NASBackup:~# hdparm --security-unlock NETGEAR /dev/md0 security_password="NETGEAR" /dev/md0: Issuing SECURITY_UNLOCK command, password="NETGEAR", user=user The running kernel lacks CONFIG_IDE_TASK_IOCTL support for this device. SECURITY_UNLOCK: Invalid argument root@NASBackup:~# hdparm --security-disable NETGEAR /dev/md0 security_password="NETGEAR" /dev/md0: Issuing SECURITY_DISABLE command, password="NETGEAR", user=user The running kernel lacks CONFIG_IDE_TASK_IOCTL support for this device. SECURITY_UNLOCK: Invalid argument root@NASBackup:~#

Am I doing something silly?

I thought that the "Nas Elite" member was helping you. Let him help you.

This is a good example of "a little knowledge is a dangerous thing" . I see it regularly in my profession and I'm pretty sure the "Nas Elite" member will be thinking that too (about both of us)
I think we must humbly accept our relative ignorance.

Hey, I classify you as one too. :)

My NAS is in Debug mode just now waiting on their login, but they'll be sleeping at this time.

You don't disable it on the md device, but rather on the disks that have it enabled e.g. /dev/sda, /dev/sdb etc.

I unlocked the disks yesterday.

I can confirm that the disk unlock performed by mdgm worked. My NAS systems are syncing as I type this.

To summarise for anyone looking at this thread with same issue. Without physically trying it myself, it would appear that once the SSH add-on is installed, and you’ve logged in to your NAS using something like mobaXterm or putty (your NAS username is “root” and the password is your normal admin password) the commands you need are:

hdparm --security-unlock NETGEAR /dev/sda
hdparm --security-disable NETGEAR /dev/sda

hdparm --security-unlock NETGEAR /dev/sdb
hdparm --security-disable NETGEAR /dev/sdb

hdparm --security-unlock NETGEAR /dev/sdc
hdparm --security-disable NETGEAR /dev/sdc

hdparm --security-unlock NETGEAR /dev/sdd
hdparm --security-disable NETGEAR /dev/sdd

with the a, b, c, d at the end representing each of the physical disks of your NAS.

Well this is my understanding of it. If this isn’t fully correct, then feel free to correct me mdgm.

To mdgm, thanks you for your help with this issue. You’re a life saver. I’d also like to thank vandermerwe for his input.

Thanks again guys.