Welcome!
Important information
-- Spectre and Meltdown vulnerabilities

News
-- MX Linux on social media: here
-- Mepis support still here

Current releases
-- MX-18 Final release info here
-- Migration Information to MX-18 here
-- antiX-17.3 release info here

New users
-- Please read this first, and don't forget to add system and hardware information to posts!
-- Here are the Forum Rules

Can't login after sudden shutdown

Mich-C
Forum Novice
Forum  Novice
Posts: 55
Joined: Tue Nov 21, 2017 1:11 pm

Can't login after sudden shutdown

#1

Post by Mich-C » Sun Jan 13, 2019 6:03 pm

Yesterday my laptop had a sudden shutdown because it wasn't plugged in to the current when the battery fully discharged.
Today I booted it. Instead of the desktop I get the shell mode with this:

Code: Select all

Live root password for maintenance: or press Control+D to continue
Inserting the root password doesn't change anything (it just displays some logs if I'm not wrong).
I have to use "strartx" to reach the desktop as root user.
But I can't switch to normal user when using lightdm (I get redirected to the lightdm screen, and using both the commands "sudo lightdm stop" "sudo lightdm restart" didn't solve the problem)
My user password is correct, and when I log in as user in shell mode I get this:

Code: Select all

No mail.
No directory, logging in with HOME=/
To solve lightdm loops users usually delete the XAuthorithy file inside the home folder, but the home folder in my root partition is empty, since I have a dedicated home partition.
I tryed to access that partition with thunar but I get this error

Code: Select all

Failed to mount home can't read superblock
Moreover I don't see my Windows partitions listed in thunar.

Can you help me also this time?
Thanks you as always guys!

P.S. I don't think know if this info can help you: when booting MX I always had this line in the logs, even after a fresh install, but I noticed that after this sudden shutdown it is displayed a lot more often

Code: Select all

amdgpu[powerplay] VBIOS did not find boot engine clock value in dependency table. Using memory DPM level 0

User avatar
Eadwine Rose
Forum Veteran
Forum Veteran
Posts: 6799
Joined: Wed Jul 12, 2006 2:10 am

Re: Can't login after sudden shutdown

#2

Post by Eadwine Rose » Mon Jan 14, 2019 10:48 am

When asked for the live root password did you try the root pass of YOU (the one you set) or the live one, or both?


Hopefully someone will come by with an idea..
MX-18_x64 20-12-2018 * 4.19.0-1-amd64 ext4 Xfce 4.12.3 * AMD Asus M4A785TD-V EVO AM3 * ASUS GF GT640-1GD5-L NVIDIA 390.87 * AMD Proc. Athl II X4 635, sAM3 * HDA ATI SB VT1708S An * 2x4Gb DDR3 1600 Kingston * 22" Samsung SyncMaster P2250 * HP Envy5030

User avatar
j2mcgreg
Forum Regular
Forum Regular
Posts: 440
Joined: Tue Oct 23, 2007 12:04 pm

Re: Can't login after sudden shutdown

#3

Post by j2mcgreg » Mon Jan 14, 2019 11:02 am

Please post the results of inxi -F so we can have a clear idea of the hardware involved.
Acer Aspire 3 A315-41-R2W5, AMD Ryzen 5 2500U, Radeon Vega Mobile Graphics, 8 GB ram, 1000 TB hdd

Mich-C
Forum Novice
Forum  Novice
Posts: 55
Joined: Tue Nov 21, 2017 1:11 pm

Re: Can't login after sudden shutdown

#4

Post by Mich-C » Tue Jan 15, 2019 11:26 am

Eadwine Rose wrote:
Mon Jan 14, 2019 10:48 am
When asked for the live root password did you try the root pass of YOU (the one you set) or the live one, or both?


Hopefully someone will come by with an idea..
Hi! I tryed with my root password ("root") , I haven' t tryed with "demo" yet.
The complete message I get when I try to boot the pc is this one (I wrongly reported it in my first post)

Code: Select all

You are in emergency mode! After logging in, type "journalctl -xb" to view system logs, "systemctl reboot" to reboot, "systemctl default" or ^D to try again to boot into default mode.
Press Enter for maintenace
(or press Control-D to continue):_
After insering the root password and giving "jpurnalctl -xb" and "mount-a" (a command I found on internet used to diagnostic problem of this kind) I get the following logs:
You do not have the required permissions to view the files attached to this post.
Last edited by Mich-C on Tue Jan 15, 2019 11:32 am, edited 2 times in total.

Mich-C
Forum Novice
Forum  Novice
Posts: 55
Joined: Tue Nov 21, 2017 1:11 pm

Re: Can't login after sudden shutdown

#5

Post by Mich-C » Tue Jan 15, 2019 11:27 am

j2mcgreg wrote:
Mon Jan 14, 2019 11:02 am
Please post the results of inxi -F so we can have a clear idea of the hardware involved.
Sorry for the photos
You do not have the required permissions to view the files attached to this post.

User avatar
Adrian
Forum Veteran
Forum Veteran
Posts: 9371
Joined: Wed Jul 12, 2006 1:42 am

Re: Can't login after sudden shutdown

#6

Post by Adrian » Tue Jan 15, 2019 12:46 pm

I think you have some disk errors, you probably need to boot from Live USB and then use fsck to check you sda disk for errors. Not sure exactly what switches to use, I don't think it even happened to me so I don't really have experience with this so it's better to hear from people who have more experience recovering file system errors, but the important things is running the test from a live environment, that will make things easier, you'll also be able to copy and paste error message not only pictures of the screen.

philotux
Forum Regular
Forum Regular
Posts: 138
Joined: Sun Apr 22, 2018 12:57 pm

Re: Can't login after sudden shutdown

#7

Post by philotux » Tue Jan 15, 2019 1:27 pm

Gparted can also be used in live environment to run a check and repair by right-clicking on the partition in question, choosing "check" from the menu and applying from the toolbar.
It uses a command like:

Code: Select all

e2fsck -f -y -v -C 0
These are the details of a check process I just ran on /dev/sda9 on my disk (e2fsck -f -y -v -C 0 /dev/sda9):

Code: Select all

GParted 0.25.0 --enable-libparted-dmraid --enable-online-resize

Libparted 3.2

Check and repair file system (ext4) on /dev/sda9  00:00:00    ( SUCCESS )
    	
calibrate /dev/sda9  00:00:00    ( SUCCESS )
    	
path: /dev/sda9 (partition)
start: 243810304
end: 275267583
size: 31457280 (15.00 GiB)
check file system on /dev/sda9 for errors and (if possible) fix them  00:00:00    ( SUCCESS )
    	
e2fsck -f -y -v -C 0 /dev/sda9  00:00:00    ( SUCCESS )
    	
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure 
Pass 3: Checking directory connectivity 
Pass 4: Checking reference counts
Pass 5: Checking group summary information

23016 inodes used (2.34%, out of 983040)
64 non-contiguous files (0.3%)
5 non-contiguous directories (0.0%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 22993/15
319677 blocks used (8.13%, out of 3932160)
0 bad blocks
1 large file

20483 regular files
2524 directories
0 character device files
0 block device files
0 fifos
13 links
0 symbolic links (0 fast symbolic links)
0 sockets
------------
23020 files
e2fsck 1.43.4 (31-Jan-2017)
grow file system to fill the partition  00:00:00    ( SUCCESS )
    	
resize2fs -p /dev/sda9  00:00:00    ( SUCCESS )
    	
resize2fs 1.43.4 (31-Jan-2017)
The filesystem is already 3932160 (4k) blocks long. Nothing to do!

========================================

Mich-C
Forum Novice
Forum  Novice
Posts: 55
Joined: Tue Nov 21, 2017 1:11 pm

Re: Can't login after sudden shutdown

#8

Post by Mich-C » Tue Jan 15, 2019 6:14 pm

philotux wrote:
Tue Jan 15, 2019 1:27 pm
Gparted can also be used in live environment to run a check and repair by right-clicking on the partition in question, choosing "check" from the menu and applying from the toolbar.
I just had confirmation again that the mxlinux forum is the best forum of the world :number1: Thank you guys!
After running the "checkdisk" and closing Gparted, I immediately reopened thunar and I saw again all my partitions on the left bar. At this point I understood the problem was solved!
The only thing that worryes me is that Gparted failed to check/fix my Windows partion (OS).
I am not able to boot Windows from MXGrub, the grub installation didn't create any entry at all. I am still not sure if Grub doesn't list Windows because Windows was installed in legacy mode and I'm using MX in uefi mode, or because there are disk problems... What do you think?

(As you can see I left some disk space empty because I plan to reinstall Windows in uefi mode if I ascertain that it's not possible to boot it in legacy mode)
Check_Disk_Reports_For_Each_Partition.zip contains also the failed checkdisk for the Win/OS partition:

Code: Select all


GParted 0.25.0 --enable-libparted-dmraid --enable-online-resize

Libparted 3.2
Check and repair file system (ntfs) on /dev/sda1  00:00:02    ( ERROR )
     	
calibrate /dev/sda1  00:00:02    ( SUCCESS )
     	
path: /dev/sda1 (partition)
start: 1320118272
end: 1442998271
size: 122880000 (58.59 GiB)
check file system on /dev/sda1 for errors and (if possible) fix them  00:00:00    ( ERROR )
     	
ntfsresize -i -f -v /dev/sda1  00:00:00    ( ERROR )
     	
ntfsresize v2016.2.22AR.1 (libntfs-3g)
Device name : /dev/sda1
NTFS volume version: 3.1
Cluster size : 4096 bytes
Current volume size: 62914556416 bytes (62915 MB)
Current device size: 62914560000 bytes (62915 MB)
Checking for bad sectors ...
Bad cluster: 0xceb8e5 - 0xceb8f4 (16)
Bad cluster: 0xceb8f7 - 0xceb903 (13)
ERROR: This software has detected that the disk has at least 29 bad sectors.
****************************************************************************
* WARNING: The disk has bad sector. This means physical damage on the disk *
* surface caused by deterioration, manufacturing faults or other reason. *
* The reliability of the disk may stay stable or degrade fast. We suggest *
* making a full backup urgently by running 'ntfsclone --rescue ...' then *
* run 'chkdsk /f /r' on Windows and rebooot it TWICE! Then you can resize *
* NTFS safely by additionally using the --bad-sectors option of ntfsresize.*
****************************************************************************

========================================
Check and repair file system (ntfs) on /dev/sda2

========================================
You do not have the required permissions to view the files attached to this post.

philotux
Forum Regular
Forum Regular
Posts: 138
Joined: Sun Apr 22, 2018 12:57 pm

Re: Can't login after sudden shutdown

#9

Post by philotux » Tue Jan 15, 2019 7:46 pm

ERROR: This software has detected that the disk has at least 29 bad sectors.
****************************************************************************
* WARNING: The disk has bad sector. This means physical damage on the disk *
* surface caused by deterioration, manufacturing faults or other reason. *
* The reliability of the disk may stay stable or degrade fast. We suggest *
* making a full backup urgently by running 'ntfsclone --rescue ...' then *
* run 'chkdsk /f /r' on Windows and rebooot it TWICE!
Can you boot into Windows via BIOS?
How to Fix Hard Drive Problems with Chkdsk in Windows 7, 8, and 10

Mich-C
Forum Novice
Forum  Novice
Posts: 55
Joined: Tue Nov 21, 2017 1:11 pm

Re: Can't login after sudden shutdown

#10

Post by Mich-C » Wed Jan 16, 2019 6:13 pm

philotux wrote:
Tue Jan 15, 2019 7:46 pm
ERROR: This software has detected that the disk has at least 29 bad sectors.
****************************************************************************
* WARNING: The disk has bad sector. This means physical damage on the disk *
* surface caused by deterioration, manufacturing faults or other reason. *
* The reliability of the disk may stay stable or degrade fast. We suggest *
* making a full backup urgently by running 'ntfsclone --rescue ...' then *
* run 'chkdsk /f /r' on Windows and rebooot it TWICE!
Can you boot into Windows via BIOS?
How to Fix Hard Drive Problems with Chkdsk in Windows 7, 8, and 10
No because to boot Windows in bios mode the Windows bootloader has to be stored on the first sector of an mbr disk. (no gpt) The only solution would be booting Windows in bios mode through a uefi grub! At this point I'll mark this thread as solved and I think I'll start a new one to discuss about this.

Post Reply

Return to “Hardware /Configuration”