help about linux disks
help about linux disks
you have multiple disks affected by bad sectors, but diskinfo shows none. you're planning to convert an ntfs disk to ext4, which might help. recent file transfers caused issues, and linux has been unstable with partial downloads and app conflicts. consider checking disk health before conversion and ensure proper formatting afterward.
There’s nothing I know that would cause panic or lose your files. Like any other modern operating system, if they haven’t been transferred to the right place, they should stay where they are unless something is wrong with the source or destination drive. Bad sectors don’t always mean a bad drive; it’s how many and how fast they appear that indicates a failing drive. Whether you can play partially downloaded files depends on how much of the file you have, which app you use, and whether the file starts correctly. This also depends on the format (mkv, ts, avi, etc.) and how it’s stored. It’s similar to Windows in many ways. What do you mean by “working on a directory”? Sometimes the file manager you’re using might freeze while the drive is working, and other programs could share the same tools, causing delays. This shouldn’t block anything that doesn’t rely on that specific interface, like a console window.
I completely agree. However, I noticed that fixing the SATA cable usually resolves the problem almost every time I encounter bad sectors. YMMV
I transferred some files and Jellyfin didn’t display the new ones until the process finished (they were unrelated files). This happened because I was using a different HDD than my main SSD, which might be why. Also, when I moved files to my phone on Windows, I couldn’t access those folders either.
yea but the issue is i had bad sectors on windows and linux doesnt see them, wtf is up? @Alex Atkin UK
Jellyfin may experience a pause because continuous scans would hinder performance while you transfer files. It requires fully processed files to create indexes, which involves generating metadata and searching for credits. I configure my Plex server to avoid automatic library updates until I’m certain new content is added. Bad sectors are managed by the drive and listed in SMART data. The Linux tool might not display the correct information. Much of the SMART data relates to manufacturer health metrics and can be misunderstood by external programs.
You can use Sonarr or Radarr to manage file transfers, after which it delivers a mostly finished metadata file to Plex or JF, prompting them to search for intros or credits.
Drives contain a limited number of spare sectors. When a faulty sector appears, the controller tries to correct it during the next write operation. If successful, the issue was corruption, not damage. If writing fails to fix it, the controller will reassign the bad sector to one of the available spares. After that, commands targeting the original sector address will redirect to the new location. The exact process may be more involved, but the core idea stays consistent. The spare sector count typically ranges from a few hundred, and once depleted, further remapping isn’t possible. A stable count usually indicates good drive condition; rising remappings often signal impending failure. Tools like smartctl (command line) or KDE’s SMART Status can reveal current remapping status. You can also check controller logs for errors such as failed read/write attempts at specific LBA locations. Running a short (2-5 min) and longer (1+ hour) self-test is advisable to verify the controller’s ability to detect and fix problems. Record the remapped sector count before and after testing. Note: This applies mainly to traditional spinning platters, not SSDs, where wear-leveling affects the process differently. SSDs may show similar issues but involve more complex rewriting cycles.