On Thu, 18 Aug 2022, Ben Koenig wrote:
If fdisk is seeing those partitions as sdi/sdj but they show in mount as
their original sdc/sdd, then that definitely means they disconnected and
reconnected. It probably happened so fast that the system didn't have time
to clean up the old devices. You might want to check to make sure /dev
doesn't have any strange block devices laying around. ls /dev/sd*
shouldn't show any files for sdc or sdd. lsblk is a more detailed version
of that.
# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sdb 8:16 0 1.8T 0 disk
├─sdb2 8:18 0 100G 0 part /opt
├─sdb3 8:19 0 1.3T 0 part /data1
└─sdb1 8:17 0 400G 0 part /home
sdi 8:128 0 1.8T 0 disk
└─md0 9:0 0 1.8T 0 raid1 /media/backup
sr0 11:0 1 1024M 0 rom
sdg 8:96 0 1.8T 0 disk
└─sdg1 8:97 0 1.8T 0 part
sda 8:0 0 232.9G 0 disk
├─sda2 8:2 0 32G 0 part [SWAP]
├─sda3 8:3 0 200.8G 0 part /
└─sda1 8:1 0 100M 0 part /boot/efi
sdj 8:144 0 1.8T 0 disk
└─md0 9:0 0 1.8T 0 raid1 /media/backup
sdh 8:112 0 1.8T 0 disk
└─sdh1 8:113 0 1.8T 0 part
It looks like all you need to do is umount the drives, then mount fresh to
force a replay of the ext4 journal. Since the fstab entries go by UUID you
probably don't need to do anything more, it will find the correct path in
/dev.
Sonofagun. I umounted then mounted /dev/sdc1 and /dev/sdd1 and now mount
shows them (again) as /dev/sdg1 and /dev/sdh1, but I can (as a user) once
again access those two drive. Ergo, that fixed the problem.
As long as I can access and back up those two partitions I don't care that
different utilities see them as differently named devices.
Thanks very much, Ben.
Rich
