Thanks for all the suggestions. Just to review, the issue was the drive didn't even appear in lsblk, so nothing can be done to fix it. It is possible it was partially failing, it seems after multiple windows reboots and repairs it is working again, although at least one app had to be reinstalled. I only use linux myself, so I know nothing about windows or how to diagnose it. So my real question was not how to fix the drive, but why it doesn't even show up on linux. Thanks Neal
On Sat, May 30, 2020 at 6:26 PM George N. White III <gnw...@gmail.com> wrote: > On Sat, 30 May 2020 at 10:37, Neal Becker <ndbeck...@gmail.com> wrote: > >> Today my wife's windows10 lenovo laptop was not starting normally, >> cycling through various "repair" screens. It does seem to work at least >> minimally though. >> > > I've seen this with older version of Windows. The "repair" may have > repaired the "original" Windows boot configuration, but the > need for the repair is most likely due to a failing drive. Using the USB > live stick you should be able to install smartmontools to check the drive. > > >> I tried booting of my f32 usb stick and thought maybe I could take a look >> at the SSD. But when I start gnome disks, the internal SSD doesn't >> show up! lsblk doesn't show it. I looked through journalctl and saw >> some reference to ATA1, and I believe some kind of error. >> >> Anyone have any idea what's going on? The SSD is working enough to boot >> windows and run various things like file manager, so why doesn't it >> show in linux? >> > > Windows may have messed with "BIOS" settings in an attempt to recover from > a problem. > > How old is the drive? SSD bits have a limited lifetime. Some workloads > (video production) that fill, empty, and refill the drive very hard on > SSD's. Wear leveling strategies try to make the wear even across all the > bits, and there are spares when a bit goes bad, but eventually the spares > are used up and you lose data in some high-wear area. You should use > ddrescue to image the drive and attempt repairs on the image rather than > tying to do repairs on a failing drive. > > -- > George N. White III > > _______________________________________________ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org > -- *Those who don't understand recursion are doomed to repeat it*
_______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
