Yes indeed I could boot only as root in emergency state.
I am unable to decipher the meaning of the journalctl report which I partially attach below.
- Code: Select all
tail --lines=600 /root/jrnl.tmp | grep 'Jacob'
tail --lines=600 /root/jrnl.tmp | grep 'Jacob'
Jun 25 07:04:27 localhost systemd[1]: Mounting /mnt/Jacob...
-- Subject: A start job for unit mnt-Jacob.mount has begun execution
-- A start job for unit mnt-Jacob.mount has begun execution.
Jun 25 07:04:28 localhost kernel: CIFS: Attempting to mount //10.0.2.2/Jacob
Jun 25 07:04:28 localhost systemd[1]: mnt-Jacob.mount: Mount process exited, code=exited, status=32/n/a
-- An n/a= process belonging to unit mnt-Jacob.mount has exited.
Jun 25 07:04:28 localhost systemd[1]: mnt-Jacob.mount: Failed with result 'exit-code'.
-- The unit mnt-Jacob.mount has entered the 'failed' state with result 'exit-code'.
Jun 25 07:04:28 localhost systemd[1]: Failed to mount /mnt/Jacob.
-- Subject: A start job for unit mnt-Jacob.mount has failed
-- A start job for unit mnt-Jacob.mount has finished with a failure.
Also attached is the fsck output
- Code: Select all
cat /root/fsck.txt
which was aborted with error
- Code: Select all
e2fsck 1.45.2 (27-May-2019)
e2fsck: Cannot continue, aborting.
I'll appreciate if you can help me