Re: Server not booting anymore
On Fri, May 8, 2020 at 2:58 AM Roman Meier <roman.meier@gismap.ch> wrote:
>
>
> That's working nicely. Don't have a clue on how to fix it tho. :(
>
Generic (Debian) advice (works for a lot of other Linux distros too)
The file /etc/fstab contains the filesystems to be mounted upon boot.
For modern Linux'es, it is common to mount these by UUID, since that
follows the disk partition, whereas the name of a disk partition can
change.
Random example from one of my machines:
# <file system> <mount point> <type> <options> <dump> <pass>
/dev/mapper/kg--vm4--debian--root--vg-debian--root /
ext4 errors=remount-ro 0 1
# /boot was on /dev/sdb2 during installation
UUID=4d143d81-5afe-4fc5-b51c-d9e3c5ed8542 /boot ext2
defaults 0 2
UUID=9200-86DC /boot/efi vfat umask=0077 0 1
# this is /dev/sdc1, and ext2 filesystem
UUID=24813b15-c365-488d-bd68-2d025e4bd9ea /zs ext2 defaults 0 0
# the /dev/sdc2 is an ext4 filesystem
UUID=68e453de-b559-457e-b99c-903cf3cb5876 /zv ext4 defaults 0 0
if you use the command 'blkid' you will list all partions with uuid, like this
tingo@kg-vm4:~$ sudo blkid
/dev/sda1: UUID="58A4-1919" TYPE="vfat"
PARTUUID="0037b32d-b328-11e5-87c5-bc5ff4fb29ea"
/dev/sda2: UUID="568ae10d70f9650b" TYPE="ufs"
PARTUUID="38fbe1cc-b328-11e5-87c5-bc5ff4fb29ea"
/dev/sda3: PARTUUID="52af5808-b328-11e5-87c5-bc5ff4fb29ea"
/dev/sdb1: UUID="9200-86DC" TYPE="vfat"
PARTUUID="bcf935df-c6b3-43d4-806b-07619ef9edce"
/dev/sdb2: UUID="4d143d81-5afe-4fc5-b51c-d9e3c5ed8542" TYPE="ext2"
PARTUUID="a539bc03-2ffa-4ab3-a721-c9e0c85158b2"
/dev/sdb3: UUID="qkQCMe-oCNQ-hANf-tklh-K3N5-EO2t-SU1Y8X"
TYPE="LVM2_member" PARTUUID="1ef3b039-69a6-451e-b361-e46f9e9e9c66"
/dev/sdb4: UUID="Dxg5iY-5DgD-Qm4c-ymBO-8kfl-dsRh-3L7d1a"
TYPE="LVM2_member" PARTUUID="24c94ba0-ff33-4db0-9cd7-9e0c172a2258"
/dev/sdc1: UUID="24813b15-c365-488d-bd68-2d025e4bd9ea" TYPE="ext2"
PARTUUID="5b67b0ce-4933-11e7-863d-bc5ff4fb29ea"
/dev/sdc2: UUID="68e453de-b559-457e-b99c-903cf3cb5876" TYPE="ext4"
PARTUUID="c7001bf2-4933-11e7-863d-bc5ff4fb29ea"
/dev/mapper/kg--vm4--debian--root--vg-debian--root:
UUID="50d769e6-09f2-4dc1-ba4d-dedf1670807e" TYPE="ext4"
/dev/mapper/kg--vm4--swap--vg-debian--swap:
UUID="0e799f6c-a675-48da-bb46-f51128a8e3a7" TYPE="swap"
(note that PARTUUID is a different thing, you almost always want UUID)
Armed with this information, you should be able to figure out what has happened:
- the partition in question got a new UUID (this is often a bad sign,
the UUID is created when the partition is created)
- the /etc/fstab got changed somehow; simply change the correct line
to point to the correct UUID
Apologies if this is well known already.
If not, hope it helps.
--
Regards,
Torfinn Ingolfsen
Reply to: