Re: Cannot boot after distro upgrade
On 8/31/19 3:48 PM, Reco wrote:
On Sat, Aug 31, 2019 at 03:41:12PM +0200, Miroslav Skoric wrote:
On 8/31/19 3:26 PM, Reco wrote:
Boot with init=/bin/bash kernel commandline parameter, remount root
filesystem read-write, fix your /etc/fstab (systemd is picky about
filesystems it's not able to mount, and no, "noauto" won't fix it),
reboot once more.
Sorry for my ignorance, but where to put that "init=/bin/bash"? Here I have LILO and it starts booting properly.
http://tldp.org/HOWTO/LILO-2.html , chapter 2.3.
Reco
Ok Reco, I managed to crawl through this a little bit (I am an old
person), so when I reached prompt, did that:
root@(none):/# mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs
(rw,nosuid,relatime,size=1514900k,nr_inodes=215931,mode=755)
devpts on /dev/pts type devpts
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=304560k,mode=755)
/dev/mapper/localhost-root on / type ext3
(rw,relatime,errors=continue,barrier=1,data=ordered)
/dev/mapper/localhost-usr on /usr type ext3
(rw,relatime,errors=continue,barrier=1,data=ordered)
root@(none):/#
root@(none):/# mount -a
[ 1024.810706] EXT3-fs (dm-6): error: couldn't mount because of
unsupported optional features (8000)
mount: wrong fs type, bad option, bad superblock on
/dev/mapper/localhost-home, missing codepage or helper program, or other
error
In some cases useful info is found in syslog - try dmesg | tail or so.
[ 1024.839252] EXT3-fs (dm-5): error: couldn't mount because of
unsupported optional features (8000)
mount: wrong fs type, bad option, bad superblock on
/dev/mapper/localhost-tmp, missing codepage or helper program, or other
error
In some cases useful info is found in syslog - try dmesg | tail or so.
[ 1024.874388] kjournald starting. Commit interval 5 seconds
[ 1024.874702] EXT3-fs (dm-3): using internal journal
[ 1024.874761] EXT3-fs (dm-3): mounted filesystem with ordered data mode
root@(none):/#
root@(none):/# dmesg | tail
[ 19.828971] kjournald starting. Commit interval 5 seconds
[ 19.836188] EXT3-fs (dm-2): using internal journal
[ 19.836246] EXT3-fs (dm-2): mounted filesystem with ordered data mode
[ 19.838924] aufs: module is from the staging directory, the quality is
unknown, you have been warned.
[ 19.840477] aufs 3.2.x+setfl-debian
[ 1024.810706] EXT3-fs (dm-6): error: couldn't mount because of
unsupported optional features (8000)
[ 1024.839252] EXT3-fs (dm-5): error: couldn't mount because of
unsupported optional features (8000)
[ 1024.874388] kjournald starting. Commit interval 5 seconds
[ 1024.874702] EXT3-fs (dm-3): using internal journal
[ 1024.874761] EXT3-fs (dm-3): mounted filesystem with ordered data mode
root@(none):/# nano /etc/fstab
#
...
proc /proc proc defaults 0 0
/dev/mapper/localhost-root ext3 errors=remount-ro 0 1
# /boot was on /dev/sda1 during installation
UUID=...... /boot ext2 defaults 0 2
/dev/mapper/localhost-home /home ext3 defaults 0 2
/dev/mapper/localhost-tmp /tmp ext3 defaults 0 2
/dev/mapper/localhost-usr /usr ext3 defaults 0 2
/dev/mapper/localhost-var /var ext3 defaults 0 2
/dev/mapper/localhost-swap_1 none swap sw 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto 0 0
Whatever I tried to fix in fstab, did not bring improvement. As Pascal
Hambourg suggested, tried also to mount /home and /tmp as ext4 but no
avail. At next reboot:
...
...
[FAILED] Failed to mount /home.
See 'systemctl status home.mount' for details.
...
...
...
and similar for /tmp
By the way, there appeared some other errors (I hope not in connection
with the main issue):
...
...
[FAILED] Failed to start Console System Startup Logging.
See 'systemctl status console-kit-log-system-start.service' for details.
[FAILED] Failed to start Enable support for additional executable binary
formats.
See 'systemctl status binfmt-support.service' for details.
...
...
Any idea?
Misko
Reply to: