NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Tomahna
Dec 30, 2018Aspirant
Readynas Ultra 4 RAID 5 - 2 of 4 disks fail at the same time
Before I was able to replace the disks (for which smart disk errors were reported previously), the next reboot gave me an unrecoverable disk problem (End of Life error). Checking the fs_check log, re...
Marc_V
Jan 02, 2019NETGEAR Employee Retired
Hi Tomahna
Happy New Year!
We wouldn't recommend doing any further action as this might cause much more damage on recovery of data.
I would suggest to try and get the data off the disks through Data recovery software or service and try to clone the disks. Contacting Support for assistance on this is also advisable though Data Recovery and Support might need to be purchased. You can login to my.netgear.com and create a case for your product so the experts can assist you on escalating the case.
Have you checked which of the 2 disks failed the last? This might be needed for re-assembling the RAID.
Hope this helps!
Regards
Tomahna
Jan 02, 2019Aspirant
Hello Marc,
Thank you for your reply. I will check out my.netgear.com
PS both disks failed at exactly the same time, which I found rather suspious, but never the less the the problem remains the same. Unless another cause can be identified that would cause both disks to become unusbale (powersupply or driver), which can be recovered in another way.
Best regards,
Mark
- StephenBJan 02, 2019Guru - Experienced User
Tomahna wrote:
... gave me an unrecoverable disk problem (End of Life error).
...PS disks failed at exactly the same time, which I found rather suspious,
"End of Life" isn't a SMART statistic, and it's not an error I've seen before from a NAS.
Are you sure this was the error?
Were these SSD disks?
Perhaps download the log zip file and/or query the disk status with smartctl.
- TomahnaJan 02, 2019Aspirant
The “End of life error” was displayed on the Ultra4 unit itself. I cannot find it in the log files.
They are not SSD disks:
- Disk 1 WD2003FYYS-23W0B0 42D0788 42D0791IBM 1863 GB
- Disk 2 WD2003FYYS-23W0B0 42D0788 42D0791IBM 1863 GB
- Disk 3 Seagate ST3000DM001-1ER166 2794 GB
- Disk 4 Seagate ST3000DM001-1ER166 2794 GBPlease find below some interesting snippets from the system.log file
(Also attached the log web-screen positioned form when the problem started.)
Aug 29 10:49:49 Serenia kernel: All bugs added by David S. Miller davem@redhat.com
Probably some kind of joke...
Jan 2 17:36:52 Serenia kernel: ata2.00: cmd 60/00:10:d8:b4:26/01:00:27:00:00/40 tag 2 ncq 131072 in
Jan 2 17:36:52 Serenia kernel: res 41/40:00:e0:b4:26/00:00:27:00:00/40 Emask 0x409 (media error) <F>A whole set of:
Jan 2 17:36:52 Serenia kernel: ata2.00: status: { DRDY ERR }
Jan 2 17:36:52 Serenia kernel: ata2.00: error: { UNC }
Jan 2 17:36:52 Serenia kernel: ata2.00: configured for UDMA/133
Jan 2 17:36:52 Serenia kernel: ata2: EH complete
Jan 2 17:36:52 Serenia kernel: ata2.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
Jan 2 17:36:52 Serenia kernel: ata2.00: irq_stat 0x40000008
Jan 2 17:36:52 Serenia kernel: ata2.00: failed command: READ FPDMA QUEUEDJan 2 17:36:52 Serenia kernel: bio: create slab <bio-1> at 1
Jan 2 17:36:52 Serenia kernel: md/raid1:md0: active with 4 out of 4 mirrors
Jan 2 17:36:52 Serenia kernel: md0: detected capacity change from 0 to 4294955008
Jan 2 17:36:52 Serenia kernel: md0: unknown partition table
Jan 2 17:36:52 Serenia kernel: md: bind<sdb2>Jan 2 17:36:52 Serenia kernel: md: using 128k window, over a total of 1948793216 blocks.
Jan 2 17:36:52 Serenia kernel: md2: unknown partition table
Jan 2 17:36:52 Serenia kernel: md: bind<sdd6>Unrecovered read error - auto reallocate failed
Jan 2 17:36:52 Serenia kernel: sd 0:0:0:0: [sda] CDB: Read(10): 28 00 27 26 b4 e0 00 00 f8 00
Jan 2 17:36:52 Serenia kernel: end_request: I/O error, dev sda, sector 656848098
Jan 2 17:36:52 Serenia kernel: md/raid:md2: read error not correctable (sector 647410928 on sda5).
Jan 2 17:36:52 Serenia kernel: md/raid:md2: Disk failure on sdb5, disabling device.
Jan 2 17:36:52 Serenia kernel: <1>md/raid:md2: Operation continuing on 3 devices.
Jan 2 17:36:52 Serenia kernel: md/raid:md2: Disk failure on sda5, disabling device.
Jan 2 17:36:52 Serenia kernel: <1>md/raid:md2: Operation continuing on 2 devices.
Jan 2 17:36:52 Serenia kernel: Buffer I/O error on device dm-0, logical block 242778913
Jan 2 17:36:52 Serenia kernel: md/raid:md2: read error not correctable (sector 647410936 on sda5).
Jan 2 17:36:52 Serenia kernel: md/raid:md2: read error not correctable (sector 647410944 on sda5).
Jan 2 17:36:52 Serenia kernel: md/raid:md2: read error not correctable (sector 647410952 on sda5).
Jan 2 17:36:52 Serenia kernel: Buffer I/O error on device dm-0, logical block 242778914
Jan 2 17:36:52 Serenia kernel: md/raid:md2: read error not correctable (sector 647410960 on sda5).
Jan 2 17:36:52 Serenia kernel: Buffer I/O error on device dm-0, logical block 242778915
Jan 2 17:36:52 Serenia kernel: md/raid:md2: read error not correctable (sector 647410968 on sda5).
Jan 2 17:36:52 Serenia kernel: Buffer I/O error on device dm-0, logical block 242778916
Jan 2 17:36:52 Serenia kernel: ata1: EH complete
Jan 2 17:36:52 Serenia kernel: md: md2: resync done.
Jan 2 17:36:52 Serenia kernel: md: checkpointing resync of md2.
Jan 2 17:36:52 Serenia kernel: RAID conf printout:
Jan 2 17:36:52 Serenia kernel: --- level:5 rd:4 wd:2
Jan 2 17:36:52 Serenia kernel: disk 0, o:0, dev:sda5
Jan 2 17:36:52 Serenia kernel: disk 1, o:0, dev:sdb5
Jan 2 17:36:52 Serenia kernel: disk 2, o:1, dev:sdc5
Jan 2 17:36:52 Serenia kernel: disk 3, o:1, dev:sdd5- StephenBJan 03, 2019Guru - Experienced User
The logical next step is to power down the NAS and test disks 1 and 2 in a Windows PC using WDC's lifeguard software. You can connect the disks using either SATA or a USB adapter/dock.
You could also try powering down, removing disk 1, and then try to boot without disk 1. I'm not seeing the details of the disk 2 failure in the log snippet, but there is plenty of evidence that disk 1 is struggling. So it's conceivable that the system would boot w/o disk 1. If it does, the next step is to backup the data. Do that before you do anything else.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!