[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Disks renamed after update to 'testing'...?

On 8/18/2020 6:01 AM, hobie of RMN wrote:

On 2020-08-17 16:42, hobie of RMN wrote:

Hi, All -

My brother has been issuing "mount /dev/sdb1" prior to backing up some
files to a second hard disk.  He lately upgraded to 'testing', and it
appears (from result of running df) that what the system now calls
/dev/sdb1 is what he has thought of as /dev/sda1, the system '/'
partition.

Thanks to the UUID= mechanism, his system still boots properly, but
'mount
/dev/sdb1' is inappropriate now, could even be the path to madness. :)

Two questions, then: (1) What caused this shift of device naming? And
(2)
How do we fix it?  Is this something that can be changed in the BIOS?
But, if so, what caused it to change in the first place?

Thanks for your time and attenton.


Please run the following commands as root and post the complete console
session -- prompt, command issued, and output obtained:

	# cat /etc/fstab

	# mount


Please post the complete console session demonstrating the issue with
mount(8).


David



Thaks. :)

cat /etc/fstab output includes:
# / was on /dev/sda1 during installation
UUID=3f50ca38-20f3-4a12-880c-a1283ac6e41b /               ext4
errors=remount-ro 0

'mount' output includes:
/dev/sdb1 on / type ext4 (rw,relatime,errors=remount-ro)



Instead of '/dev/sdb1' you should use the 'UUID' or a 'lable' to refer
to that partition.

In the case of your brother, I would do:

$ blkid -s UUID -o export /dev/sdb1

From the output of the above cmd, substitute '/dev/sdb1' by the all
UUID line.


You also might consider changing your mountpoint from using '/'..


To answer your other question:

'# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#'


--
John Doe
Reply to: