NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Disk Removal Detected but all looks ok? ReadyNAS NV+ V2 running 5.1.13
Hi. Over the last few days I've tried to create a new Windows 7 VHD which took days, so I aborted it. In investigating why it was taking so long I discovered that the NAS network interface was only r...
You can try removing the disk with the NAS running, and then re-insert it (also with the NAS running).
It'd be wise to make sure you have an up to date backup first.
I take it there's no way to kick-off the RAID rebuild at the CLI then. Oh well, I removed the disk, waited a few minutes and in that time the NAS recognised the disk failure/removal. When I re-inserted the disk it thought it was a new disk, tested it, and then started to re-sync. It didn't recognise it as a disk that was previously in use, should it have done?
I've historically had problems with disk 1 on this NAS. Also opening and closing the door causes the NAS to "chirp" a lot of the time. When I first got it, it did this, and after a Support call the NAS was replaced, and the new one did/does the same, so I've assumed it's "normal" behaviour although I can't think why it should be.
It said it was resyncing:
Fri Nov 17 09:53:20 WET 2017 RAID sync started on volume C.
Fri Nov 17 09:52:48 WET 2017 Data volume will be rebuilt with disk 1.
Fri Nov 17 09:52:39 WET 2017 New disk detected. If multiple disks have been added, they will be processed one at a time. Please do not remove any added disk(s) during this time. [Disk 1]...but I didn't get any message to indicate that sync had completed like I have on previous occasions thus:
Sun May 21 00:24:20 WEST 2017 RAID sync finished on volume C.
...and it's been over 18 hours since I replaced to disk.
In addition to this the Blue LED for Disk 2 is now flashing.
I have no front panel display or GUI Info indications that there is anything wrong though.
It sounds like it is still syncing. What does RAIDar show for the status? If the syncing goes on well beyod the normal time, it's probably because the drive is full of errors. My experience is that the NAS will just keep chugging along trying to complete the sync instead of giving up at some point. Then, ultimately, it will fail the resync.
The RAIDar status says "Healthy". Is there anything I can interrogate from the Command Line Interface please?
fixit9660 wrote:
It didn't recognise it as a disk that was previously in use, should it have done?
No, it will format/resync any disk that you hot-insert (no matter what was on it).
fixit9660 wrote:
Also opening and closing the door causes the NAS to "chirp" a lot of the time.
The NAS has no speaker, so this is surprising. Are you certain it's not one of the disk drives?
fixit9660 wrote:
The RAIDar status says "Healthy". Is there anything I can interrogate from the Command Line Interface please?
Try mdadm --detail /dev/md??? I don't own a v2 NAS, so I'm not sure what the exact device name is for the data volume. md0 should should you the details on the OS partition.
Detail in the order requested:
root@NETGEAR_NAS:/# cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md2 : active raid5 sda3[4](S) sdb3[3](F) sdc3[2]
5851089408 blocks super 1.2 level 5, 64k chunk, algorithm 2 [3/1] [__U]
md1 : active raid1 sda2[5] sdb2[4] sdc2[3]
524276 blocks super 1.2 [3/3] [UUU]
md0 : active raid1 sda1[5] sdc1[3] sdb1[4]
4193268 blocks super 1.2 [3/3] [UUU]
unused devices: <none>
root@NETGEAR_NAS:/#and...
"chirping" could be one of the disks; it sounds like the heads doing a rapid "seek" and then stopping, but how do I tell?
root@NETGEAR_NAS:/dev# mdadm --detail /dev/md0
/dev/md0:
Version : 1.2
Creation Time : Sun Jul 6 11:07:41 2014
Raid Level : raid1
Array Size : 4193268 (4.00 GiB 4.29 GB)
Used Dev Size : 4193268 (4.00 GiB 4.29 GB)
Raid Devices : 3
Total Devices : 3
Persistence : Superblock is persistentUpdate Time : Sun Nov 19 11:02:51 2017
State : clean
Active Devices : 3
Working Devices : 3
Failed Devices : 0
Spare Devices : 0Name : E0469AA09320:0
UUID : c4b120f8:384eda73:e2e10747:202a8ca9
Events : 2038158Number Major Minor RaidDevice State
5 8 1 0 active sync /dev/sda1
3 8 33 1 active sync /dev/sdc1
4 8 17 2 active sync /dev/sdb1
root@NETGEAR_NAS:/dev# mdadm --detail /dev/md1
/dev/md1:
Version : 1.2
Creation Time : Sun Jul 6 11:07:42 2014
Raid Level : raid1
Array Size : 524276 (512.07 MiB 536.86 MB)
Used Dev Size : 524276 (512.07 MiB 536.86 MB)
Raid Devices : 3
Total Devices : 3
Persistence : Superblock is persistentUpdate Time : Sun Nov 19 06:47:02 2017
State : clean
Active Devices : 3
Working Devices : 3
Failed Devices : 0
Spare Devices : 0Name : E0469AA09320:1
UUID : 3a1e75e5:4b69f076:3e21d8e1:dd9c0445
Events : 97442Number Major Minor RaidDevice State
5 8 2 0 active sync /dev/sda2
3 8 34 1 active sync /dev/sdc2
4 8 18 2 active sync /dev/sdb2
root@NETGEAR_NAS:/dev# mdadm --detail /dev/md2
/dev/md2:
Version : 1.2
Creation Time : Sun Jul 6 11:07:42 2014
Raid Level : raid5
Array Size : 5851089408 (5580.03 GiB 5991.52 GB)
Used Dev Size : 2925544704 (2790.02 GiB 2995.76 GB)
Raid Devices : 3
Total Devices : 3
Persistence : Superblock is persistentUpdate Time : Sun Nov 19 06:47:02 2017
State : clean, FAILED
Active Devices : 1
Working Devices : 2
Failed Devices : 1
Spare Devices : 1Layout : left-symmetric
Chunk Size : 64KName : E0469AA09320:2
UUID : 0d8cff58:88922ac2:697948ea:aba59759
Events : 881405Number Major Minor RaidDevice State
0 0 0 0 removed
1 0 0 1 removed
2 8 35 2 active sync /dev/sdc33 8 19 - faulty spare /dev/sdb3
4 8 3 - spare /dev/sda3
root@NETGEAR_NAS:/dev#
fixit9660 wrote:
Number Major Minor RaidDevice State
0 0 0 0 removed
1 0 0 1 removed
2 8 35 2 active sync /dev/sdc33 8 19 - faulty spare /dev/sdb3
4 8 3 - spare /dev/sda3This doesn't look good. Do you have a backup?
and...
"chirping" could be one of the disks; it sounds like the heads doing a rapid "seek" and then stopping, but how do I tell?
The best way is to connect the disk to a Windows PC (either sata or USB adapter) and run the vendor diagnostic (Seatools for seagate, Lifeguard for Western Digital). If the disk is chirping, that is a clear sign of disk failure.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
