Wow, I'm weirdly close to the same age as the X Windows System

I generated a domain_logfile with > ddru_ntfsbitmap /dev/sdc1 ddru_ntfsbitmap.mapfile (This way ddrescue knows, which blocks are empty and don't need to be read) Then I ran ddrescue: > ddrescue --sparse --domain-mapfile=ddru_ntfsbitmap.domain_mapfile /dev/sdc1 sdc1.img mapfile But after a very short time ddrescue froze and I disconnected the drive. This is an excerpt from the log: I tried it again: > ddrescue --no-scrape --no-trim --idirect --sparse --domain-mapfile=ddru_ntfsbitmap.domain_mapfile /dev/sdc1 sdc1.img mapfile it froze again. Then I tried different --input-positions, So that I could overcome the part on the HDD, which caused the freeze: ``` ddrescue --no-scrape --no-trim --idirect --sparse -i 3333 --domain-mapfile=ddru_ntfsbitmap.domain_mapfile /dev/sdc1 sdc1.img mapfile ddrescue --no-scrape --no-trim --idirect --sparse --input-position 3333 --domain-mapfile=ddru_ntfsbitmap.domain_mapfile /dev/sdc1 sdc1.img mapfile ddrescue --no-scrape --no-trim --idirect --sparse --input-position 993333 --domain-mapfile=ddru_ntfsbitmap.domain_mapfile /dev/sdc1 sdc1.img mapfile ddrescue --no-scrape --no-trim --idirect --sparse --mapfile-interval 30s --timeout 2m--input-position 993333 --domain-mapfile=ddru_ntfsbitmap.domain_mapfile /dev/sdc1 sdc1.img mapfile ddrescue --no-scrape --no-trim --idirect --sparse --mapfile-interval 30s --timeout 2m --input-position 993333 --domain-mapfile=ddru_ntfsbitmap.domain_mapfile /dev/sdc1 sdc1.img mapfile ddrescue --no-scrape --no-trim --idirect --sparse --mapfile-interval 30s --timeout 1m --input-position 99999999999 --domain-mapfile=ddru_ntfsbitmap.domain_mapfile /dev/sdc1 sdc1.img mapfile ``` That last one worked and finished: ```(sizes limited to domain from 97_667_704Ki B to 976_750_976Ki B of 976_750_976Ki B) rescued: 0 B, tried: 0 B, bad-sector: 0 B, bad areas: 0 Current status ipos: 1000 GB, non-trimmed: 0 B, current rate: 393 kB/s opos: 1000 GB, non-scraped: 0 B, average rate: 125 MB/s non-tried: 0 B, bad-sector: 0 B, error rate: 0 B/s rescued: 866603 MB, bad areas: 0, run time: 1h 55m 3s pct rescued: 100.00%, read errors: 0, remaining time: n/a time since last successful read: n/a Copying non-tried blocks... Pass 1 (forwards) Finished ``` I compared the mapfile I got from ddrescue with the one I generated from the ntfs filesystem and was shocked to see that there was an offset. The ddrescue mapfile: ![The ddrescue mapfile]( There the Block is 6718 The ntfs mapfile: ![The ntfs mapfile]( and here the block is 8817. But both report the same Start 0x123BAAE000 and Length. I compared the two mapfile outputs and there are some differences: (thanks @Zerush[]( for the recommendation of textcompare ) However other parts are identical. --- # Now to my Questions:D Is this offset bad? Can I continue to use ddrescue and try to get the remaining parts, where ddrescue froze? How can and should I correct it? Whats the cause? I read that > Modern [HDDs] tend to handle the simple BadBlocks automatically, for example by writing a disk sector that was read with difficulty to another area on the media. [...] such a remapping can be done by a disk drive transparently Was the slow freezing of ddrescue caused by the drive trying to read bad blocks and reallocating them somwhere else? Was it stupid to unplug the USB-HDD while ddrescue was freezed? Did this cause the mismatch of the mapfile I generated from ntfs with the one generated during the ddrescue run? Or was the mismatch caused by the input-positions not aligning to the Blocks on disk? Or because I used the `--sparse` option, so 0 values will be compressed on disk? (This was my source, on how to use ddrescue: )
fedilink These people keep bringing up "mArKeT sHaRE" 1. Linux is free. How would it get market share? 2. It's quite difficult to get an accurate "market share" since user-agents can be faked. EDIT: I wonder if Microsoft are making anti-Linux accounts to try and hamper Linux.

Wayland is not going to save the Linux Desktop
Some issues with Wayland explained.

gitea has now WIP ActivitiyPub Federation
* Mastodon post where they manage to follow a their gitea account: * Gitea federation task list #3 - * the gitea fork that develops this:

Don't use Reddit for Linux or BSD related questions
The upvote-downvote feature is the worst mechanic to plague social media.

Does anyone have a good GPU Passthrough guide for kvm gaming?
Simply put, proton is great for playing single player games or even ones I don't mind playing offline like dark souls. However I recently purchased rust and am limited to servers with each disabled. I think a good work around is playing in a vm with my Nvidia GPU run through the onboard GPU. Many of the guides I have tried have yielded no results, idk if I'm doing something wrong. Help would be appreciated, I'm using Ubuntu with a 1080ti and a Ryzen CPU.

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word “Linux” in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.


  • Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
  • No misinformation
  • No NSFW content
  • No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

  • 0 users online
  • 1 user / day
  • 2 users / week
  • 72 users / month
  • 435 users / 6 months
  • 7 subscribers
  • 1.58K Posts
  • Modlog
A community of leftist privacy and FOSS enthusiasts, run by Lemmy’s developers

What is


  1. No bigotry - including racism, sexism, ableism, homophobia, or xenophobia. Code of Conduct.
  2. Be respectful. Everyone should feel welcome here.
  3. No porn.
  4. No Ads / Spamming.

Feel free to ask questions over in: