There have been multiple accounts created with the sole purpose of posting advertisement posts or replies containing unsolicited advertising.

Accounts which solely post advertisements, or persistently post them may be terminated.

tal , (edited )
@tal@lemmy.today avatar

I mean, if you want to start over, that’s your call, but in all honesty, my guess is that all you have to change from your current situation is a line of text in fstab. I don’t believe that changing the cloning method is going to change that.

EDIT: maybe the UUID is for a swap partition or similar in fstab?

EDIT2: This guy is describing a very similar sounding situation (though it’s not clear if he unplugged his original drive before trying to use his cloned one, so might have had duplicate UUIDs).

unix.stackexchange.com/…/systemd-is-eternally-stu…

He thinks that some users have “fixed the problem” by creating a swap partition with gparted.

Multiple forums have had users with similar issues and they fixed it with a GParted-made Swap partition and adding that partition’s UUID to /etc/fstab like…

That would, I expect, generate a new UUID for the swap partition via calling mkswap and then they’re putting the UUID into their fstab.

Just saying that I’d personally do that, confirm that the UUIDs listed in fstab conform to what blkid is saying before starting all over, because I don’t think that dd or another utility for copying disk contents will likely produce a different result.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • [email protected]
  • random
  • lifeLocal
  • goranko
  • All magazines