> Generic (Debian) advice (works for a lot of other Linux distros too) > The file /etc/fstab contains the filesystems to be mounted upon boot.
[...] > 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 > > Hi folks, Thanks so much for your contributions! I was finally able to fix the issue! It seems that the liveCd I used to boot Debian-Edu did some changes to fstab. I'm not sure tho. Fact is that I found some funny content in my fstab: #Entry for /dev/loop0 : UUID=2020-02-08-14-49-26-00 /media/roman/d-live\040nf\04010.3.0\040xf\040amd64 iso9660 ro,nosuid,nodev,relatime,nojoliet,check=s,map=n,blocksize=2048, uid=1000,gid=1000, dmode=500,fmode=400 0 0 I also found the following file: /etc/fstab/fstab-disk-manager-save The file date is equal to the time this boot issue started. I suspect that it's some kind of backup file. The following step fixed the issue: cp fstab-disk-manager-save fstab Thanks again!!! Kind regards, Roman
