NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ReadyNas PRO6 hangs when BulkCopy
Hello
when I copy a huge amount of data or files (e.g. VMWare Images or photos) to my readynas pro it often hangs and goes on copying this files after a while (about 1Minute delay)
- JumboFrames are deactivated on my TestPC and are also deactivated on the NAS
- occours also when I map it as Network-Drive
- have already tested three different Switches - no diff... (NetGear GS724TS, Zyxel GS2200, D-Link DGS-1008D)
- also with differnt PC's
What can I do?
Logs are for Download at
http://www.bernhard-hartl.com/Share/System_log-NAS-20130528-010004.zip
thank you
Bernhard Hartl
when I copy a huge amount of data or files (e.g. VMWare Images or photos) to my readynas pro it often hangs and goes on copying this files after a while (about 1Minute delay)
- JumboFrames are deactivated on my TestPC and are also deactivated on the NAS
- occours also when I map it as Network-Drive
- have already tested three different Switches - no diff... (NetGear GS724TS, Zyxel GS2200, D-Link DGS-1008D)
- also with differnt PC's
What can I do?
Logs are for Download at
http://www.bernhard-hartl.com/Share/System_log-NAS-20130528-010004.zip
thank you
Bernhard Hartl
19 Replies
Replies have been turned off for this discussion
- Bernard,
I have briefly looked at logs.
Disk logs are fine. No packet drops.
The only comment I can make is that NAS is 85% full, and in that
state, the NAS takes longer to find space, to accomodate data.
You could try copying the same file size when NAS is 50% full, for comparison.
Status -old is in German, so I cannot interpret.
Goodnight,
Marto - Thank you for your respons Marto
OK - I'll move Data to an other location and try again
good night
Bernhard - Disk 1 is having issues, or the backplane is failing.
May 26 17:58:26 NAS kernel: ata1.00: exception Emask 0x0 SAct 0x7fffffff SErr 0x0 action 0x0
May 26 17:58:26 NAS kernel: ata1.00: irq_stat 0x40000008
May 26 17:58:26 NAS kernel: ata1.00: failed command: READ FPDMA QUEUED
May 26 17:58:26 NAS kernel: ata1.00: cmd 60/08:40:b5:7e:c7/00:00:09:00:00/40 tag 8 ncq 4096 in
May 26 17:58:26 NAS kernel: res 41/40:00:b5:7e:c7/00:00:09:00:00/40 Emask 0x409 (media error) <F>
May 26 17:58:26 NAS kernel: ata1.00: status: { DRDY ERR }
May 26 17:58:26 NAS kernel: ata1.00: error: { UNC }
May 26 17:58:26 NAS kernel: ata1.00: configured for UDMA/133
May 26 17:58:26 NAS kernel: ata1: EH complete
May 26 17:58:26 NAS kernel: ata1.00: exception Emask 0x0 SAct 0x7fffffff SErr 0x0 action 0x0
May 26 17:58:26 NAS kernel: ata1.00: irq_stat 0x40000008
May 26 17:58:26 NAS kernel: ata1.00: failed command: READ FPDMA QUEUED
May 26 17:58:26 NAS kernel: ata1.00: cmd 60/08:b0:b5:7e:c7/00:00:09:00:00/40 tag 22 ncq 4096 in
May 26 17:58:26 NAS kernel: res 41/40:00:b5:7e:c7/00:00:09:00:00/40 Emask 0x409 (media error) <F>
May 26 17:58:26 NAS kernel: ata1.00: status: { DRDY ERR }
May 26 17:58:26 NAS kernel: ata1.00: error: { UNC }
May 26 17:58:26 NAS kernel: ata1.00: configured for UDMA/133
May 26 17:58:26 NAS kernel: ata1: EH complete
May 26 17:58:26 NAS kernel: ata1.00: exception Emask 0x0 SAct 0x7fffffff SErr 0x0 action 0x0
May 26 17:58:26 NAS kernel: ata1.00: irq_stat 0x40000008
May 26 17:58:26 NAS kernel: ata1.00: failed command: READ FPDMA QUEUED
May 26 17:58:26 NAS kernel: ata1.00: cmd 60/08:40:b5:7e:c7/00:00:09:00:00/40 tag 8 ncq 4096 in
May 26 17:58:26 NAS kernel: res 41/40:00:b5:7e:c7/00:00:09:00:00/40 Emask 0x409 (media error) <F>
May 26 17:58:26 NAS kernel: ata1.00: status: { DRDY ERR }
May 26 17:58:26 NAS kernel: ata1.00: error: { UNC }
May 26 17:58:26 NAS kernel: ata1.00: configured for UDMA/133
May 26 17:58:26 NAS kernel: ata1: EH complete
May 26 17:58:26 NAS kernel: ata1.00: exception Emask 0x0 SAct 0x7fffffff SErr 0x0 action 0x0
May 26 17:58:26 NAS kernel: ata1.00: irq_stat 0x40000008
May 26 17:58:26 NAS kernel: ata1.00: failed command: READ FPDMA QUEUED
May 26 17:58:26 NAS kernel: ata1.00: cmd 60/08:b0:b5:7e:c7/00:00:09:00:00/40 tag 22 ncq 4096 in
May 26 17:58:26 NAS kernel: res 41/40:00:b5:7e:c7/00:00:09:00:00/40 Emask 0x409 (media error) <F>
May 26 17:58:26 NAS kernel: ata1.00: status: { DRDY ERR }
May 26 17:58:26 NAS kernel: ata1.00: error: { UNC }
May 26 17:58:26 NAS kernel: ata1.00: configured for UDMA/133
May 26 17:58:26 NAS kernel: ata1: EH complete
May 26 17:58:26 NAS kernel: ata1.00: exception Emask 0x0 SAct 0x7fffffff SErr 0x0 action 0x0
May 26 17:58:26 NAS kernel: ata1.00: irq_stat 0x40000008
May 26 17:58:26 NAS kernel: ata1.00: failed command: READ FPDMA QUEUED
May 26 17:58:26 NAS kernel: ata1.00: cmd 60/08:40:b5:7e:c7/00:00:09:00:00/40 tag 8 ncq 4096 in
May 26 17:58:26 NAS kernel: res 41/40:00:b5:7e:c7/00:00:09:00:00/40 Emask 0x409 (media error) <F>
May 26 17:58:26 NAS kernel: ata1.00: status: { DRDY ERR }
May 26 17:58:26 NAS kernel: ata1.00: error: { UNC }
May 26 17:58:26 NAS kernel: ata1.00: configured for UDMA/133
May 26 17:58:26 NAS kernel: ata1: EH complete
May 26 17:58:26 NAS kernel: ata1.00: exception Emask 0x0 SAct 0x7fffffff SErr 0x0 action 0x0
May 26 17:58:26 NAS kernel: ata1.00: irq_stat 0x40000008
May 26 17:58:26 NAS kernel: ata1.00: failed command: READ FPDMA QUEUED
May 26 17:58:26 NAS kernel: ata1.00: cmd 60/08:b0:b5:7e:c7/00:00:09:00:00/40 tag 22 ncq 4096 in
May 26 17:58:26 NAS kernel: res 41/40:00:b5:7e:c7/00:00:09:00:00/40 Emask 0x409 (media error) <F>
May 26 17:58:26 NAS kernel: ata1.00: status: { DRDY ERR }
May 26 17:58:26 NAS kernel: ata1.00: error: { UNC }
May 26 17:58:26 NAS kernel: ata1.00: configured for UDMA/133
May 26 17:58:26 NAS kernel: sd 0:0:0:0: [sda] Unhandled sense code
May 26 17:58:26 NAS kernel: sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
May 26 17:58:26 NAS kernel: sd 0:0:0:0: [sda] Sense Key : Medium Error [current] [descriptor]
May 26 17:58:26 NAS kernel: Descriptor sense data with sense descriptors (in hex):
May 26 17:58:26 NAS kernel: 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
May 26 17:58:26 NAS kernel: 09 c7 7e b5
May 26 17:58:26 NAS kernel: sd 0:0:0:0: [sda] Add. Sense: Unrecovered read error - auto reallocate failed
May 26 17:58:26 NAS kernel: sd 0:0:0:0: [sda] CDB: Read(10): 28 00 09 c7 7e b5 00 00 08 00
May 26 17:58:26 NAS kernel: end_request: I/O error, dev sda, sector 164069045
May 26 17:58:26 NAS kernel: ata1: EH complete
May 26 17:58:26 NAS kernel: md/raid:md2: read error corrected (8 sectors at 154631856 on sda5) Marto73 wrote: The only comment I can make is that NAS is 85% full, and in that
state, the NAS takes longer to find space, to accomodate data.
You could try copying the same file size when NAS is 50% full, for comparison.
Hello Marto
you are right
have moved Data from the NAS to an other location
no it works perfect again
THANK YOU
Bernhard- What's more likely here is now with less data on the volume, you aren't hitting the 'bad spot' on Disk 1, so the hang doesn't occur.
From those logs I pasted above, you still have issues on that hardware.
Agreed.chirpa wrote: What's more likely here is now with less data on the volume, you are't hitting the 'bad spot' on Disk 1, so the hang doesn't occur.
From those logs I pasted above, you still have issues on that hardware.
Bernard - did you look at the SMART+ stats for the drives (particularly disk 1)?- SMART doesn't look out of place. I suggest a full disk test with the manufacturers diagnostic tools. If that is still clean, may point to backplane issue in the ReadyNAS itself.
And to Marto, are you suggesting that all the ReadyNAS platforms using EXT4 filesystem have the 80%+ issue like the DuoV2 initially pointed out? If all systems become unstable at 85%+ disk usage, that is a big problem. chirpa wrote: And to Marto, are you suggesting that all the ReadyNAS platforms using EXT4 filesystem have the 80%+ issue like the DuoV2 initially pointed out? If all systems become unstable at 85%+ disk usage, that is a big problem.
That is for shure a NetGear Problem as I have got two identical NAS Pro6
one is the Backup of the other one
and the second one has got the same problem - hanging when the bulk-copy starts
Bernhard
PS. I have ordered some Disks to upgrade the NAS
I'll start with Disk 1 and check it afterwards...- Chirpa,
Points taken. How do you interpret from the Kernal code that there
is possibly a Disk 1 fault.?
Thank you, Marto - Those lines were from further up in his log files, not in the last reboot where he had to reboot from hang to get the logs.
For the specific errors, I don't know enough to diagnose them in detail, just know they aren't good to see. Maybe have Marcus check with Wei for detailed analysis.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
