1

Final Update:

I ended up replacing Ubuntu with Linux Mint and the problem of random crashes seems to have gone away (been using it heavy-duty for a good couple of hours by which time Ubuntu would have normally crashed on me).

I know that's not a great answer but I did try hard to figure out what was going on and came out with naught. Mint is also based on Ubuntu 16.04 which makes it even more puzzling.

Hopefully this is somewhat useful to anyone else that gets similar symptoms to what I was getting (where after using it for a while the hard-disk gets disconnected, the Ubuntu menu stops working, and a hard-reset is required).

Original post:

I keep getting errors when I try to run fsck. Ubuntu also keeps crashing on me.

I'm not convinced it's a hard drive issue as disk checks other than fsck do not report a problem and I've even shifted the Ubuntu partition around (see original post here: Dependency failed for /dev/disk/).

The error I get when running fsck in recovery mode is: Timed out waiting for device dev-disk-by\x2duuid-1d227bb3\x2db6ac\x2d44f6\x2dda063\ ...I could not read the rest

My fstab is:

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/nvme0n1p7 during installation
UUID=06473276-9e10-42e4-86db-fc3c81557d8b /               ext4    errors=remount-ro 0       1
# /boot/efi was on /dev/nvme0n1p1 during installation
UUID=A48B-EA59  /boot/efi       vfat    umask=0077      0       1
# swap was on /dev/nvme0n1p6 during installation
UUID=1d227bb3-b6ac-44f6-a063-2bd5e8578eba none            swap    sw              0       0

My blkid is:

/dev/loop0: TYPE="squashfs"
/dev/loop1: TYPE="squashfs"
/dev/nvme0n1: PTUUID="06fdaa6e-9825-4df2-8d9b-b405e996ba04" PTTYPE="gpt"
/dev/nvme0n1p1: LABEL="SYSTEM" UUID="A48B-EA59" TYPE="vfat" PARTLABEL="Ubuntu Boot" PARTUUID="5402c9a1-2c4f-4dd4-9b56-e5068b5f0950"
/dev/nvme0n1p2: PARTLABEL="Microsoft reserved partition" PARTUUID="52ef0e33-bb36-4ee5-9b96-a8595743b369"
/dev/nvme0n1p3: LABEL="Windows" UUID="7ACA8CC9CA8C82DD" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="1b57fd79-f182-4786-b140-7f8b4688f5f6"
/dev/nvme0n1p4: UUID="0202928302927AFD" TYPE="ntfs" PARTUUID="9c06573d-1ecb-4821-abea-a51ab044f001"
/dev/nvme0n1p5: UUID="e681ae06-9f7e-4902-ae91-4d1f8dcf028d" TYPE="ext4" PARTLABEL="Basic data partition" PARTUUID="1a2ac5ca-37c5-11e7-9246-00155d6ff614"
/dev/nvme0n1p6: UUID="1d227bb3-b6ac-44f6-a063-2bd5e8578eba" TYPE="swap" PARTLABEL="Basic data partition" PARTUUID="1a2ac759-37c5-11e7-9246-00155d6ff614"
/dev/nvme0n1p7: UUID="06473276-9e10-42e4-86db-fc3c81557d8b" TYPE="ext4" PARTLABEL="Ubuntu" PARTUUID="1a2ac76e-37c5-11e7-9246-00155d6ff614"
/dev/nvme0n1p8: LABEL="Windows RE tools" UUID="5E348D1C348CF7F3" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="d7e07fd7-01ac-4e69-bf35-ad57fabdfd1c"
/dev/nvme0n1p9: LABEL="LinuxStorage" UUID="dc012449-3e39-4c52-97fb-1ffe9df2cab9" TYPE="ext4" PARTLABEL="LinuxStorage" PARTUUID="e9e0ec72-be01-436a-bbf7-f574a28f35fa"
/dev/sda1: LABEL="UBUNTU 16_0" UUID="F852-224C" TYPE="vfat" PARTUUID="00010c9d-01"

Does my fstab look ok to people?


UPDATE

Here is what I have found since:

  • if I go into root and wait a few seconds the system crashes/displays this on its own: https://www.dropbox.com/s/xzux7fj997dxobt/IMG_20170603_104418496.jpg?dl=0
  • For this error to appear I have to start typing out a command such as fsck or reboot or pretty much anything. It then crashes before I hit enter
  • Whatever command I had started typing out gets run after it finishes crashing, so reboot is the safest thing here

  • Because that error indicated it was my swap that was failing I formatted my swap and updated my fstab

  • However the above error returned. I was unable to get a good photo of the error as it only stays on the screen a few seconds before it disappears

  • But I can tell you the main error at the top seems to point to A48B now , which according to blkid is my Ubuntu Boot partition on https://www.dropbox.com/s/ztqw1yd8a7qy6t0/IMG_20170603_110604580.jpg?dl=0

  • Not sure what I should do with that as didn't want to mess around with boot. But I do have a USB boot I can use to format p1 perhaps?

Reddspark
  • 119

1 Answers1

0

Unless your machine to totally starved for DRAM, swap should be running there and not as a HDD/SDD partition. That said, you can check for HDD bad blocks with this command:

sudo badblocks -v /dev/sdax # where x = /dev/swap_partition_name_ID

Running fsck on the swap partition is not needed and is probably not even desirable.

As a practical matter, and to answer your concerns, a reasonably resourced machine will rarely if ever actually use swap.

jones0610
  • 2,514