theone Posted September 28, 2010 Share Posted September 28, 2010 Hello, I just noticed that I have the following 2 errors/warnings under smart history in unMenu: Disk 1: OK - Reallocated_Event_Count is 0 Disk 1: *ERROR* - Current_Pending_Sector has increased from 0 to 1 since 2010-09-09 Disk 1: WARNING - Current_Pending_Sector it is now 1 (warning threshold is 1) After running samrt history again I get only the warning message: Disk 1: WARNING - Current_Pending_Sector it is now 1 (warning threshold is 1) What does it mean? Should it be fixed? What is the best way to fix it? Link to comment
Joe L. Posted September 28, 2010 Share Posted September 28, 2010 Hello, I just noticed that I have the following 2 errors/warnings under smart history in unMenu: Disk 1: OK - Reallocated_Event_Count is 0 Disk 1: *ERROR* - Current_Pending_Sector has increased from 0 to 1 since 2010-09-09 Disk 1: WARNING - Current_Pending_Sector it is now 1 (warning threshold is 1) After running samrt history again I get only the warning message: Disk 1: WARNING - Current_Pending_Sector it is now 1 (warning threshold is 1) What does it mean? Should it be fixed? What is the best way to fix it? One of the sectors on disk1 is not readable, and the SMART firmware has marked it for possible re-allocation the next time it is written to. The fix would be to re-write that sector. You do not know which sector. Even if you did, you have no way of knowing which file or file-system structure it might be affiliated with. So... there is nothing you really can do. Typically unRAID will re-write those sectors if it detects on in its access of the disk. I can only guess that the disk detected it on its own, possibly as a result of you requesting a long or short test of it. Most large modern disks have several thousand spare sectors... If you see the number of re-allocated sectors increasing rapidly, it is time to RMA the disk. Link to comment
theone Posted September 28, 2010 Author Share Posted September 28, 2010 One of the sectors on disk1 is not readable, and the SMART firmware has marked it for possible re-allocation the next time it is written to. The fix would be to re-write that sector. You do not know which sector. Even if you did, you have no way of knowing which file or file-system structure it might be affiliated with. So... there is nothing you really can do. Typically unRAID will re-write those sectors if it detects on in its access of the disk. I can only guess that the disk detected it on its own, possibly as a result of you requesting a long or short test of it. Most large modern disks have several thousand spare sectors... If you see the number of re-allocated sectors increasing rapidly, it is time to RMA the disk. I did not run any disk test except the smart history report. Is there data on that sector or has the data already been relocated? Did I loose parts of my data? Link to comment
Joe L. Posted September 28, 2010 Share Posted September 28, 2010 One of the sectors on disk1 is not readable, and the SMART firmware has marked it for possible re-allocation the next time it is written to. The fix would be to re-write that sector. You do not know which sector. Even if you did, you have no way of knowing which file or file-system structure it might be affiliated with. So... there is nothing you really can do. Typically unRAID will re-write those sectors if it detects on in its access of the disk. I can only guess that the disk detected it on its own, possibly as a result of you requesting a long or short test of it. Most large modern disks have several thousand spare sectors... If you see the number of re-allocated sectors increasing rapidly, it is time to RMA the disk. I did not run any disk test except the smart history report. Perhaps, but the disk itself is constantly reading, and buffering whole cylinders of data... It might have detected the un-readable sector on its own. Is there data on that sector"No way to know, remember, it was un-readable or has the data already been relocated?It would not be pending re-allocation if it had already been re-allocated. The disk is waiting for that sector to be written again. Then it will re-try using it first, and if un-successful, it will re-allocate a sector from its pool of reserve sectors. Did I loose parts of my data? No way to know... but we can guess. Did you see any "read" errors on the web-management interface? I think it is unlikely you lost anything, since if unRAID detected the un-readable sector it would have re-constructed the sector from parity and the other data disks and then written it back to the un-readable drive. That would either fix the sector that was poorly written, or it would force the re-allocation to occur. IT would also have shown as a "read" error on the management console for that drive. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.