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

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

+- Linux Lite Forums (https://www.freecinema2022.gq/forums)
+-- Forum: Hardware - Support (https://www.freecinema2022.gq/forums/forumdisplay.php?fid=6)
+--- Forum: Hard Drives and SSDs (https://www.freecinema2022.gq/forums/forumdisplay.php?fid=26)
+--- Thread: My external device SSD not able to mount for my data files (/showthread.php?tid=8950)

Pages: 1 2

Re: My external device SSD not able to mount for my data files - Muhammad Umar Farooq - 10-22-2023

/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  ~ 

Re: My external device SSD not able to mount for my data files - stevef - 10-22-2023

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

Re: My external device SSD not able to mount for my data files - Muhammad Umar Farooq - 10-22-2023

It is still not mounting for your convenience message file enclosed

Re: My external device SSD not able to mount for my data files - stevef - 10-22-2023

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.

Re: My external device SSD not able to mount for my data files - Muhammad Umar Farooq - 10-23-2023

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  ~ 

Re: My external device SSD not able to mount for my data files - stevef - 10-23-2023

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

Code:
sudo fdisk -l

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

Code:
lsblk

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

Re: My external device SSD not able to mount for my data files - Muhammad Umar Farooq - 10-24-2023

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  ~ 

Re: My external device SSD not able to mount for my data files - stevef - 10-24-2023

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:
sudo dumpe2fs -h /dev/sdc5

Code:
sudo dumpe2fs /dev/sdc5 | grep superblock

Post back with the results

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

Re: My external device SSD not able to mount for my data files - Muhammad Umar Farooq - 10-25-2023

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 

Re: My external device SSD not able to mount for my data files - stevef - 10-25-2023

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

The commands should have been

Code:
sudo dumpe2fs -h /dev/sdc5

Code:
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.