Member Avatar for lewashby

I recently created a post thinking I had blown up my bootloader but I've actually narrowed the problem down to the SSD on which my home directory is mounted. The reason my computer has not been booting is because my system is not mounting my home directory's SSD. This started after I opened my box and installed a new SSD which is now unplugged and not being used. Every since I opened my box my computer wouldn't boot again. I edited /etc/fstab while booted in a live USB and commented out the line telling my computer to auto mount the SSD drive to /home/user/. After that my computer has booted up just fine, except that I'm given a generic home directory without all of my files.
When I try to mount the drive manually this is what I get.

user@mothership ~ $ sudo mount /dev/sdd1 /home/user/
mount: special device /dev/sdd1 does not exist
user@mothership ~ $ dmesg | tail
[ 1104.937031] sd 11:0:0:0: Attached scsi generic sg4 type 0
[ 1104.938166] sd 11:0:0:0: [sdd] 488397168 512-byte logical blocks: (250 GB/233 GiB)
[ 1104.939159] sd 11:0:0:0: [sdd] Write Protect is off
[ 1104.939165] sd 11:0:0:0: [sdd] Mode Sense: 28 00 00 00
[ 1104.940154] sd 11:0:0:0: [sdd] No Caching mode page found
[ 1104.940158] sd 11:0:0:0: [sdd] Assuming drive cache: write through
[ 1104.948053]  sdd:
[ 1104.951038] sd 11:0:0:0: [sdd] Attached SCSI disk
[ 1105.150165] EXT4-fs (sdd): no journal found
[ 1124.237071] EXT4-fs (sdd): no journal found

And when I plug the device into my fron USB ports this is what I get

Error mounting /dev/sdd at /media/user/86e3838b-7c18-4870-8a7b-684255629264: Command-line `mount -t "ext4" -o "uhelper=udisks2,nodev,nosuid" "/dev/sdd" "/media/user/86e3838b-7c18-4870-8a7b-684255629264"' exited with non-zero exit status 32: mount: wrong fs type, bad option, bad superblock on /dev/sdd,
       missing codepage or helper program, or other error

       In some cases useful info is found in syslog - try
       dmesg | tail or so.

Any ideas? Thanks. I know I'm a pain.

  • 4 Contributors
  • 3 Replies
  • 1K Views
  • 2 Weeks Discussion Span
  • Latest Post Latest Post by alc6379

Dani AI

Generated

— good progress so far: you booted by disabling the fstab entry, which means the kernel sees the device but userspace (udisks/mount) is failing to use it. is right that a filesystem check is part of troubleshooting, 's Windows hibernation/fast-start is worth considering if the disk was last touched by Windows, and is correct to check whether the disk actually has partitions versus a filesystem on the whole device.

Do not write to the drive if the files matter. First gather non‑destructive evidence:

lsblk -f
blkid
file -sL /dev/sdX
sudo smartctl -a /dev/sdX

What to do next (based on what those probes show)

  • No partition node (no sdX1): the partition table may be lost. Run TestDisk to scan for and restore partitions.
  • blkid/file report an ext* FS but fsck/errors complain about a bad superblock: run a read‑only fsck probe (e2fsck with the non‑destructive option) and, if needed, locate alternate superblocks with a dry run (mke2fs -n) and repair with e2fsck -b.
  • smartctl shows hardware errors: image the disk first (use GNU ddrescue) and attempt recovery from the image.
  • If the disk came from Windows, verify it wasn't left hibernating; mounting an NTFS hibernated volume will be refused by modern tools.

When fixed, use stable identifiers in /etc/fstab (UUID= or LABEL=) rather than /dev/sdX to avoid renumbering issues.

Recommended Answers

All 3 Replies

Member Avatar for AndrisP

It's a dual boot PC? If yes maybe Windows system is sleep or hybrid sleep not succesfully shut down.

Member Avatar for alc6379

What do you get when you run fdisk -l? do you have partitions on the drive?

Usually the drive is partitioned, and you'd mount /dev/sdd1, not /dev/sdd, which it looks like it's trying to do.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.