NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Drive failed, volume not mounting - what next?
I'm hoping some members of this forum might be able to offer some advice. My NAS has a problem.
My setup: ReadyNAS RND4200 NV+ V2
3 x 3TB Segate Barracuda.
Default out-of-the-box raid setup.
I came back from a weekend away to find my ReadyNAS RND4200 NV+ V2 unresponsive and I was unable to connect to it. I (reluctantly) powered it down and restarted.
On restarting, one of the drives sounds like it's failed (clicking/clunking).
Of the three disk LEDs, only disk 1 stays lit. 2 and 3 both flash.
The following message appears in my emailed log:
***** File system check forced at Sun Jul 6 21:25:51 GMT 2014 *****
fsck from util-linux-ng 2.17.2 e2fsck 1.41.14 (22-Dec-2010)
fsck.ext4: No such file or directory while trying to open /dev/c/c
Possibly non-existent device?
What shall I do next? I'm a bit paranoid about doing something that will cause the system to wipe everything (important files are backed up, but I'd like to recover my media library if possible).
I will attach the downloaded logs.
My setup: ReadyNAS RND4200 NV+ V2
3 x 3TB Segate Barracuda.
Default out-of-the-box raid setup.
I came back from a weekend away to find my ReadyNAS RND4200 NV+ V2 unresponsive and I was unable to connect to it. I (reluctantly) powered it down and restarted.
On restarting, one of the drives sounds like it's failed (clicking/clunking).
Of the three disk LEDs, only disk 1 stays lit. 2 and 3 both flash.
The following message appears in my emailed log:
***** File system check forced at Sun Jul 6 21:25:51 GMT 2014 *****
fsck from util-linux-ng 2.17.2 e2fsck 1.41.14 (22-Dec-2010)
fsck.ext4: No such file or directory while trying to open /dev/c/c
Possibly non-existent device?
What shall I do next? I'm a bit paranoid about doing something that will cause the system to wipe everything (important files are backed up, but I'd like to recover my media library if possible).
I will attach the downloaded logs.
11 Replies
- Link to log files.
https://dl.dropboxusercontent.com/u/7528753/System_log-Dinosaur-20140706-213725.zip
I just noticed something a little worrying in the log that indicates I had a mixed setup of RAID 1 and RAID 5. Am I right in thinking that's not good? EDIT: Just realised this is probably how XRAID-2 would look - and that's how my nas in configured.
***** RAID configuration log from 2014/06/29 *****
***** mdadm -D --scan -v *****
ARRAY /dev/md/0 level=raid1 num-devices=3 metadata=1.2 name=2CB05DBE7FEB:0 UUID=95d8207e:d82cdba9:7d2580b0:6db85c40
devices=/dev/sda1,/dev/sdb1,/dev/sdc1
ARRAY /dev/md/1 level=raid1 num-devices=3 metadata=1.2 name=2CB05DBE7FEB:1 UUID=f64f2ca9:4561a09a:d408ddf0:89aaa8a2
devices=/dev/sda2,/dev/sdb2,/dev/sdc2
ARRAY /dev/md/2 level=raid5 num-devices=3 metadata=1.2 name=2CB05DBE7FEB:2 UUID=f053f55a:e9e369e7:26af938d:2cacb8da
devices=/dev/sda3,/dev/sdb3,/dev/sdc3
***** mdadm -D --scan -vv ***** - Natalie,
I have looked at logs through Dropbox download.
On 29th June, disk_smart06_29 shows 3 disks, looking fine.
Raid_config_2014_06_29 shows 3 working disks in RAID.
Disk_smart_07_06 only shows 1 disk on channel 1.
For some strange reason, disks 2 & 3 have disappeared.
Did the NAS physically move recently? Any vibration?
Can you power off, remove and re-seat disks 2 & 3.
Power on, and see.
The 3 disks were on RAID 5, so that is not the issue.
Regards Marto - Hi Marto, thanks for looking at the logs for me.
I've followed those steps and it hasn't made any difference. All the drives were already sat correctly, but I removed them, blew a bit of dust off and reseated them.
The unit hasn't moved recently - it's positioned out of the way, next to a wall, behind some furniture - and it's been in the same place for 4 months. It's on a wooden floor, but I don't think vibration would be a cause. We do have cats, but can't see that being a problem considering the weight of the NAS and it's location next to the wall.
I'm really puzzled as to what has happened? - Natalie,
Yes, it is puzzling.
2 points
(a) For disks 2 and 3, can you put through a disk checker utility, and see are there errors?
(b) If you boot up NAS with Disks (1 &2 ), will it boot?
Similarly Disks (1 &3)?
Regards Marto - Okay, 6 weeks later and I've finally got around to testing the drives. Disk 2 has got failures, so following the advice from Marto I've booted with just 1 & 3 and bingo, the NAS boots. Thanks you Marto for your help.
So, aside from the fact that it's frustrating that there's no simple error like "disk 2 has failed, booting with just 1 & 3..." I need to get a replacement disk.
After a bit of analysis, I think I'm going to get a like for like 3TB Seagate replacement (ST3000DM001 is on the HCL - http://kb.netgear.com/app/answers/detail/a_id/20641/~/hardware-compatibility-list-hard-disks)
I've looked at the WD RED, but I worry about mixing manufacturers. Am I right in thinking that *in theory* I could mix different drives fro the HCL and everything *should* be okay? Seems like it would make sense to not rock the boat... - I think uou are way better off with a WD30EFRX Red, I suggesting passing on the ST3000DM001. If you search this forum, you will see lots of people have had problems with that particular seagate.
You can mix/match vendors as long as the disks are the same size. I have two NAS running with a mix of Seagate and WDC reds.
Some people actually think that mixing vendors might improve reliability, not reduce it. The idea is that if you install multiple identical disks at the same time, they likely will fail about the same time. Though that doesn't apply in your case, since you are replacing a drive. - So this 3TB WD Red (http://www.ebuyer.com/390986) would be fine wouldn't it?
For some reason the HCL only shows 1, 2 and 4TB WD Red drives. Not sure why they don't like the 3TB! - Ah, it is on the HCL - I was searching incorrectly. Right, going to get that instead.
- Another question, when the new disk arrives (to replace faulty disk 2) I just need to slot it into the same bay (number 2) that the faulty drive was in and then let the system restripe the data. That's right isn't it?
Yes. hot-insert the replacement (with the NAS running). Don't format it, it is not necessary.nataliej wrote: Another question, when the new disk arrives (to replace faulty disk 2) I just need to slot it into the same bay (number 2) that the faulty drive was in and then let the system restripe the data. That's right isn't it?
If desired, you can run wdc's lifeguard diagnostic first - though that requires that you attach the disk to a Windows PC.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
