My ReadyNAS has been running flawlessly for years. I had to rewire my office. I powered off the ReadyNAS and took several days to rewire. When I powered on the ReadyNAS it hung during boot with a "Kernal error" and sat there for 24 hours before I turned it off. I've read every post herein that I think is related. I carefully removed and tested each disk (Seagate 500GB Barracuda) with Seagate's Windows 7 based diagnostics. I'm using a USB disk cradle. Disk 4, the one that always ran a little warmer than the other 3 ... the one next to the vents ... the one with a lot of dust on it ... failed to even be recognized by the USB interface. Listening closely I hear an endless "whirr ... whirr ... whirr ..." when I power it on. An exact replacement is on the way to me.I've read posts about replacing (in an attempt to recover) one disk. I'm frightened. How do I replace the disk without losing it all? I've not powered on the ReadyNAS again since I turned it off. I think I need a detailed step by step procedure.How should I proceed, please?Thanks,Stan

So you have no backup?One option would be to clone your remaining three disks though you may find the NAS boots up fine with just those three disks installed.If you clone your good disks then if something does go wrong at least you have the clones to fall back on.

I understood that the ReadyNAS would allow me to recover from the loss of a single disk. I'd rather like to see that promise fulfilled.Most of the data that was on the ReadyNAS (all the really critical data) is backed up.What I'd really like to know is:1) do I stick the new HD into the ReadyNAS and power it up and expect it to recover?2) do I power it up first and hot-swap the disk when the boot sequence fails ... and expect it to recover?3) is there some other procedure I should be using?How should I proceed, please?Thanks,

What disks were in the NAS?Did you start out with 4 disks installed or did you start with less disks installed and add more over time?

The current configuration (4 disks) has been there since 2008. I don't even remember for sure which RAID.

If you boot without disks do you still get the kernel panic?If not you could try powering off the NAS, putting the 3 good disks back in the same slot as before, booting the NAS, seeing if it comes up fine and if so adding a replacement disk to slot 4.Note disk 4 may be the dedicated parity disk (has no partition on it) if you are using X-RAID. So it didn't even appear to your PC as if it were an uninitialised disk?

ReadyNAS NV (RND4250-100NAS) hangs on boot

14 Replies

stanleytberry
Aspirant
Oct 10, 2014
OK. It booted without the 4th disk in place. The indicator for the 4th disk is blinking. The display indicates the correct IP address and "C: 0.1/1.3T free".

Can I safely access the shares without ruining my chance of dropping the new disk in when it arrives?

Should I drop the old disk back in on the chance that it really is the parity disk and that's why my USB wouldn't detect it (I will try this only on assurances that it won't screw the chance of having the new one work if the old one doesn't)?

Again, thanks.
StephenB
Guru - Experienced User
Oct 10, 2014
stanleytberry wrote:
OK. It booted without the 4th disk in place. The indicator for the 4th disk is blinking. The display indicates the correct IP address and "C: 0.1/1.3T free".
Great.

stanleytberry wrote:
Can I safely access the shares without ruining my chance of dropping the new disk in when it arrives?
Yes. Rebuilding the parity disk requires reading all the sectors on the existing drives, to construct the parity. If you can't read the data now, the rebuild process won't work anyway. If you can read the data now, you might as well. I'd probably avoid writing to it much until the new disk is sync'd, though if the remaining disks are healthy it shouldn't matter - just an abundance of caution.

stanleytberry wrote:
Should I drop the old disk back in on the chance that it really is the parity disk and that's why my USB wouldn't detect it
I wouldn't. Windows should have installed the device driver for the disk, even if it was zeroed. Similarly, Seatools will find it, even if Windows doesn't understand the format.

I had a Seagate fail similarly a few weeks ago - the NAS stayed running in my case, but the SATA channel on the drive timed out (and eventually disabled itself). Windows didn't recognize it, Seatools didn't see it. There were no SMART alerts on reallocated sectors, etc, it just failed.
stanleytberry
Aspirant
Oct 10, 2014
Thanks.

It appears that everything is there. I'll exercise it as little as possible until the new disk is in place.

Later,
stanleytberry
Aspirant
Oct 15, 2014
OK. I inserted the new disk late yesterday afternoon. The ReadyNAS acknowledged the insertion of the 4th disk. A minute later it indicated that it was synching the disk. Eventually the display went back to normal. The light for the 4th disk was still blinking when I went to bed.

This AM all 4 lights are on solid and the box appears to be functioning normally.

Huzzah!

Thanks a bunch.

Forum Discussion

ReadyNAS NV (RND4250-100NAS) hangs on boot

14 Replies

Related Content

ReadyNAS Duo v1 resynch hang.

GS724Tv4 hinter einen GS748Tv5 hängen

ReadyNas RN104 hangs 99% booting

ReadyNAS RN626X 6.10.2 Random hanging

ReadyNAS Pro RNDP6000 hangs on "ReadyNAS" prompt.

NETGEAR Academy

ProSupport for Business