SwisherSweet
Contributor
- Joined
- May 13, 2017
- Messages
- 139
Hi,
I got two CRITICAL alerts today from FreeNAS:
Based on my research in this forum and abroad, it appears the drive has some bad sectors. However, many of the posts suggest that ZFS/FreeNAS can't really deal with this and one must us dd to write data to these bad sectors for it to reallocate data. Now these posts were pretty old, so I'm hoping that is no longer the case.
Does FreeNAS 9.10.2 handle this type of problem now? Or, does one have to constantly check for, and manually deal with bad sectors each time one or more pop-up? If the answer is the later, I'll be confounded since I never had to deal with this with my Drobo. Perhaps the Drobo just showed the drive as bad when it encounter a bad sector... I don't know. But I was never asked to locate and deal with bad sectors myself.
I got two CRITICAL alerts today from FreeNAS:
- CRITICAL: July 11, 2017, 2:03 a.m. - Device: /dev/ada17, 8 Currently unreadable (pending) sectors
- CRITICAL: July 11, 2017, 2:33 a.m. - Device: /dev/ada17, 2 Offline uncorrectable sectors
Based on my research in this forum and abroad, it appears the drive has some bad sectors. However, many of the posts suggest that ZFS/FreeNAS can't really deal with this and one must us dd to write data to these bad sectors for it to reallocate data. Now these posts were pretty old, so I'm hoping that is no longer the case.
Does FreeNAS 9.10.2 handle this type of problem now? Or, does one have to constantly check for, and manually deal with bad sectors each time one or more pop-up? If the answer is the later, I'll be confounded since I never had to deal with this with my Drobo. Perhaps the Drobo just showed the drive as bad when it encounter a bad sector... I don't know. But I was never asked to locate and deal with bad sectors myself.
Last edited: