My right of passage was trying to run hobby websites in the early 2000s using a pirated copy of Windows Server with IIS. Then I discovered Apache and Linux LAMP stacks and realized how much IIS sucks and it was all over from there.
I even was inspired to get back into programming due to wanting to learn PHP ( I only had some QBasic experience at the time). Now I can do PHP, C, C++, and JS (granted they all have extremely similar syntax)
Why not? It’s simple, lightweight, has a lot of interesting commands that fills its respective niche really well (btop, for instance) and (the best of all) it doesn’t explode my PC everytime I run such commands.
Use the nbd system (network block devices) and qemu to create a qcow2 image with your defective device as the base device. Serve this qcow2 image with qemu-nbd and attach it as a NBD device locally. Then run fsck or testdisk on the NBD device. This will let you repair the filesystem Linux sees without writing to the disk. Testdisk can scan for any filesystems left on the device if the partitions no longer match filesystems.
Also, if all else fails use photorec to slice the file types you need.
Also, ddrescue can try to read any actually failing sectors and work out what they contain, but puts a lot of stress on the device.
Beware, any method that puts more wear on the disk should not be used unless you’re willing to accept the risk that the drive could get worse.
I don’t know how to do any of that first part. All of the data on the drive is replaceable, it’s just going to be very tedious and time consuming. I’m currently trying one other method and I think after I’m done with that, that I’m just going to skip trying to recover the data. I had some other plans for what I wanted to do with this device and I think trying to recover the data isn’t worth it at this point.
People suggested formatting to exFAT which is valid, but first you could just try either compressing the file (tar czvf file tarball.tgz for instance). FAT32 cannot handle files larger than 4GB, and compression might just make your file small enough.
As a workaround you could also split it in half and stich it back on the target machine
You don’t have the features “auto-allocate-uids” and “configurable-impure-env” enabled, so “auto-allocate-uids” and “impure-env” options are ignored in your config.
I’ve actually been getting into NixOS recently; interested in replacing an old server I’ve had for like 10 years with something I can just build from a bunch of config files.
Can confirm it is confusing and I have no idea how anything works. :D
In my searches, I’ve come across nixos.org/guides/nix-pills/ , which I’ve gone through a few chapters of - seems good so far.
I used Ubuntu for a few years, and always felt that it works well and was super easy to set up. But it also seemed to use a lot of disk space. This was of course not ubuntu‘s fault, but my inexperience. But I never had to look under the hood, so I didn’t, and I ended up installing a bunch pf bloat, some of which ended up causing minor issues eventually.
I decided to try arch, and get more into configuration and learning linux. It was quite a ride, and I am happy to have gone through with it. I’m still learning, but I have so much more knowledge & control over what the PC does and how it does it. I also have a lot more room for games and such.
linux
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.