warri
Guru
- Joined
- Jun 6, 2011
- Messages
- 1,193
Hi all!
Some days ago my NAS fell down about 50 cm to the floor (due to a not properly mounted wall board - stupid thing) while I was accessing data on it.
Luckily just one HDD died completely (click of death) and I had some spare drives left. I tried replacing the hard disk via the GUI first, but that yielded in some big error about a String which couldn't be parsed correctly.
So I went on to the CLI and followed the inofficial FAQ and the official FAQ.
First I removed the bad drive, put in the replacement at the same sata port, and began the resilvering process. It completed successfully after ~15 hours.
Now my pool status is HEALTHY again, but there are some read errors on two other drives:
I'm getting following smart errors:
So probably those drives also are slightly damaged (they correspond to the 2 drives with read errors from the zpool report). Can't the drives just flag those sectors as damaged and ignore them in future? Or do I need to replace them as well? Should I just clear the errors and scrub again?
Also the name of the new drive is ada2 instead of the unique ID (probably because I typed zpool replace tank1 <oldid> ada2 for the resilvering to start). In the GUI it say {serial}... instead of {uuid}.., see attached screenshot.
So the two main quesions which bug me:
Thanks for your help in advance! The FAQ's and other threads already helped a lot :)
[edit]
After looking around in the bug reports, I found this ticket: https://support.freenas.org/ticket/744
It addresses the ID issue, and according to the ticket it just seems to be a cosmetic issue.
Some days ago my NAS fell down about 50 cm to the floor (due to a not properly mounted wall board - stupid thing) while I was accessing data on it.
Luckily just one HDD died completely (click of death) and I had some spare drives left. I tried replacing the hard disk via the GUI first, but that yielded in some big error about a String which couldn't be parsed correctly.
So I went on to the CLI and followed the inofficial FAQ and the official FAQ.
First I removed the bad drive, put in the replacement at the same sata port, and began the resilvering process. It completed successfully after ~15 hours.
Now my pool status is HEALTHY again, but there are some read errors on two other drives:
Code:
pool: tank1 state: ONLINE status: One or more devices has experienced an unrecoverable error. An attempt was made to correct the error. Applications are unaffected. action: Determine if the device needs to be replaced, and clear the errors using 'zpool clear' or replace the device with 'zpool replace'. see: http://www.sun.com/msg/ZFS-8000-9P scrub: resilver completed after 15h50m with 0 errors on Sat Dec 17 04:09:18 2011 config: NAME STATE READ WRITE CKSUM tank1 ONLINE 8 0 0 raidz1 ONLINE 8 0 0 gptid/9c4114e4-9143-11e0-820f-485d6094a16a ONLINE 0 0 0 gptid/9cf38c6a-9143-11e0-820f-485d6094a16a ONLINE 4 0 0 ada2 ONLINE 0 0 0 1.17T resilvered gptid/9e389f0f-9143-11e0-820f-485d6094a16a ONLINE 0 0 0 gptid/9efe636a-9143-11e0-820f-485d6094a16a ONLINE 0 0 0 gptid/9fc77be7-9143-11e0-820f-485d6094a16a ONLINE 4 0 0 errors: No known data errors
I'm getting following smart errors:
Code:
Dec 17 10:41:28 freenas smartd[3181]: Device: /dev/ada1, 5 Currently unreadable (pending) sectors Dec 17 10:41:29 freenas smartd[3181]: Device: /dev/ada6, 4 Currently unreadable (pending) sectors
So probably those drives also are slightly damaged (they correspond to the 2 drives with read errors from the zpool report). Can't the drives just flag those sectors as damaged and ignore them in future? Or do I need to replace them as well? Should I just clear the errors and scrub again?
Also the name of the new drive is ada2 instead of the unique ID (probably because I typed zpool replace tank1 <oldid> ada2 for the resilvering to start). In the GUI it say {serial}... instead of {uuid}.., see attached screenshot.
So the two main quesions which bug me:
- What to do about the id of the new drive?
- Do I need to replace the other two disks as well?
Thanks for your help in advance! The FAQ's and other threads already helped a lot :)
[edit]
After looking around in the bug reports, I found this ticket: https://support.freenas.org/ticket/744
It addresses the ID issue, and according to the ticket it just seems to be a cosmetic issue.