NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ReadyNAS NV+ (SPARC) Kernel Panic with Factory Settings
Good evening all,
History and setup:
I've had my NV+ for three or four years, in that time it have been kitted out with 2x Seagate 2TB hard drives and 2x Western Digital 2TB hard drives, the four drive in one volume. In January I directly connected the ReadyNAS to the second NIC on my Mac Pro, then used it as storage for the iTunes library to be streamed (via the Mac Pro) to my Apple TV - I've had poor experience with trying to serve content to my TV (XBOX/Raspberry Pi) and I wanted to go down an 'all Apple' route. The content was already on the ReadyNAS, so it was just a case of setting iTunes to look at the share for its library and import everything. This all went according to plan and worked for a month or so.
Problems:
About a week ago I went to stream a movie to my Apple TV, it got about 5 seconds in and the stream stopped. The ReadyNAS looked fine, the display appeared normal, but I couldn't access the Web interface or get in via SSH - the power button didn't work, so a hard power off ensued. After it booted back up everything connected again, and I selected the same movie to stream and the same thing happened.
Looking in the logs it appeared to have an issue on channel "(??)", which is immensely helpful…All the disks looked OK, nothing specific was being reported. I tried a few hard reboots and occasionally got a Kernel Panic. I managed to get everything working by taking the second disk out (middle left), it was only a hunch that this would work due to some differing activity on the disk 2 LED. I've transfered all of my content elsewhere for the time being, and have spent bits of free time this week trying to troubleshoot.
I have performed a Factory Reset and although it reports the same sized volume, it says it must resync disk 4. When the resync had about 2% to go, it kernel panicked. Before this happened, I SSHd into the ReadyNAS to look around (nothing destructive). I was intrigued to find the volumes appear to be set up with LVM, and doing a quick `fdisk -l` found that disks 1-3 had a smattering of partitions, but disk 4 did not.
I have since taken all of the hard drives out of the ReadyNAS, hung them off of another computer, checked them, and wiped the partition tables clean - each disk looks 'new'. With the power off, installed the disks again in a different order, and on the first boot selected a Factory Reset. Again, the web GUI showed that it was resyncing to disk 4…Again, when it got to around 2% until complete, I got a Kernel Panic. Again, before it panicked I looked at the disks via SSH and disk 4 didn't have any partitions
I've checked the memory, and the ReadyNAS reports it to be OK…
In between times, I've found that the first three bays seem fine, just populating them seems to be OK. I haven't tried populating three bays where one is bay 4, though not sure if this adds anything…
It seems odd that the first three disks get partitioned, etc, on a Factory Reset, but the fourth disk doesn't appear to...
So now I'm at a bit of a loose end…The logs in the web interface seem to tell me nothing specific, in fact nothing at all aside from the fact that I pulled the power when it wasn't ready…
Linux, Solaris, throw it at me. Storage and networking, erm, not so good at!
Many thanks in advance,
Ben
History and setup:
I've had my NV+ for three or four years, in that time it have been kitted out with 2x Seagate 2TB hard drives and 2x Western Digital 2TB hard drives, the four drive in one volume. In January I directly connected the ReadyNAS to the second NIC on my Mac Pro, then used it as storage for the iTunes library to be streamed (via the Mac Pro) to my Apple TV - I've had poor experience with trying to serve content to my TV (XBOX/Raspberry Pi) and I wanted to go down an 'all Apple' route. The content was already on the ReadyNAS, so it was just a case of setting iTunes to look at the share for its library and import everything. This all went according to plan and worked for a month or so.
Problems:
About a week ago I went to stream a movie to my Apple TV, it got about 5 seconds in and the stream stopped. The ReadyNAS looked fine, the display appeared normal, but I couldn't access the Web interface or get in via SSH - the power button didn't work, so a hard power off ensued. After it booted back up everything connected again, and I selected the same movie to stream and the same thing happened.
Looking in the logs it appeared to have an issue on channel "(??)", which is immensely helpful…All the disks looked OK, nothing specific was being reported. I tried a few hard reboots and occasionally got a Kernel Panic. I managed to get everything working by taking the second disk out (middle left), it was only a hunch that this would work due to some differing activity on the disk 2 LED. I've transfered all of my content elsewhere for the time being, and have spent bits of free time this week trying to troubleshoot.
I have performed a Factory Reset and although it reports the same sized volume, it says it must resync disk 4. When the resync had about 2% to go, it kernel panicked. Before this happened, I SSHd into the ReadyNAS to look around (nothing destructive). I was intrigued to find the volumes appear to be set up with LVM, and doing a quick `fdisk -l` found that disks 1-3 had a smattering of partitions, but disk 4 did not.
I have since taken all of the hard drives out of the ReadyNAS, hung them off of another computer, checked them, and wiped the partition tables clean - each disk looks 'new'. With the power off, installed the disks again in a different order, and on the first boot selected a Factory Reset. Again, the web GUI showed that it was resyncing to disk 4…Again, when it got to around 2% until complete, I got a Kernel Panic. Again, before it panicked I looked at the disks via SSH and disk 4 didn't have any partitions
I've checked the memory, and the ReadyNAS reports it to be OK…
In between times, I've found that the first three bays seem fine, just populating them seems to be OK. I haven't tried populating three bays where one is bay 4, though not sure if this adds anything…
It seems odd that the first three disks get partitioned, etc, on a Factory Reset, but the fourth disk doesn't appear to...
So now I'm at a bit of a loose end…The logs in the web interface seem to tell me nothing specific, in fact nothing at all aside from the fact that I pulled the power when it wasn't ready…
Linux, Solaris, throw it at me. Storage and networking, erm, not so good at!
Many thanks in advance,
Ben
11 Replies
Replies have been turned off for this discussion
- Most probably a disk problem.
When you say you tested the disks, did you actually test them each with vendor tools extended tests ( seatools and wd lifeguard)? - No, I did a quick check that I could partition and format them, then did a "Verify disk" under Disk Utility in OS X.
I'd be happy if it was a disk, being far cheaper to replace than the ReadyNAS, but I find it odd that the problem doesn't follow a particular disk around the bays…
I'll investigate the vender tools and test each disk. - What firmware?
- Ah yes, should have put that in the first post, sorry. It's running the latest, 4.1.14
- After your factory default you say the unit starts a resync. You say it is resyncing to disk 4, what do you mean?
If you factory default with 4 disks in and the volume starts to resync, all disks are involved and you should not receive messages about specific disks.
Are you saying the initial resync happens normally but then the nas wants to resync with disk 4 again? If this is the case it may be that disk 4 is dropping out of the array for some reason, perhaps a bad slot/sata connector.
I would still run full tests on all the disks first. - The Factory Reset seems to take around half an hour, and during that time I cannot access the web GUI. When RAIDar tells me the ReadyNAS is accessible, I log in and disk 4 is resyncing.
After managing to borrow a Windows laptop from work (the vender tools don't seem to be available for OS X), I've plopped the first disk into an enclosure and hooked it up via USB (2.0). The first Seagate one failed with "6C9AC2A4" which translates to "Serial number not detected, SeaTools did fail the drive", but that was several hours into the "Long Generic" test. Plugging the second Seagate drive in also shows that it's unable to ready the serial number and firmware version, though I'm not sure if that is due to communications over USB?
The second Seagate drive is currently on it's "Long Generic" test, I'll test the WD ones after. - Seatools may require a sata connection. It does for me.
- I have used Seatools with USB. Though I have a laptop with eSATA, so I usually use that for diags. There are some restrictions (and getting the serial might be one).
The net here is that the first disk failed ("Seatools did fail the drive"), and it seems real because it happened several hours into the test. If you can read the SMART stats, that might be useful information. - I've swapped the enclosure and both of the Seagate drives passed the test. The WD ones are a different story - one fails several hours into the test (Too many bad sectors), and the other gets stuck a few minutes in. I'm running the first WD drive through again as I think I may have knocked the cable around the time it failed.
- I still suggest checking the SMART stats on the PC. There are several freeware tools that support this, including Acronis Drive Monitor (though you do need to leave them your email address).
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
