My external device SSD not able to mount for my data files

[stevef]

My apologies for another typing error.  I have edited the mistake in my earlier post.

The commands should have been

Code: [Select]

sudo dumpe2fs -h /dev/sdc5

Code: [Select]

sudo dumpe2fs /dev/sdc5 | grep superblock
You need to check and confirm that the SSD is still at /dev/sdc5 and not mounted.

I don't know what scalpel is - sorry.  If you wish to go down another path to try to solve the problem I completely understand.

[Muhammad Umar Farooq]

 linuxlite  ~  sudo dump2fs -h /dev/sdc5
sudo: dump2fs: command not found
 linuxlite  ~  1  sudo dump2fs /dev/sdc5 | grep superblock
sudo: dump2fs: command not found
 linuxlite  ~  1  1 
I have applied the following command and get the result segmentation fault

0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 30.3 kB of archives.
After this operation, 87.0 kB of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu jammy/universe amd64 scalpel amd64 1.60-9 [30.3 kB]
Fetched 30.3 kB in 1s (38.2 kB/s) 
Selecting previously unselected package scalpel.
(Reading database ... 455227 files and directories currently installed.)
Preparing to unpack .../scalpel_1.60-9_amd64.deb ...
Unpacking scalpel (1.60-9) ...
Setting up scalpel (1.60-9) ...
Processing triggers for man-db (2.10.2-1) ...
 linuxlite  ~  scalpel -o block_info.bin /dev/sdb5
Scalpel version 1.60
Written by Golden G. Richard III, based on Foremost 0.69.

Opening target "/dev/sdb5"

Segmentation fault
 linuxlite  ~  SIGSEGV  remove fault
Command 'remove' not found, did you mean:
  command 'remote' from snap remote (1.09)
See 'snap info <snapname>' for additional versions.
 linuxlite  ~  127  

[stevef]

Without adding or removing any devices so that the sdc device doesn't change, please run these commands to examine the block information on the SSD
You may need to enter your password

Code: [Select]

sudo dumpe2fs -h /dev/sdc5

Code: [Select]

sudo dumpe2fs /dev/sdc5 | grep superblock
Post back with the results

Edit - Typo was "dump2fs" in original. Corrected to "dumpe2fs"

[Muhammad Umar Farooq]

Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop13: 40.86 MiB, 42840064 bytes, 83672 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/sdc: 119.24 GiB, 128035675136 bytes, 250069678 sectors
Disk model: Storage Device 
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x29de2ba9

Device     Boot   Start       End   Sectors   Size Id Type
/dev/sdc1  *       2048   1050623   1048576   512M  b W95 FAT32
/dev/sdc2       1052670 250068991 249016322 118.7G  5 Extended
/dev/sdc5       1052672 250068991 249016320 118.7G 83 Linux
 linuxlite  ~  

loop5    7:5    0 349.7M  1 loop /snap/gnome-3-38-2004/140
loop6    7:6    0  73.9M  1 loop /snap/core22/864
loop7    7:7    0  63.5M  1 loop /snap/core20/2015
loop8    7:8    0 349.7M  1 loop /snap/gnome-3-38-2004/143
loop9    7:9    0 496.9M  1 loop /snap/gnome-42-2204/132
loop10   7:10   0   497M  1 loop /snap/gnome-42-2204/141
loop11   7:11   0  91.7M  1 loop /snap/gtk-common-themes/1535
loop12   7:12   0  40.8M  1 loop /snap/snapd/20092
loop13   7:13   0  40.9M  1 loop /snap/snapd/20290
sda      8:0    0  74.5G  0 disk
├─sda1   8:1    0     1M  0 part
├─sda2   8:2    0   513M  0 part /boot/efi
└─sda3   8:3    0    74G  0 part /run/timeshift/backup
                                 /var/snap/firefox/common/host-hunspell
                                 /
sdb      8:16   0 232.9G  0 disk
├─sdb1   8:17   0   512M  0 part
├─sdb2   8:18   0     1K  0 part
└─sdb5   8:21   0 232.4G  0 part
sdc      8:32   0 119.2G  0 disk
├─sdc1   8:33   0   512M  0 part /media/linuxlite/F435-8CF4
├─sdc2   8:34   0     1K  0 part
└─sdc5   8:37   0 118.7G  0 part
 linuxlite  ~  

[stevef]

With the SSD connected, run this command in a terminal - enter your password if asked.

Code: [Select]

sudo fdisk -lThis command with the -l option lists partitions connected to your system.
Next, run this command

Code: [Select]

lsblkThis command lists block storage devices connected to the system along with mount status
Please post the results of both commands.

[Muhammad Umar Farooq]

the below is result after applying sudo dmesg and whereis journalctl commands

[  465.552645] scsi 6:0:0:0: Direct-Access        Mass  Storage Device        PQ: 0 ANSI: 0
[  465.553631] sd 6:0:0:0: Attached scsi generic sg2 type 0
[  465.554270] sd 6:0:0:0: [sdc] 250069678 512-byte logical blocks: (128 GB/119 GiB)
[  465.555011] sd 6:0:0:0: [sdc] Write Protect is off
[  465.555019] sd 6:0:0:0: [sdc] Mode Sense: 03 00 00 00
[  465.555893] sd 6:0:0:0: [sdc] No Caching mode page found
[  465.555904] sd 6:0:0:0: [sdc] Assuming drive cache: write through
[  465.593769]  sdc: sdc1 sdc2 < sdc5 >
[  465.595990] sd 6:0:0:0: [sdc] Attached SCSI disk
[  475.971310] EXT4-fs error (device sdc5): ext4_get_journal_inode:5151: inode #8: comm pool-udisksd: iget: special inode unallocated
[  475.972281] EXT4-fs (sdc5): Remounting filesystem read-only
[  475.972290] EXT4-fs (sdc5): no journal found
[  480.966096] FAT-fs (sdc1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[  496.691682] EXT4-fs error (device sdc5): ext4_get_journal_inode:5151: inode #8: comm pool-udisksd: iget: special inode unallocated
[  496.692329] EXT4-fs (sdc5): Remounting filesystem read-only
[  496.692361] EXT4-fs (sdc5): no journal found
 linuxlite  ~  whereis journalctl
journalctl: /usr/bin/journalctl /usr/share/man/man1/journalctl.1.gz
 linuxlite  ~  

[stevef]

I think it might be a good idea to a clean start and post back with the dmesg output and the journalctl output so that we can see if anything is different.

[Muhammad Umar Farooq]

It is still not mounting for your convenience message file enclosed

[stevef]

You seem to have progressed.
Does the SSD mount now or is it still failing ?

[Muhammad Umar Farooq]

/dev/sdb5: UUID="00566cc5-d853-46bc-b4ff-2649a3450fd5" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="e32b244f-05"
/dev/sdb1: UUID="C461-7069" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="e32b244f-01"
/dev/sda2: UUID="EDCC-3FF8" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="6a7d196f-11cf-49a5-b301-d38f93ba95a0"
/dev/sda3: UUID="c2ac39a4-b96e-4cad-872a-1b887eb472af" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="417b4b18-6ee4-47e8-ba6a-19db66c38a17"
 linuxlite  ~  sudo fsck.ext6 -v /dev/sdb5
[sudo] password for linuxlite:
sudo: fsck.ext6: command not found
 linuxlite  ~  1  
 linuxlite  ~  1  sudo fsck.ext4 -v /dev/sdb5
e2fsck 1.46.5 (30-Dec-2021)
/dev/sdb5: recovering journal
Clearing orphaned inode 394923 (uid=1000, gid=1000, mode=0100600, size=196608)
Clearing orphaned inode 11272786 (uid=0, gid=0, mode=0100644, size=522936)
Clearing orphaned inode 11283639 (uid=0, gid=0, mode=0100644, size=339472)
Clearing orphaned inode 11283634 (uid=0, gid=0, mode=0100644, size=63888)
Clearing orphaned inode 11272332 (uid=0, gid=0, mode=0100644, size=1799408)
Clearing orphaned inode 11283927 (uid=0, gid=0, mode=0100644, size=465008)
Setting free inodes count to 14008836 (was 14050742)
Setting free blocks count to 51764202 (was 52117911)
/dev/sdb5: clean, 1228284/15237120 files, 9153814/60918016 blocks
 linuxlite  ~  

[Muhammad Umar Farooq]

Welcome to Linux Lite 6.6 linuxlite
 
Sunday 22 October 2023, 20:18:03
Memory Usage: 662/3790MB (17.47%)
Disk Usage: 52/73GB (75%)
Support - https://www.linuxliteos.com/forums/ (Right click, Open Link)
 
 linuxlite  ~  blkid
/dev/sdb5: UUID="00566cc5-d853-46bc-b4ff-2649a3450fd5" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="e32b244f-05"
/dev/sdb1: UUID="C461-7069" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="e32b244f-01"
/dev/sda2: UUID="EDCC-3FF8" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="6a7d196f-11cf-49a5-b301-d38f93ba95a0"
/dev/sda3: UUID="c2ac39a4-b96e-4cad-872a-1b887eb472af" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="417b4b18-6ee4-47e8-ba6a-19db66c38a17"
 linuxlite  ~  

Should I use the second command just like as you depicted or to be changed if changed please give rewrite command.

[stevef]

The second part of your post (since edited) shows you entered "blkid", then "ext4" and then the fsck command exited with "Possibly non-existent device?"

I don't understand where the messages beginning "Force rewrite" come from.  What command was that ?

[Muhammad Umar Farooq]

Dear Sir/Madam,
Force rewrite<y>? yes
Error reading block 3147598 (Input/output error) while getting next inode from scan.  Ignore error<y>? yes
Force rewrite<y>? yes
Error reading block 3147599 (Input/output error) while getting next inode from scan.  Ignore error<y>? yes
Force rewrite<y>? yes
Error reading block 3147600 (Input/output error) while getting next inode from scan.  Ignore error<y>? yes
Force rewrite<y>? yes
Error reading block 3147601 (Input/output error) while getting next inode from scan.  Ignore error<y>? no
Error while scanning inodes (815872): Can't read next inode

/dev/sdc5: ***** FILE SYSTEM WAS MODIFIED *****
Recreate journal<y>? yes
Creating journal (131072 blocks): Error reading block 1040 (Input/output error).  Error reading block 14680065 (Input/output error).  Error reading block 22020097 (Input/output error).  Ignore error<y>? Ignore error<y>? Ignore error<y>? Error reading block 7340033 (Input/output error).  Ignore error<y>? yes
Force rewrite<y>? yes
Force rewrite<y>? yes
Force rewrite<y>? yes
Force rewrite<y>?

After applying the commands as suggested by you the above is result
Welcome to Linux Lite 6.6 linuxlite
 
Sunday 22 October 2023, 20:18:03
Memory Usage: 662/3790MB (17.47%)
Disk Usage: 52/73GB (75%)
Support - https://www.linuxliteos.com/forums/ (Right click, Open Link)
 
 linuxlite  ~  blkid
/dev/sdb5: UUID="00566cc5-d853-46bc-b4ff-2649a3450fd5" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="e32b244f-05"
/dev/sdb1: UUID="C461-7069" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="e32b244f-01"
/dev/sda2: UUID="EDCC-3FF8" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="6a7d196f-11cf-49a5-b301-d38f93ba95a0"
/dev/sda3: UUID="c2ac39a4-b96e-4cad-872a-1b887eb472af" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="417b4b18-6ee4-47e8-ba6a-19db66c38a17"
 linuxlite  ~ 

 should i use the second command if yes, just like given or to be modified?

[stevef]

Sharing the results from a terminal is usually done using the code tags.
When writing a message you should see a number of face icons above the text entry box.
Above those icons are some button icons.
Locate the '#' button and place the mouse over it.  It should say 'Insert Code'.
Clicking once on the # button should place a pair of code tags into the text entry box.
The tags will be enclosed by square brackets.  Anything you put between the tags will be formatted properly in a blue box when posted.  Use the preview option to check what your post will look like.

Posting guidelines can be found at https://www.linuxliteos.com/forums/introductions/forum-posting-guidelines/
Just after the 'Thread Title' section there is a guide to pasting terminal output into the forum using codes tags.

It appears your disk is failing to mount because of corruption, possibly it was incorrectly disconnected on a previous use and the system is suggesting to use fsck.

Accepting advice off the internet is risky.  Research to double check advice offered. Take extreme care when entering commands.  Ensure you have a working backup of your system and essential data.   If the data on the disk is important you may want to get advice locally from a reputable expert.

Your first post referred to 'Error mounting /dev/sdb5' whereas the most recent post refers to 'sdc5'
It is important that the correct parameter is used when trying to fix disk problems.

Identifying the disk and attempting repair may be easier with a GUI.  If you prefer to use a GUI, the tool you need is 'Partition Drives' aka Gparted.  Let us know if you need help with this.

If you prefer to use command line,  start by showing the hard disks on the system with this.

Code: [Select]

blkid
Identify the device name used by the external SSD, it will be in the form /dev/xxxx
Make a note of the device and also the TYPE listed.

Post back if you can't identify the drive and TYPE.

When you have the correct device and TYPE for the external SSD, run file system check to see what it reports.
If for example, blkid reported "/dev/sdc5" and TYPE="ext4" for your SSD, you would run the command below, but the command you use may be different.

Code: [Select]

sudo fsck.ext4 -v /dev/sdc5
Post back with the results.

[Muhammad Umar Farooq]

=2
[  614.804243] usb 2-1.3: Product: USB Mass Storage Device
[  614.804248] usb 2-1.3: Manufacturer: Generic     
[  614.804253] usb 2-1.3: SerialNumber: 116AC2101219
[  614.908594] usb-storage 2-1.3:1.0: USB Mass Storage device detected
[  614.908908] scsi host6: usb-storage 2-1.3:1.0
[  614.909009] usbcore: registered new interface driver usb-storage
[  614.927305] usbcore: registered new interface driver uas
[  615.923585] scsi 6:0:0:0: Direct-Access        Mass  Storage Device        PQ: 0 ANSI: 0
[  615.924593] sd 6:0:0:0: Attached scsi generic sg2 type 0
[  615.925884] sd 6:0:0:0: [sdc] 250069678 512-byte logical blocks: (128 GB/119 GiB)
[  615.926521] sd 6:0:0:0: [sdc] Write Protect is off
[  615.926530] sd 6:0:0:0: [sdc] Mode Sense: 03 00 00 00
[  615.927140] sd 6:0:0:0: [sdc] No Caching mode page found
[  615.927150] sd 6:0:0:0: [sdc] Assuming drive cache: write through
[  615.938386]  sdc: sdc1 sdc2 < sdc5 >
[  615.940517] sd 6:0:0:0: [sdc] Attached SCSI disk
[  627.005841] FAT-fs (sdc1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[  632.975301] JBD2: no valid journal superblock found
[  632.975307] EXT4-fs (sdc5): error loading journal
 linuxlite  ~ 
ation="open" profile="snap-update-ns.firefox" name="/var/lib/" pid=12883 comm="5" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[  949.393556] audit: type=1107 audit(1697968761.529:53): pid=931 uid=103 auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call"  bus="system" path="/org/freedesktop/login1" interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" name=":1.0" pid=12832 label="snap.firefox.firefox" peer_pid=947 peer_label="unconfined"
                exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? terminal=?'
[  950.104149] audit: type=1107 audit(1697968762.237:54): pid=931 uid=103 auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call"  bus="system" path="/org/freedesktop/timedate1" interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" name=":1.230" pid=12832 label="snap.firefox.firefox" peer_pid=13246 peer_label="unconfined"
                exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? terminal=?'
[  950.314572] audit: type=1107 audit(1697968762.449:55): pid=931 uid=103 auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call"  bus="system" path="/org/freedesktop/timedate1" interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" name=":1.230" pid=12832 label="snap.firefox.firefox" peer_pid=13246 peer_label="unconfined"
                exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? terminal=?'
 linuxlite  ~ 