linuxdeepin / developer-center

Deepin developer center, provide developer wiki and community forum.
452 stars 73 forks source link

'Cannot open access to console, the root account is locked.' System won't boot #1586

Closed Germo20 closed 2 years ago

Germo20 commented 4 years ago

Describe the bug

Since a couple of days ago this message shows in every single boot, most of the times System won't boot. No matter what boot option(from the given ones) I chose, system won't boot. Pressing 'Enter' just repeats the message and will eventually cause system halt until I manually reboot. I cannot type any other input or command from there. With some patience and reboots, system will randomly boot after a couple of 'Enter' and work 'normally'. I'm running DeepIn 15.11 x64 with recently(today) applied updates on a Dell Inspiron 3400 with 8th Gen Intel i5. System is installed on an WD Green M.2 SSD. Any other info I'll be happy to provide once the system randomly boots.

PS: Only change since the first boot with this problem is an USB Wireless mouse that I connected before system boot. Mouse was previosly used on the notebook, but always connected after system boot.

  1. Problem reproduce frequency Every boot ever since first time. I'd upload a dd dump of my root partition if needed. Operating system :deepin Desktop environment :dde

To Reproduce

Normal boot

Screenshots

IMG_20191111_233423

Enviroments:

Distro & Version

Linux DeepIn 15.11 x64

Related package version

Additional context

RMoroni commented 4 years ago

Sometimes i have this problem, but i follow these steps to correct:

On the Grub screen, press 'e' to edit boot options. On the linux line, got to the end of line and put this: 'break=mount' (separated by a space after the last option). Press F10 to boot. Then you will see the initramfs screen (that's why the option 'break=mount'). Now run the file system check command: 'fsck.ext4 dev/sdaX' for your Deepin file systems (/, /home), except for EFI and Swap partition. If some of the file systems return some problems (inconsistency or something like this), then the fsck will show you the option to correct, so you accept all the corrections (by press 'y' for each correction). After check the file systems (and eventually correct some problems), write 'exit' and press Enter, so you will boot normally.

It always works for me, good luck for u!

Germo20 commented 4 years ago

Thanks for the answer. I'll try it tonight and comment the results. That aside, it's not really good that this will happen from time to time randomly lol. If any developer wants or need more info, I'll try to make a dump of current root partition status so they can replicate error, hopefully.

patyiscoding commented 4 years ago

Same thing happening to my comp on every boot. Typically, the first one is unsuccessful, I press 'Enter' and the system halts on the 'deepin' logo. After multiple manual reboots (1 or 2 are most often enough), it will finally show the login screen, though still showing the message.

RMoroni commented 4 years ago

Do you have a Dell laptop too? Every month i have this problem...

patyiscoding commented 4 years ago

Nope, Acer here. Started happening about ~8 months ago, mostly isn't very problematic; though, last week, it wouldn't boot for the whole day. I had to run chkdsk on my Windows partition and it finally seemed to fix the issue. Kinda weird

RMoroni commented 4 years ago

Well, I hope v20 solves this. Let's wait.

patyiscoding commented 4 years ago

Funnily enough, the ‘I won’t boot no matter what’ mode just came back 🤷🏼‍♀️ 5 boot tries and 30 mins in with no success so far

Germo20 commented 4 years ago

I'm mostly able to boot the system with a couple of 'enter's using safe mode in the boot opitons. It's still a lot of random and I got used to sleep the pc through the week instead of shutting down. I've just decided to re-install and now it boots normally, but it still 'thinks' there's a mouse permanently connected. Also I get the same message with 'unexpected device config size' on every boot, although it starts normally.

@RMoroni I've never been able to do the chkdsk, device it's locked while booted and I don't know how to run it from grub(only accesible thing when on boot loop). Also yes, I insist on DeepIn only in hopes they fix this with version 20.

PS: Also, I have / and /home in different disks. I've tried formatting only / and the boot loop continued. I had to format both disks so it can boot 'normally' again.

Germo20 commented 4 years ago

On the linux line, got to the end of line and put this: 'break=mount' (separated by a space after the last option).

I have not found where to put this to get to console.

RMoroni commented 4 years ago

C4880B82-712D-4C7F-9CE3-F4E427721CF5

After press ‘e’, you’ll see this screen. You have the ‘linux’ line, then you put ‘break=mount’ in the end (press F10 to boot). I put this to force initramfs screen...on this screen you can check all your FS.

Germo20 commented 4 years ago

I got it now. I was able to do the checks and both finished almost instantly with no error(ofc since I re installed on sunday). Nothing else has changed, I still get the devices message and can't enable 'Disable touchpad when a mouse is present' option because it will disable touchpad anyways.

RMoroni commented 4 years ago

Funnily enough, the ‘I won’t boot no matter what’ mode just came back 🤷🏼‍♀️ 5 boot tries and 30 mins in with no success so far

Did you try check your file systems? From other OS or initramfs...

mRrSandMan-gif commented 4 years ago

Sometimes i have this problem, but i follow these steps to correct:

On the Grub screen, press 'e' to edit boot options. On the linux line, got to the end of line and put this: 'break=mount' (separated by a space after the last option). Press F10 to boot. Then you will see the initramfs screen (that's why the option 'break=mount'). Now run the file system check command: 'fsck.ext4 dev/sdaX' for your Deepin file systems (/, /home), except for EFI and Swap partition. If some of the file systems return some problems (inconsistency or something like this), then the fsck will show you the option to correct, so you accept all the corrections (by press 'y' for each correction). After check the file systems (and eventually correct some problems), write 'exit' and press Enter, so you will boot normally.

It always works for me, good luck for u!

It worked with deepin 20

StoreSatan commented 3 years ago

To get Kali to boot into console mode:

(useful on slow and bad hardware such as ARM Raspberry Pi) Just simply run the following commands:

1: root@kali:~# systemctl get-default 2: root@kali:~# systemctl set-default multi-user.target 3: root@kali:~# sudo reboot

After a reboot, Kali will start in consol mode everytime after this.

To revert these changes, all you have to do is use this command:

root@kali:~# systemctl set-default graphical.target root@kali:~# sudo reboot

After a reboot, Kali will start normaly with GUI login screen everytime again.

Good luck champ! /cheers

Germo20 commented 3 years ago

Sometimes i have this problem, but i follow these steps to correct: On the Grub screen, press 'e' to edit boot options. On the linux line, got to the end of line and put this: 'break=mount' (separated by a space after the last option). Press F10 to boot. Then you will see the initramfs screen (that's why the option 'break=mount'). Now run the file system check command: 'fsck.ext4 dev/sdaX' for your Deepin file systems (/, /home), except for EFI and Swap partition. If some of the file systems return some problems (inconsistency or something like this), then the fsck will show you the option to correct, so you accept all the corrections (by press 'y' for each correction). After check the file systems (and eventually correct some problems), write 'exit' and press Enter, so you will boot normally. It always works for me, good luck for u!

It worked with deepin 20

By the time I read this I had already changed SO to Debian 9. At some point I started having a similar behaviour and I fixed this yesterday with those instructions :D I'll probably be changing to DeepIn 20, because in the end, Debian has que same errors itself, as it seems.

Also, I added -y to fsck.ext4, because I had a long list of error to confirm.

Quartz15 commented 3 years ago

hi, im having a little bit of trouble. i followed RMoroni's steps and when i got to the part where im meant to put in "fsck.ext4 dev/sdaX" i get a message saying "fsck.ext4: no such file or directory while trying to open dev/sdaX possibly non-existent device?"

please help...

Quartz15 commented 3 years ago

and i have Deepin 20

RMoroni commented 3 years ago

Hi @Quartz15. You have to replace the 'X' by a number. If you have only one partition, it'll be 'dev/sda1', if you have more, apply the command 'fsck.ext4' on the others ext4 partitions, e.g. 'fsck.ext4 dev/sda1', 'fsck.ext4 dev/sda2', etc.

Quartz15 commented 3 years ago

ok thank you ill try that now

Quartz15 commented 3 years ago

i wasn't sure how many partitions i had so i tried 'fsck.ext4 dev/sda1,2 and 3. when i did 'sda1' it said "bad magic number in super-block while trying to open dev/sda1". however when i did 'sda2' and '3' it would tell how many files and blocks i had ?

RMoroni commented 3 years ago

Ok, it usually this happens when you try to run a fsck.ext4 on a file system different from what was specified. For Linux we have: ext2, ext3 and ext4. 'fsck.ext4' is for a ext4 file system, you can try e2fsck (the command is the same: 'e2fsck -y /dev/hda5) for ext2, ext3 and ext4. Sometimes, in the end of output, it say what file system that partition are using. If your pc is using UEFI, dev/sda1 probably is the EFI System, so you don't need to run fsck on it. You need to check (by running 'fsck' or 'e2fsck') your Linux file systems (where is your / and /home). I recommend you to run 'fsck.ext4 -y dev/sda2' if you have only Deepin on your pc. If you have another OS, try to run 'fdisk -l' or other way to see what partitions you have in your pc.

Quartz15 commented 3 years ago

if i were to put in 'fsck.ext4 -y dev/sda2 what would happen ?

RMoroni commented 3 years ago

If 'dev/sda2' is a ext4 file system, it'll be checked for errors. In the case of finding errors, fsck will try to resolve them.

Quartz15 commented 3 years ago

i put in fsck.ext4 -y dev/sda1 it said at the bottom that dev/sda1 contains a vfat file system labelled 'EFI'

RMoroni commented 3 years ago

So you have to try 'fsck.ext4 -y dev/sda2'

Quartz15 commented 3 years ago

ok

Quartz15 commented 3 years ago

It said 'boot : clean, 419/98304 files 62073/393216 blocks'

RMoroni commented 3 years ago

It means that dev/sda2 is ok

Quartz15 commented 3 years ago

so what now ?

Quartz15 commented 3 years ago

is there anything else i should type ?

RMoroni commented 3 years ago

If you have more partitions (with a Linux file system), you should try to run the fsck on it. Then, run 'exit'.

Quartz15 commented 3 years ago

thanks it worked :D

Quartz15 commented 3 years ago

Sorry me again, it was working good for a little bit then I turned it back on and now I'm stuck at the deepin loading screen

Does anyone have any suggestions on what I should do ?

Quartz15 commented 3 years ago

I would like some help please thank you

Quartz15 commented 3 years ago

20210203_211225.jpg

Does anyone know what this means?

Numic150 commented 3 years ago

Ok, it usually this happens when you try to run a fsck.ext4 on a file system different from what was specified. For Linux we have: ext2, ext3 and ext4. 'fsck.ext4' is for a ext4 file system, you can try e2fsck (the command is the same: 'e2fsck -y /dev/hda5) for ext2, ext3 and ext4. Sometimes, in the end of output, it say what file system that partition are using. If your pc is using UEFI, dev/sda1 probably is the EFI System, so you don't need to run fsck on it. You need to check (by running 'fsck' or 'e2fsck') your Linux file systems (where is your / and /home). I recommend you to run 'fsck.ext4 -y dev/sda2' if you have only Deepin on your pc. If you have another OS, try to run 'fdisk -l' or other way to see what partitions you have in your pc.

guys hi, tried what u recommended above but as a result I've got the following: entered: fsck.ext4 dev/sda1 (...2, 3 too) got: e2fsck 1.44.5 (15-Dec-2018) fsck.ext4: No such file or directory while trying to open dev/sda1

Do you have any ideas what I should do? Sorry, this is my first experience with linux deepin 20...

thanks in advance

derekzyl commented 3 years ago

I'm sorry where will I apply these: . You have to replace the 'X' by a number. If you have only one partition, it'll be 'dev/sda1', if you have more, apply the command 'fsck.ext4' on the others ext4 partitions, e.g. 'fsck.ext4 dev/sda1', 'fsck.ext4 dev/sda2', etc. Cause there is no place to run these I presume... Cause it keeps bringing up error

RMoroni commented 3 years ago

You need to run fsck.ext4 dev/sdaX where the big X is the number of your partition, probably you will have 'dev/sda1' for EFI and 'dev/sda2' for / . So, in this case the command is fsck.ext4 dev/sda2

orly2001 commented 3 years ago

need help on kali linux []()20210422_192132.jpg

Numic150 commented 3 years ago

do u know what to do with this?

deepin screen issuie

ср, 14 апр. 2021 г., 23:21 derekzyl @.***>:

I'm sorry where will I apply these: . You have to replace the 'X' by a number. If you have only one partition, it'll be 'dev/sda1', if you have more, apply the command 'fsck.ext4' on the others ext4 partitions, e.g. 'fsck.ext4 dev/sda1', 'fsck.ext4 dev/sda2', etc. Cause there is no place to run these I presume... Cause it keeps bringing up error

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/linuxdeepin/developer-center/issues/1586#issuecomment-819806484, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGABIB237Y6FFAVRDE2VCODTIX2NDANCNFSM4JL5QSSA .

IsaiahTek commented 3 years ago

Same thing happened to my Dell machine running on Deepin 20.x.y. I used fsck.ext4 /dev/sda7 to access the data partition (where the /home also is). Then saw the error and entered yes for all (a)

RMoroni commented 3 years ago

do u know what to do with this? deepin screen issuie ср, 14 апр. 2021 г., 23:21 derekzyl @.***>: I'm sorry where will I apply these: . You have to replace the 'X' by a number. If you have only one partition, it'll be 'dev/sda1', if you have more, apply the command 'fsck.ext4' on the others ext4 partitions, e.g. 'fsck.ext4 dev/sda1', 'fsck.ext4 dev/sda2', etc. Cause there is no place to run these I presume... Cause it keeps bringing up error — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#1586 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGABIB237Y6FFAVRDE2VCODTIX2NDANCNFSM4JL5QSSA .

@Numic150 if you still need an answer, the problem is that you're trying to run a filesystem check for EXT4 on a NTFS filesystem (probably Windows?). You need to run the EXT4 (that is the command fsck.ext4) on EXT4 partitions, like on your root partition (where is the / ?) or /home .

tsic404 commented 2 years ago

your disk get some errors, you need to fix those errors to boot system.This is not a bug and the issue will close.

tsic404 commented 2 years ago

If you still have any problem, you can reopen this issue.