Jump to content

Gamegenorator

Member
  • Posts

    8
  • Joined

  • Last visited

Everything posted by Gamegenorator

  1. Man that really sucks. As a new(er) Linux user I guess I'll ask, I have a backup of everything in /home, are there any configuration files I need to get from /var, /etc, or anywhere else before attempting to refresh the system from the recovery partition? (I had a lot of flatpaks)
  2. I'm still not convinced that it's hardware failure considering I can get into the recovery partition and how young the drive is. But regardless thank you for your help.
  3. The drive is less than a year old, is there a way I could recover it long enough to get my data off of it?
  4. I was just starting up the system and opened Steam when Gnome locked up, the mouse worked but nothing else including alt+f2 worked. I waited a couple of minutes for the drive activity light to disappear, and I hard rebooted it. After the Systemd boot menu I see a flash of gray from the Gnome login screen right before being dumped here. Booting between the current kernel and the old kernel via the systemd boot menu makes no difference. I haven't tried booting into the recovery partition yet, but I can boot into Windows which rules out hardware failure. After some searching I found this: https://askubuntu.com/questions/646414/welcome-to-emergency-mode-think-it-is-a-fsck-problem After booting into the recovery partition and running fdisk -l I get this: sda appears to be the NTFS formatted Segate drive installed in my system that mounts on boot. (I have checked it in Windows and it is fine) sdb is the drive PopOS is installed on, but I don't know what to do about the "Partition 1 does not start on physical sector boundary" error. If anyone has any information on this I would love to know more. As you can see here, fsck thinks that sdb2 (The partition I believe Pop is installed on, is fine) Running cat /etc/fstab provides this: Am I screwed? How can I figure out what went wrong and (hopefully) fix it? If anyone has any idea what's going on here I could really appreciate the help. If worst comes for worse, would refreshing the OS from the recovery partition fix this issue?
  5. Ok, how do I boot into recovery mode, and is TWRP already part of the device or must that be installed?
  6. I have an old Samsung Galaxy Tab 3 from 2013 still running KitKat 4.4, It actually has "reasonable" hardware but it's biggest issue is the software, I would like to install a version of lineage OS on it that's based on a newer version of Android. I understand this involves rooting, and wiping the device out completely but I wouldn't know where to begin. Can someone tell me if this is possible on such an old device? And if so give me some guides on where to get started? Device in question: https://www.amazon.com/Samsung-Galaxy-SM-T310-16GB-Wi-Fi/dp/B00I0FT792/ref=sr_1_4?keywords=galaxy+tab+3&qid=1556227865&s=gateway&sr=8-4
×