Post as a guest Name. Email Required, but never shown. The Overflow Blog. Podcast Making Agile work for data science. Stack Gives Back Featured on Meta. New post summary designs on greatest hits now, everywhere else eventually. Related 7. Hot Network Questions. Question feed. Then a few minutes to hours later, we can ask for the results of those tests. February 1st, 5. Some smartctl output I didn't see output of the first smartctl command so I searched online and ran some other smartctl commands Code:.
February 1st, 6. You can exclude snaps in partition list: exclude snaps lsblk -af grep -sv loop I have deleted all my snaps, so cannot test above, but posted previously. February 2nd, 7. So, if sda is the problem disk and SMART data isn't working for it, and you've addressed the possible issues in my list above, and sda still doesn't work, there is only 1 thing left. Showing sdb output is good in that we see a working storage device, but it has nothing to do with sda's issues.
At least as far as I can tell. Another thing I should have mentioned: the info box also tells me the disc has "at least 1 bad sector". I knew there had been one but I thought the disk test I ran had repaired it, and Gparted was just picking up the existence of a repaired sector. Now I think about it a bit more, I think that probably doesn't make sense, and possibly that is the cause of the problem.
It was another hdd I remembered as having had a sector repaired by its test program. Is ntfsprogs included on the Gparted-live CD, and therefore is the warning message in my first post just a general-purpose message to be displayed whether ntfsprogs is loaded or not? I'm away from home at present, but I will see what I can do when I get back in a couple of days.
I am a total ignoramus Linux-wise, but I seem to remember seeing a command-line option somewhere during the boot or was it during clonezilla boot? Bad sectors are usually detected by the HD firmware and are marked to be remapped. This is done by the firmware, not by the operating system or other software. Remapping is done the next time there is access to the specific sectors. If the sector is allocated and just not easily readable, the content isn't lost.
If it is really bad, a file or folder might be corrupted. So, it is probable that a detected bad or suspect sector was remapped by the various operations after this detection. Furthermore, there is a list of "known bad sectors" kept by the operating system. This list isn't automatically updated, that's why these previously bad and later remapped sectors remain in the list.
Format resets this list. I know it is possible to rebuild the list in the linux filesystems, but I don't know how this is possible in ntfs without format. This will display among other the number of already relocated sectors and the number of sectors pending to relocation.
These results appear in the last column. Presumably there is no issue with ntfsprogs, so I guess it is the "bad sector" that is the problem. Using the command on its own I only see what I assume is the last page. I've used more and less, and see a different page, but still only one, and pressing the space-bar does nothing.
Email Required, but never shown. The Overflow Blog. Podcast Making Agile work for data science. Stack Gives Back Featured on Meta. New post summary designs on greatest hits now, everywhere else eventually. Related 2. Hot Network Questions.
Question feed. Stack Overflow works best with JavaScript enabled. Accept all cookies Customize settings.
0コメント