FYI, both hard drives and SSDs internally reallocate defective sectors onto working ones when the problem "block" is written over (it is really just an address, and it changes out the physical storage location backing it). With SSDs it is actually more internally complex than hard drives, but the principle is the same: the OS doesn't track the defective sectors, the drive does, and fills in with spare working sectors when it gets new data, so the OS doesn't have to care. This is what the "current pending sectors", "offline uncorrectable", etc in the SMART attributes mean.
For hard drives, some sectors going bad is an early sign that there may be a catastrophic failure in the near future. For SSDs, it isn't as clear what it means - it could be a one-time event from unexpected power loss, if the drive isn't robust to that (some drive models are designed to handle it, others lose recent writes, and some become bricks), or being powered off for a very long time, or outside its temperature range, or it could be manufacturing defects, etc. Tim ________________________________ From: Marc Lobelle <[email protected]> Sent: Thursday, March 10, 2022 4:09 AM To: Toomas Soome via openindiana-discuss <[email protected]> Subject: Re: [OpenIndiana-discuss] io errors in rpool, was surprising error when I try to install a package WARNING: This message has originated from an External Source. This may be a phishing expedition that can result in unauthorized access to our IT System. Please use proper judgment and caution when opening attachments, clicking links, or responding to this email. Hi Toomas, Indeed I have problems with the local storage. This notebook has a single ssd drive (rpool) and scrubbing it finds unrecoverable errors ml@mosquito:/export/home/ml# zpool status -v pool: rpool state: DEGRADED status: One or more devices has experienced an error resulting in data corruption. Applications may be affected. action: Restore the file in question if possible. Otherwise restore the entire pool from backup. see: https://nam02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fillumos.org%2Fmsg%2FZFS-8000-8A&data=04%7C01%7Ctsc5yc%40mst.edu%7Ccf37e7e3825c491d0a0508da027e138c%7Ce3fefdbef7e9401ba51a355e01b05a89%7C0%7C0%7C637825038199891448%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=ZyewsG4qTnB2yrH%2FSYaXn2FhHm2mV5sfMCvWPbL8vhQ%3D&reserved=0 scan: scrub in progress since Wed Mar 9 18:41:08 2022 141G scanned at 179M/s, 31,0G issued at 39,2M/s, 142G total 0 repaired, 21,91% done, 0 days 00:48:07 to go config: NAME STATE READ WRITE CKSUM rpool DEGRADED 2 0 3 c6t0d0s0 DEGRADED 2 0 6 too many errors errors: Permanent errors have been detected in the following files: rpool/ROOT/openindiana-2022:02:16:<0x881c0> rpool/dump:<0x1> rpool/swap:<0x1> /export/home/ml/.local/share/Trash/files/Capture du 2022-03-03 15-11-12.png rpool/export/home/ml:<0x147d> rpool/ROOT/openindiana-2022:02:16@2022-03-04-09:38:53:/var/pkg/state/known/catalog.summary.C rpool/ROOT/openindiana-2022:02:16@2022-03-04-09:38:53:/var/pkg/state/known/catalog.dependency.C rpool/ROOT/openindiana-2022:02:16@install:/usr/share/doc/dbus/api/group__DBusMessageInternals.html rpool/ROOT/openindiana-2022:02:16@install:/usr/share/doc/libsigc++-2.0/reference/html/inherit_graph_24.png rpool/ROOT/openindiana-2022:02:16@install:/usr/share/doc/libsigc++-2.0/reference/html/modules.html Loosing a few blocks on a 1 TB ssd is acceptable if the OS can avoid using these faulty blocks in the future. What does zpool do if I do a zpool clear: the faults will disappear from the status but will the faulty blocs be avoided henceforth ? The corrupted files are lost but, if I do "pkg refresh --full; pkg update -v", I assume they will be replaced. However if the faulty blocks are not removed from the list of usable blocks, the faults will happen again and the drive must be considered as lost and to be replaced On 3/9/22 09:22, Toomas Soome via openindiana-discuss wrote: >> On 9. Mar 2022, at 10:15, Marc Lobelle<[email protected]> wrote: >> >> Hello, >> >> I got a surprising error when trying to install packages (any package, even >> xeyes) on one of my computers running openindiana: *Error encountered while >> retrieving data from: [Errno 5] I/O error.* >> >> Anybody knows what to do ? >> >> Thanks and best regards >> >> Marc > there are two possible causes, either it is some sort of network issue (truss > -f pkg…. and see what will get EIO), or it is issue with local storage (zpool > scrub?). > > rgds, > toomas > > > _______________________________________________ > openindiana-discuss mailing list > [email protected] > https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fopenindiana.org%2Fmailman%2Flistinfo%2Fopenindiana-discuss&data=04%7C01%7Ctsc5yc%40mst.edu%7Ccf37e7e3825c491d0a0508da027e138c%7Ce3fefdbef7e9401ba51a355e01b05a89%7C0%7C0%7C637825038199891448%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=zzcKHiUiUlNnT6nHf2DZHvB74%2FwrboHx%2FQjclxLaXvU%3D&reserved=0 _______________________________________________ openindiana-discuss mailing list [email protected] https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fopenindiana.org%2Fmailman%2Flistinfo%2Fopenindiana-discuss&data=04%7C01%7Ctsc5yc%40mst.edu%7Ccf37e7e3825c491d0a0508da027e138c%7Ce3fefdbef7e9401ba51a355e01b05a89%7C0%7C0%7C637825038199891448%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=zzcKHiUiUlNnT6nHf2DZHvB74%2FwrboHx%2FQjclxLaXvU%3D&reserved=0 _______________________________________________ openindiana-discuss mailing list [email protected] https://openindiana.org/mailman/listinfo/openindiana-discuss
