I purchased a new HDD, i hope it will be delivered next week, i will transfer my files to the new HDD and then i will reformat the old HDD
Thanks for your help

GeorgeLG Unfortunately nothing changed either

Then I strongly suspect that it's not nfs that's causing the problem. As I said, I've used nfs-utils to access nfs content on every edition Solus distributes, and I've been doing that from 2016 up to now. I've never had an issue with it. Have you considered that the HDD may have some problems of its own that are unrelated to nfs?

There are companies that specialize in extracting data from failed disk drives, and although those services are not cheap, it might be worth a try if the data is truly priceless. If it's not, the best solution might be to recycle the HDD and replace it with a SSD. Not only will that improve performance (by a lot!), require less power to operate, and generate less heat, but they're dirt-cheap nowadays.

    • [deleted]

    WetGeek Most likely it's not NFS that's causing the problem, as the OP is talking about NTFS.

      [deleted] the OP is talking about NTFS

      Oh, fsck, you're right. I haven't worked much with Windows or ntfs since I retired 7 years ago, but I use nfs every day. Despite confusing the two file systems, shouldn't Dolphin still be able to access an ntfs drive without any extra help? After all, Dolphin can use smb to access my NAS without requiring any help - why not pacer's ntfs drive? (The Synology NAS speaks both smb and nfs.)

      Given your revelation, I still lean towards the hardware issue. The drive is probably on its way out. What do you suspect the problem is? And thanks for your help with this; I probably would never have noticed it.

        WetGeek Dolphin can use smb to access my NAS without requiring any help - why not pacer's ntfs drive?

        All this confusion got me to wondering whether I was wrong about smb being sufficient to read an ntfs drive (not a server). So, I took an NVMe drive that I'd removed from a computer I'd bought with Windows installed, and inserted it into my SSK external drive case, and resolved the matter to my satisfaction,

        Dolphon, all by itself, was perfectly capable of mounting it and reading everything on that Windows disk. I still think the problem is a dying HDD. And still believe the solution is an inexpensive SATA SSD.

        [deleted] Are you dual-booting Windows?

        Of course not. I don't dual-boot anything. The image above came from my main DELL laptop running Solus 4.5 Plasma. Just Solus 4.5 Plasma. And it's not a screenshot of what's on any of my computers, but of what's on a drive I removed from a computer I bought, before I installed Solus on it.

        Are you asking because you're getting different results from Dolphin?

          [deleted] I was asking the OP.

          My sincere apology. I was taking a quick look at the forum because I needed to be doing something else instead, and I just didn't notice.

          I would use chdsk in windows might have the dirty flag set.
          Would suggest using windows only to do that

          If the original NTFS drive was a windows boot disc then it is more complicated than a hard drive formatted to NTFS, with all the component partitions held together in a type of mother partition. I'm sorry this doesn't sound too technical but it's late and I can't remember the proper terms right now.
          Even if the drive was wiped, the information mapping out the original layout of the drive is still there unless the partition table is wiped also. I had lots of problems accessing an old Windows hard drive that had been repurposed as a storage medium. Eventually I wiped the partition table and reformatted, after that everything was reliable.
          Also sometimes the uefi handling partition will stop Linux file managers from being able to access the main data partition on an old Windows disc. The Windows OS tends to ignore the uefi information unless the disc is being used for booting from, so it will act as a perfectly fine storage device in Windows but can mess stuff up for Linux.
          Hope some of that helps, surprisingly not from any text book just from personal experiences.

          a month later

          Hi guys.
          On the topic, a little bit stretchy.

          I'm on Solus Budgie.
          I'm experiencing similar problem since Solus 4.4 and also the changed Nautilus with Nemo. The file manager may not be relevant, but these is my recall when I first noticed strange file system behavior.

          First, when I copy files from EXT4 partition to NTFS, sometime the files disapear right after the end of the copy process. Gone - the folder is empty. Terminal doesn't show anything, no hidden files, the folder properties shows zero files and size. But If I create a simple file named with one of the missing files, the system says, that there is already file with the same name, in condition of an empty folder.

          My guess was that the files are indexed wrong during the copy to NTFS file system and this cause the disappearance. Connecting the HDD to Windows, Repairing Tools, Fixing the errors and files pop-up.
          This is good, but the issue with the vanishing files happened many times lately. It doesn't follow pattern. Whenever.

          Second, after unmounting NTFS partition, then mounting again, sometimes Solus is unable to open it and says the same like with GeorgeLG: "wrong fs type, bad option, bad superblock on /dev/sda2, missing codepage or helper program, or other error".

          And this happened two or three times. Again, looking for Windows, Repairing Tools, Fixing the errors and the drive is up. Untill a couple of days, when Windows said: "No errors to fix. Everything is fine.", but Solus said: "Nop, I still can't mount the partition, wrong fs type...".

          Just for reference, live USB with old Solus version mounts the "broken" partition without any complains.

          Another guess is bad sectors on HDD, but this happened to: 2 internal HDD, 1 external HDD, 1 USB flash drive multiple times. Don't think they broke all together or fall in bad sectors.

          Never had this issue before with Solus, it was very stable, till the last new changes.
          I can't handle it.

          Any ideas?

            solus_me I run budgie with nemo and transfer stuff to and from ntfs alot do not
            seem have problems.
            They updated ntfs this update might see if that cures your problem.

            On a note nothing I do with ntfs is to a boot ntfs partition.
            Maybe something got borked in switching of all the file managers if thats poss.

              Axios They updated ntfs this update might see if that cures your problem.

              Or may be this is the issue. I can't identify.
              I made a clean reinstall recently in a hope to stop the vanish of files - same situation.

              I do update rarely since I work on Solus and it is my daily bases OS also. When it is stable as I like, I don't want unwanted changes to the programs and the OS, which interfere and stops my work. It takes me time to identify the problem and find a solution. That is why I update rarely. Also I keep my HOME folder on a different partition, because of the above reasons. May be it is a conflict between - old configuration files in Home folder, with new identity in the operating system, but file system management have no place in HOME folder configuration files where resides user references, or am I wrong?

              I use Solus for long time after I left Windows. I like it and I don't want to look for other linux distros.

              Axios Maybe something got broked in switching of all the file managers if that's poss.

              May be, I don't know.

                Axios
                Yes, I've read that.
                I don't think removing the dirty flag with "ntfsfix -d" is a good idea. It could accumulate more problems to the file system when we don't know what is causing it.
                But thanks anyway.

                  solus_me No Problem was not advocating of doing anything there more or less
                  just info.
                  Windows was good at telling you if a volume was dirty especially on plug in drives and if it said ok
                  I would believe it.