Can no longer find OS/hard drive after update

[shockwave]

@dalto

lsblk -o name,type,fstype,size,mountpoint,uuid

[root@EndeavourOS /]# lsblk -o name,type,fstype,size,mountpoint,uuid
NAME              TYPE  FSTYPE   SIZE MOUNTPOINT UUID
loop0             loop           1.6G            
sda               disk         119.2G            
├─sda1            part           300M /boot/efi  
├─sda2            part         110.1G            
│ └─mycryptdevice crypt        110.1G /          
└─sda3            part           8.8G            
sdb               disk         931.5G            
└─sdb1            part         931.5G            
sdc               disk          14.9G            
├─sdc1            part           1.7G            
└─sdc2            part           104M            
sr0               rom           1024M 

[dalto]

I guess it can’t get the uuid from within the chroot?

[shockwave]

Is there another way I can try to get it?

[petsam]

@shockwave

Is there another way I can try to get it?

blkid

[shockwave]

[root@EndeavourOS /]# blkid
/dev/loop0: TYPE="squashfs"
/dev/mapper/mycryptdevice: UUID="37f4277c-d5c2-4776-97d1-6cfd52bfc133" BLOCK_SIZE="4096" TYPE="ext4"
/dev/sdc2: SEC_TYPE="msdos" LABEL_FATBOOT="ARCHISO_EFI" LABEL="ARCHISO_EFI" UUID="826B-8B64" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="593e4509-02"
/dev/sdc1: BLOCK_SIZE="2048" UUID="2022-08-05-07-19-08-00" LABEL="EOS_202208" TYPE="iso9660" PARTUUID="593e4509-01"
/dev/sda2: UUID="cf2991b1-db38-44df-b0eb-182b21b2b115" TYPE="crypto_LUKS" PARTUUID="f06934f9-bb3b-a047-9b61-825bbfaee099"
/dev/sda3: UUID="ea763b8d-0f5c-4581-89f1-7fe0dc38087a" TYPE="crypto_LUKS" PARTUUID="037c0746-f348-af4a-b712-a06a3dd9c6d1"
/dev/sda1: UUID="36EE-B488" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="777265f0-ed89-4f44-a1e7-36b3c1e1fcea"

[petsam]

What happened to your partition?
Is this your own PC, or possibly stolen?

[dalto]

@shockwave

UUID=43651a5d-3f0d-4d20-b147-7fa7e710283c /home/workstation0/1Toshiba

What is this partition?

[shockwave]

That is the second hard drive. Mostly it has my steam library. The OS is on my main drive.

[dalto]

Is it also encrypted?

[shockwave]

Lol. I don’t know. The last time I updated it booted to this error.

[shockwave]

No, I don’t think the Toshiba is encrypted, just the main drive As far as I remember, the only thing on the Toshiba is my steam library.

[dalto]

@shockwave

No, I don’t think the Toshiba is encrypted, just the main drive As far as I remember, the only thing on the Toshiba is my steam library.

Which partition is it because it isn’t showing up in your blkid output.

[shockwave]

main drive is the sda2 . The Toshiba is sdb1

[petsam]

@shockwave

I don’t think the Toshiba is encrypted, just the main drive

Try outside of chroot:

sudo blkid

[shockwave]

[liveuser@eos-2022.08.05 ~]$ sudo blkid
/dev/loop0: TYPE="squashfs"
/dev/mapper/mycryptdevice: UUID="37f4277c-d5c2-4776-97d1-6cfd52bfc133" BLOCK_SIZE="4096" TYPE="ext4"
/dev/sdc2: SEC_TYPE="msdos" LABEL_FATBOOT="ARCHISO_EFI" LABEL="ARCHISO_EFI" UUID="826B-8B64" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="593e4509-02"
/dev/sdc1: BLOCK_SIZE="2048" UUID="2022-08-05-07-19-08-00" LABEL="EOS_202208" TYPE="iso9660" PARTUUID="593e4509-01"
/dev/sda2: UUID="cf2991b1-db38-44df-b0eb-182b21b2b115" TYPE="crypto_LUKS" PARTUUID="f06934f9-bb3b-a047-9b61-825bbfaee099"
/dev/sda3: UUID="ea763b8d-0f5c-4581-89f1-7fe0dc38087a" TYPE="crypto_LUKS" PARTUUID="037c0746-f348-af4a-b712-a06a3dd9c6d1"
/dev/sda1: UUID="36EE-B488" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="777265f0-ed89-4f44-a1e7-36b3c1e1fcea"

[joekamprad]

sudo fdisk -l is the old old way to show all the details

[shockwave]

pasted both below. chroot and outside chroot

[liveuser@eos-2022.08.05 ~]$ sudo fdisk -l
Disk /dev/sda: 119.24 GiB, 128035676160 bytes, 250069680 sectors
Disk model: SanDisk SD8SNAT1
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: gpt
Disk identifier: 045D09E9-CD10-764C-9D80-4C41CB292CEC

Device         Start       End   Sectors   Size Type
/dev/sda1       4096    618495    614400   300M EFI System
/dev/sda2     618496 231612850 230994355 110.1G Linux filesystem
/dev/sda3  231612851 250067789  18454939   8.8G Linux filesystem


Disk /dev/sdb: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: TOSHIBA MQ01ABD1
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 27DBCC4F-8765-4335-8799-08256C21BA1A

Device     Start        End    Sectors   Size Type
/dev/sdb1   2048 1953523711 1953521664 931.5G Linux filesystem


Disk /dev/sdc: 14.91 GiB, 16004415488 bytes, 31258624 sectors
Disk model: USB Flash Drive 
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: 0x593e4509

Device     Boot   Start     End Sectors  Size Id Type
/dev/sdc1  *         64 3564735 3564672  1.7G  0 Empty
/dev/sdc2       3564736 3777727  212992  104M ef EFI (FAT-12/16/32)


Disk /dev/loop0: 1.6 GiB, 1714974720 bytes, 3349560 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/mapper/mycryptdevice: 110.14 GiB, 118267012608 bytes, 230990259 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
[liveuser@eos-2022.08.05 ~]$ 

[root@EndeavourOS /]# sudo fdisk -l
Disk /dev/sda: 119.24 GiB, 128035676160 bytes, 250069680 sectors
Disk model: SanDisk SD8SNAT1
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: gpt
Disk identifier: 045D09E9-CD10-764C-9D80-4C41CB292CEC

Device         Start       End   Sectors   Size Type
/dev/sda1       4096    618495    614400   300M EFI System
/dev/sda2     618496 231612850 230994355 110.1G Linux filesystem
/dev/sda3  231612851 250067789  18454939   8.8G Linux filesystem


Disk /dev/sdb: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: TOSHIBA MQ01ABD1
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 27DBCC4F-8765-4335-8799-08256C21BA1A

Device     Start        End    Sectors   Size Type
/dev/sdb1   2048 1953523711 1953521664 931.5G Linux filesystem


Disk /dev/sdc: 14.91 GiB, 16004415488 bytes, 31258624 sectors
Disk model: USB Flash Drive 
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: 0x593e4509

Device     Boot   Start     End Sectors  Size Id Type
/dev/sdc1  *         64 3564735 3564672  1.7G  0 Empty
/dev/sdc2       3564736 3777727  212992  104M ef EFI (FAT-12/16/32)


Disk /dev/loop0: 1.6 GiB, 1714974720 bytes, 3349560 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/mapper/mycryptdevice: 110.14 GiB, 118267012608 bytes, 230990259 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

[joekamprad]

@shockwave

The Errors are as follows:

[ TIME ] Timed out waiting for device /dev/desk/by-uuid/4365…
[DEPEND] Dependency failed for /home/workstation0/Toshiba
[DEPEND] Dependency failed for Local Files systems.
[DEPEND] Dependency failed for File System Check on /dev/disk/by-uui/4365…
You are in emergency mode. After logging in, type “journalctl”…

i mean this really looks simply like the drive is unplugged or defective… or at least have filesystem issue…
you could do a filesystemcheck … would be possible with gparted too…

[petsam]

@shockwave

sda    disk             119.2G 
├─sda1 part vfat          300M 36EE-XXXX
├─sda2 part crypto_LUKS 110.1G cf2991b1-db38-XXXX-182b21b2b115
└─sda3 part crypto_LUKS   8.8G ea763b8d-0f5c-XXXX-7fe0dc38087a
sdb    disk             931.5G 
└─sdb1 part             931.5G 
sdc    disk iso9660      14.9G 2022-08-05-07-19-08-00
├─sdc1 part iso9660       1.7G 2022-08-05-07-19-08-00
└─sdc2 part vfat          104M 826B-8B64

It is worryingly strange that UUID is not shown from only sdb1.
It most possibly means there is a HW problem. The drive is seen, but not read.

[dalto]

sdb1 isn’t even showing in your lsblk.

For now, I would add nofail to the entry in /etc/fstab for that filesystem. That will stop it from blocking boot.