Hi Terry, > $ sudo -i blkid > /dev/sda1: UUID="ff55c4cb-60bd-453f-8459-408f7324ad7e" > BLOCK_SIZE="4096" TYPE="ext4" > PARTUUID="30098eb5-9a77-48dc-8e6b-bd33ef8ca62e" > /dev/sdb1: UUID="48206cfd-9f42-4e35-9ca9-aaeebf011140" TYPE="swap" > PARTUUID="c8cc13a7-d6f8-4d57-9b33-ee3de9225960" > /dev/sdb2: LABEL="Home" > UUID="c7d489ae-2d05-4c37-a699-effb5f2262ec" BLOCK_SIZE="4096" > TYPE="ext4" PARTUUID="6182d317-8280-4066-86e4-c078bd39a17a" > /dev/sdb3: LABEL_FATBOOT="BACKUP" LABEL="BACKUP" UUID="651E-205E" > BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="FAT32_Backup_Partition" > PARTUUID="772a4742-e75c-439 7-9680-803918f14529" > /dev/loop1: BLOCK_SIZE="131072" TYPE="squashfs" > .. > > Lots of these
Right, and there's UUID=ff55... that you mentioned this morning. > $ sudo -i lsblk > NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS > loop0 7:0 0 4K 1 loop /snap/bare/5 > .. > Lots of these > > sda 8:0 0 58.7G 0 disk > └─sda1 8:1 0 58.7G 0 part / > sdb 8:16 0 931.5G 0 disk > ├─sdb1 8:17 0 15M 0 part > ├─sdb2 8:18 0 908.2G 0 part /home > └─sdb3 8:19 0 23.3G 0 part /backup > sr0 11:0 1 1024M 0 rom There's sda1 mounted on /, with sdb2 on /home. sdb1 is swap, given the blkid output above. > > sudo -i lsblk -o > > rm,rota,type,name,size,fssize,fsavail,label,partlabel,vendor,model,serial,mountpoint > > $ sudo -i lsblk -o > rm,rota,type,name,size,fssize,fsavail,label,partlabel,vendor,model,serial,mountpoint > RM ROTA TYPE NAME SIZE FSSIZE FSAVAIL LABEL PARTLABEL > VENDOR MODEL SERIAL MOUNTPOINT > 0 0 loop loop0 4K 128K 0 > /snap/bare/5 > 0 0 loop loop1 79.8M 79.9M 0 > /snap/cheese/78 > 0 0 loop loop2 175.2M 175.3M 0 > /snap/chromium/3313 ... Snaps pollute. > 0 0 disk sda 58.7G > ATA SanDisk SDSSDP064G 152424400510 > 0 0 part └─sda1 58.7G 57.5G 30.9G > / > 0 0 disk sdb 931.5G > ATA SanDisk SSD PLUS 1000GB 19360S465503 > 0 0 part ├─sdb1 15M > 0 0 part ├─sdb2 908.2G 892.9G 614.3G Home > /home > 0 0 part └─sdb3 23.3G 23.3G 16.1G BACKUP FAT32_Backup_Partition > /backup > 1 0 rom sr0 1024M > HL-DT-ST HL-DT-ST DVDRAM GT90N M5HD3EJ4615 But here we are, sda is your SanDisk SDSSDP064G, a 64 GB SSD, with an sda1 partion mounted on /, etc. Am I confused? I've a lot going on off list. I thought you had booting problems, yet you've booted into sda1 mounted on /, so everything's okay? > > Well, assuming you've ext4 filesystems, then > > > > sudo -i e2fsck -n /dev/sdc1 > > I presume that has to be done with the disc unmounted, eg in Partition > Magic? Yes, checking a filesystem is done with that filesystem's partition unmounted. Otherwise, it might be changing under the checker's feet, and likewise the filesystem code in the kernel wouldn't be happy with the checker making repairs without it knowing. Two writers to one place, each unknown to the other, is often disastrous. -- Cheers, Ralph. -- Next meeting: Online, Jitsi, Tuesday, 2026-01-06 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... https://dorset.lug.org.uk New thread, don't hijack: mailto:[email protected]
