NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Unable to Stream any HD Content from my ReadyNAS Pro 6
Hey There, Everyone! New on the forum as of today, and ReadyNAS Pro 6 owner for approximately 1 week now! Happy to be aboard! Unfortunately I have run into a problem which is quite frustrating, b...
Hey Everyone,
Thanks for continuing to try to help me troubleshoot!
Thanks for this tip! You got me to thinking it might be the disks... Would another way to test this, be to connect an external HDD via USB to the NAS, and then try to stream to one of my computers from that? I thought it might be a bit easier than taking out all the drives, etc., but still achieve the same effect - streaming from the NAS, with the content on some other drive than it is on now.
In order to get some metrics around my disk/network speeds, I did a couple of things...
First, I did the drag and drop test from the "How to optimize the ReadyNAS" article, and with a 3.01 GB file, I get an average of 32.34 MB/sec read speed from the NAS through my Gigabit network.
Second, I used the AJA System Test to do a Disk Read Existing File test, and the average read speed from the NAS through my Gigabit network was 102 MB/sec.
So then I started taking a look at the disks themselves...
Taking a look at the SMART status of each disc in Frontview, I see the following:
Disk 1: Reallocated Sector Count - 0, ATA Error Count - 0 (Brand new HDD)
Disk 2: Reallocated Sector Count - 0, ATA Error Count - 0 (Brand new HDD)
Disk 3: Reallocated Sector Count - 8, ATA Error Count - 0 (1 Year old HDD)
Disk 4: Reallocated Sector Count - 27, ATA Error Count - 0 (1 Year old HDD)
Disk 5: Reallocated Sector Count - 9, ATA Error Count - 0 (1 Year old HDD)
Disk 6: Reallocated Sector Count - 41, ATA Error Count - 0 (1 Year old HDD)
That got me thinking that, yep, those 1 year old HDDs must be having some issues, so I downloaded all the logs from the ReadyNAS, and in the system.log, I see a couple of curious entries:
This seems to pop up each time I reboot my NAS:
Oct 15 07:17:08 Media-Server kernel: ata3.00: WARNING: device requires firmware update to be fully functional.
Oct 15 07:17:08 Media-Server kernel: ata4.00: WARNING: device requires firmware update to be fully functional.
Oct 15 07:17:08 Media-Server kernel: ata5.00: WARNING: device requires firmware update to be fully functional.
Oct 15 07:17:08 Media-Server kernel: ata6.00: WARNING: device requires firmware update to be fully functional.
And this seems to happen when the streaming stops and the ReadyNAS becomes unreponsive:
Oct 15 08:26:04 Media-Server kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Oct 15 08:26:04 Media-Server kernel: ata3.00: failed command: FLUSH CACHE EXT
Oct 15 08:26:04 Media-Server kernel: ata3.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
Oct 15 08:26:04 Media-Server kernel: res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Oct 15 08:26:04 Media-Server kernel: ata3.00: status: { DRDY }
Oct 15 08:26:04 Media-Server kernel: ata3: hard resetting link
Oct 15 08:26:04 Media-Server kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Oct 15 08:26:04 Media-Server kernel: ata4.00: failed command: FLUSH CACHE EXT
Oct 15 08:26:04 Media-Server kernel: ata4.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
Oct 15 08:26:04 Media-Server kernel: res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Oct 15 08:26:04 Media-Server kernel: ata4.00: status: { DRDY }
Oct 15 08:26:04 Media-Server kernel: ata4: hard resetting link
Oct 15 08:26:04 Media-Server kernel: ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Oct 15 08:26:04 Media-Server kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Oct 15 08:26:04 Media-Server kernel: ata3.00: configured for UDMA/133
Oct 15 08:26:04 Media-Server kernel: ata3.00: retrying FLUSH 0xea Emask 0x4
Oct 15 08:26:04 Media-Server kernel: ata4.00: configured for UDMA/133
Oct 15 08:26:04 Media-Server kernel: ata4.00: retrying FLUSH 0xea Emask 0x4
Oct 15 08:26:04 Media-Server kernel: ata3.00: device reported invalid CHS sector 0
Oct 15 08:26:04 Media-Server kernel: ata3: EH complete
Oct 15 08:26:04 Media-Server kernel: ata4.00: device reported invalid CHS sector 0
Oct 15 08:26:04 Media-Server kernel: ata4: EH complete
Oct 15 08:27:31 Media-Server kernel: ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Oct 15 08:27:31 Media-Server kernel: ata6.00: failed command: FLUSH CACHE EXT
Oct 15 08:27:31 Media-Server kernel: ata6.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
Oct 15 08:27:31 Media-Server kernel: res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Oct 15 08:27:31 Media-Server kernel: ata6.00: status: { DRDY }
Oct 15 08:27:31 Media-Server kernel: ata6: hard resetting link
Oct 15 08:27:31 Media-Server kernel: ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Oct 15 08:27:32 Media-Server kernel: ata6.00: configured for UDMA/133
Oct 15 08:27:32 Media-Server kernel: ata6.00: retrying FLUSH 0xea Emask 0x4
Oct 15 08:27:32 Media-Server kernel: ata6.00: device reported invalid CHS sector 0
Oct 15 08:27:32 Media-Server kernel: ata6: EH complete
Oct 15 08:29:47 Media-Server kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Oct 15 08:29:47 Media-Server kernel: ata4.00: failed command: FLUSH CACHE EXT
Oct 15 08:29:47 Media-Server kernel: ata4.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
Oct 15 08:29:47 Media-Server kernel: res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Oct 15 08:29:47 Media-Server kernel: ata4.00: status: { DRDY }
Oct 15 08:29:47 Media-Server kernel: ata4: hard resetting link
Oct 15 08:29:47 Media-Server kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Oct 15 08:29:47 Media-Server kernel: ata4.00: configured for UDMA/133
Oct 15 08:29:47 Media-Server kernel: ata4.00: retrying FLUSH 0xea Emask 0x4
Oct 15 08:29:47 Media-Server kernel: ata4.00: device reported invalid CHS sector 0
Oct 15 08:29:47 Media-Server kernel: ata4: EH complete
Oct 15 09:27:24 Media-Server kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Oct 15 09:27:24 Media-Server kernel: ata5.00: failed command: FLUSH CACHE EXT
Oct 15 09:27:24 Media-Server kernel: ata5.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
Oct 15 09:27:24 Media-Server kernel: res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Oct 15 09:27:24 Media-Server kernel: ata5.00: status: { DRDY }
Oct 15 09:27:24 Media-Server kernel: ata5: hard resetting link
Oct 15 09:27:24 Media-Server kernel: ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Oct 15 09:27:24 Media-Server kernel: ata5.00: configured for UDMA/133
Oct 15 09:27:24 Media-Server kernel: ata5.00: retrying FLUSH 0xea Emask 0x4
Oct 15 09:27:24 Media-Server kernel: ata5.00: device reported invalid CHS sector 0
Oct 15 09:27:24 Media-Server kernel: ata5: EH complete
Oct 15 12:11:08 Media-Server kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Oct 15 12:11:08 Media-Server kernel: ata4.00: failed command: FLUSH CACHE EXT
Oct 15 12:11:08 Media-Server kernel: ata4.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
Oct 15 12:11:08 Media-Server kernel: res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Oct 15 12:11:08 Media-Server kernel: ata4.00: status: { DRDY }
Oct 15 12:11:08 Media-Server kernel: ata4: hard resetting link
Oct 15 12:11:08 Media-Server kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Oct 15 12:11:08 Media-Server kernel: ata4.00: configured for UDMA/133
Oct 15 12:11:08 Media-Server kernel: ata4.00: retrying FLUSH 0xea Emask 0x4
Oct 15 12:11:08 Media-Server kernel: ata4.00: device reported invalid CHS sector 0
Oct 15 12:11:08 Media-Server kernel: ata4: EH complete
Oct 15 12:11:08 Media-Server cnid_dbd[7615]: read: Connection reset by peer
Oct 15 12:11:08 Media-Server cnid_dbd[7615]: error reading message header: Connection reset by peer
Oct 15 12:12:29 Media-Server kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Oct 15 12:12:29 Media-Server kernel: ata3.00: failed command: FLUSH CACHE EXT
Oct 15 12:12:29 Media-Server kernel: ata3.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
Oct 15 12:12:29 Media-Server kernel: res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Oct 15 12:12:29 Media-Server kernel: ata3.00: status: { DRDY }
Oct 15 12:12:29 Media-Server kernel: ata3: hard resetting link
Oct 15 12:12:29 Media-Server kernel: ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Oct 15 12:12:29 Media-Server kernel: ata3.00: configured for UDMA/133
Oct 15 12:12:29 Media-Server kernel: ata3.00: retrying FLUSH 0xea Emask 0x4
Oct 15 12:12:29 Media-Server kernel: ata3.00: device reported invalid CHS sector 0
Oct 15 12:12:29 Media-Server kernel: ata3: EH complete
Oct 15 12:12:29 Media-Server cnid_dbd[7615]: read: Connection reset by peer
Oct 15 12:12:29 Media-Server cnid_dbd[7615]: error reading message header: Connection reset by peer
Oct 15 12:17:17 Media-Server kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Oct 15 12:17:17 Media-Server kernel: ata5.00: failed command: FLUSH CACHE EXT
Oct 15 12:17:17 Media-Server kernel: ata5.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
Oct 15 12:17:17 Media-Server kernel: res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Oct 15 12:17:17 Media-Server kernel: ata5.00: status: { DRDY }
Oct 15 12:17:17 Media-Server kernel: ata5: hard resetting link
Oct 15 12:17:17 Media-Server kernel: ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Oct 15 12:17:17 Media-Server kernel: ata5.00: configured for UDMA/133
Oct 15 12:17:17 Media-Server kernel: ata5.00: retrying FLUSH 0xea Emask 0x4
Oct 15 12:17:17 Media-Server kernel: ata5.00: device reported invalid CHS sector 0
Oct 15 12:17:17 Media-Server kernel: ata5: EH complete
So it seems pretty clear at this point that the ReadyNAS is not very happy with the status of Drives 3-6.
My plan of attack at this point was to attempt to upgrade the firmware on those drives, and then see if the performance is any better and those warnings/errors disappear.
Failing that, I would plan on swapping out the 1 year old drives with new drives on the compatibility list, one at a time, letting the RAID rebuild, and once complete with new drives, see if the performance gets better.
So now my questions are:
1) Any way to upgrade the firmware of the drives now that they are in the ReadyNAS?
2) If not, can I pull the drives, put them into a USB enclosure, and upgrade the firmware by direct attaching them to a Mac or PC, without messing up the data they contain?
3) Thoughts on my plan of attack?
I suppose worst case, I just take the RAID offline, upgrade the firmware of the drives on another machine, then rebuild the RAID once that has been done, and move my data back over to the RAID. I just hate to do that since I spent such a long time copying everything over.
Thanks for continuing to try to help me troubleshoot!
="TeknoJnky"
- if you have a spare disk, power down, remove and label each disk, put the extra spare disk int the nas by it self and let it boot up/factory default it, copy some HD content to it and see if it will stream without errors.
Thanks for this tip! You got me to thinking it might be the disks... Would another way to test this, be to connect an external HDD via USB to the NAS, and then try to stream to one of my computers from that? I thought it might be a bit easier than taking out all the drives, etc., but still achieve the same effect - streaming from the NAS, with the content on some other drive than it is on now.
In order to get some metrics around my disk/network speeds, I did a couple of things...
First, I did the drag and drop test from the "How to optimize the ReadyNAS" article, and with a 3.01 GB file, I get an average of 32.34 MB/sec read speed from the NAS through my Gigabit network.
Second, I used the AJA System Test to do a Disk Read Existing File test, and the average read speed from the NAS through my Gigabit network was 102 MB/sec.
So then I started taking a look at the disks themselves...
Taking a look at the SMART status of each disc in Frontview, I see the following:
Disk 1: Reallocated Sector Count - 0, ATA Error Count - 0 (Brand new HDD)
Disk 2: Reallocated Sector Count - 0, ATA Error Count - 0 (Brand new HDD)
Disk 3: Reallocated Sector Count - 8, ATA Error Count - 0 (1 Year old HDD)
Disk 4: Reallocated Sector Count - 27, ATA Error Count - 0 (1 Year old HDD)
Disk 5: Reallocated Sector Count - 9, ATA Error Count - 0 (1 Year old HDD)
Disk 6: Reallocated Sector Count - 41, ATA Error Count - 0 (1 Year old HDD)
That got me thinking that, yep, those 1 year old HDDs must be having some issues, so I downloaded all the logs from the ReadyNAS, and in the system.log, I see a couple of curious entries:
This seems to pop up each time I reboot my NAS:
Oct 15 07:17:08 Media-Server kernel: ata3.00: WARNING: device requires firmware update to be fully functional.
Oct 15 07:17:08 Media-Server kernel: ata4.00: WARNING: device requires firmware update to be fully functional.
Oct 15 07:17:08 Media-Server kernel: ata5.00: WARNING: device requires firmware update to be fully functional.
Oct 15 07:17:08 Media-Server kernel: ata6.00: WARNING: device requires firmware update to be fully functional.
And this seems to happen when the streaming stops and the ReadyNAS becomes unreponsive:
Oct 15 08:26:04 Media-Server kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Oct 15 08:26:04 Media-Server kernel: ata3.00: failed command: FLUSH CACHE EXT
Oct 15 08:26:04 Media-Server kernel: ata3.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
Oct 15 08:26:04 Media-Server kernel: res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Oct 15 08:26:04 Media-Server kernel: ata3.00: status: { DRDY }
Oct 15 08:26:04 Media-Server kernel: ata3: hard resetting link
Oct 15 08:26:04 Media-Server kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Oct 15 08:26:04 Media-Server kernel: ata4.00: failed command: FLUSH CACHE EXT
Oct 15 08:26:04 Media-Server kernel: ata4.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
Oct 15 08:26:04 Media-Server kernel: res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Oct 15 08:26:04 Media-Server kernel: ata4.00: status: { DRDY }
Oct 15 08:26:04 Media-Server kernel: ata4: hard resetting link
Oct 15 08:26:04 Media-Server kernel: ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Oct 15 08:26:04 Media-Server kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Oct 15 08:26:04 Media-Server kernel: ata3.00: configured for UDMA/133
Oct 15 08:26:04 Media-Server kernel: ata3.00: retrying FLUSH 0xea Emask 0x4
Oct 15 08:26:04 Media-Server kernel: ata4.00: configured for UDMA/133
Oct 15 08:26:04 Media-Server kernel: ata4.00: retrying FLUSH 0xea Emask 0x4
Oct 15 08:26:04 Media-Server kernel: ata3.00: device reported invalid CHS sector 0
Oct 15 08:26:04 Media-Server kernel: ata3: EH complete
Oct 15 08:26:04 Media-Server kernel: ata4.00: device reported invalid CHS sector 0
Oct 15 08:26:04 Media-Server kernel: ata4: EH complete
Oct 15 08:27:31 Media-Server kernel: ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Oct 15 08:27:31 Media-Server kernel: ata6.00: failed command: FLUSH CACHE EXT
Oct 15 08:27:31 Media-Server kernel: ata6.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
Oct 15 08:27:31 Media-Server kernel: res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Oct 15 08:27:31 Media-Server kernel: ata6.00: status: { DRDY }
Oct 15 08:27:31 Media-Server kernel: ata6: hard resetting link
Oct 15 08:27:31 Media-Server kernel: ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Oct 15 08:27:32 Media-Server kernel: ata6.00: configured for UDMA/133
Oct 15 08:27:32 Media-Server kernel: ata6.00: retrying FLUSH 0xea Emask 0x4
Oct 15 08:27:32 Media-Server kernel: ata6.00: device reported invalid CHS sector 0
Oct 15 08:27:32 Media-Server kernel: ata6: EH complete
Oct 15 08:29:47 Media-Server kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Oct 15 08:29:47 Media-Server kernel: ata4.00: failed command: FLUSH CACHE EXT
Oct 15 08:29:47 Media-Server kernel: ata4.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
Oct 15 08:29:47 Media-Server kernel: res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Oct 15 08:29:47 Media-Server kernel: ata4.00: status: { DRDY }
Oct 15 08:29:47 Media-Server kernel: ata4: hard resetting link
Oct 15 08:29:47 Media-Server kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Oct 15 08:29:47 Media-Server kernel: ata4.00: configured for UDMA/133
Oct 15 08:29:47 Media-Server kernel: ata4.00: retrying FLUSH 0xea Emask 0x4
Oct 15 08:29:47 Media-Server kernel: ata4.00: device reported invalid CHS sector 0
Oct 15 08:29:47 Media-Server kernel: ata4: EH complete
Oct 15 09:27:24 Media-Server kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Oct 15 09:27:24 Media-Server kernel: ata5.00: failed command: FLUSH CACHE EXT
Oct 15 09:27:24 Media-Server kernel: ata5.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
Oct 15 09:27:24 Media-Server kernel: res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Oct 15 09:27:24 Media-Server kernel: ata5.00: status: { DRDY }
Oct 15 09:27:24 Media-Server kernel: ata5: hard resetting link
Oct 15 09:27:24 Media-Server kernel: ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Oct 15 09:27:24 Media-Server kernel: ata5.00: configured for UDMA/133
Oct 15 09:27:24 Media-Server kernel: ata5.00: retrying FLUSH 0xea Emask 0x4
Oct 15 09:27:24 Media-Server kernel: ata5.00: device reported invalid CHS sector 0
Oct 15 09:27:24 Media-Server kernel: ata5: EH complete
Oct 15 12:11:08 Media-Server kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Oct 15 12:11:08 Media-Server kernel: ata4.00: failed command: FLUSH CACHE EXT
Oct 15 12:11:08 Media-Server kernel: ata4.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
Oct 15 12:11:08 Media-Server kernel: res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Oct 15 12:11:08 Media-Server kernel: ata4.00: status: { DRDY }
Oct 15 12:11:08 Media-Server kernel: ata4: hard resetting link
Oct 15 12:11:08 Media-Server kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Oct 15 12:11:08 Media-Server kernel: ata4.00: configured for UDMA/133
Oct 15 12:11:08 Media-Server kernel: ata4.00: retrying FLUSH 0xea Emask 0x4
Oct 15 12:11:08 Media-Server kernel: ata4.00: device reported invalid CHS sector 0
Oct 15 12:11:08 Media-Server kernel: ata4: EH complete
Oct 15 12:11:08 Media-Server cnid_dbd[7615]: read: Connection reset by peer
Oct 15 12:11:08 Media-Server cnid_dbd[7615]: error reading message header: Connection reset by peer
Oct 15 12:12:29 Media-Server kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Oct 15 12:12:29 Media-Server kernel: ata3.00: failed command: FLUSH CACHE EXT
Oct 15 12:12:29 Media-Server kernel: ata3.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
Oct 15 12:12:29 Media-Server kernel: res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Oct 15 12:12:29 Media-Server kernel: ata3.00: status: { DRDY }
Oct 15 12:12:29 Media-Server kernel: ata3: hard resetting link
Oct 15 12:12:29 Media-Server kernel: ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Oct 15 12:12:29 Media-Server kernel: ata3.00: configured for UDMA/133
Oct 15 12:12:29 Media-Server kernel: ata3.00: retrying FLUSH 0xea Emask 0x4
Oct 15 12:12:29 Media-Server kernel: ata3.00: device reported invalid CHS sector 0
Oct 15 12:12:29 Media-Server kernel: ata3: EH complete
Oct 15 12:12:29 Media-Server cnid_dbd[7615]: read: Connection reset by peer
Oct 15 12:12:29 Media-Server cnid_dbd[7615]: error reading message header: Connection reset by peer
Oct 15 12:17:17 Media-Server kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Oct 15 12:17:17 Media-Server kernel: ata5.00: failed command: FLUSH CACHE EXT
Oct 15 12:17:17 Media-Server kernel: ata5.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
Oct 15 12:17:17 Media-Server kernel: res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Oct 15 12:17:17 Media-Server kernel: ata5.00: status: { DRDY }
Oct 15 12:17:17 Media-Server kernel: ata5: hard resetting link
Oct 15 12:17:17 Media-Server kernel: ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Oct 15 12:17:17 Media-Server kernel: ata5.00: configured for UDMA/133
Oct 15 12:17:17 Media-Server kernel: ata5.00: retrying FLUSH 0xea Emask 0x4
Oct 15 12:17:17 Media-Server kernel: ata5.00: device reported invalid CHS sector 0
Oct 15 12:17:17 Media-Server kernel: ata5: EH complete
So it seems pretty clear at this point that the ReadyNAS is not very happy with the status of Drives 3-6.
My plan of attack at this point was to attempt to upgrade the firmware on those drives, and then see if the performance is any better and those warnings/errors disappear.
Failing that, I would plan on swapping out the 1 year old drives with new drives on the compatibility list, one at a time, letting the RAID rebuild, and once complete with new drives, see if the performance gets better.
So now my questions are:
1) Any way to upgrade the firmware of the drives now that they are in the ReadyNAS?
2) If not, can I pull the drives, put them into a USB enclosure, and upgrade the firmware by direct attaching them to a Mac or PC, without messing up the data they contain?
3) Thoughts on my plan of attack?
I suppose worst case, I just take the RAID offline, upgrade the firmware of the drives on another machine, then rebuild the RAID once that has been done, and move my data back over to the RAID. I just hate to do that since I spent such a long time copying everything over.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
