LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux Mint (https://www.linuxquestions.org/questions/linux-mint-84/)
-   -   does'nt boot. ACPI vido bus. timed out waiting for device (https://www.linuxquestions.org/questions/linux-mint-84/doesnt-boot-acpi-vido-bus-timed-out-waiting-for-device-4175684112/)

grimpeur 10-23-2020 10:13 AM

does'nt boot. ACPI vido bus. timed out waiting for device
 
1 Attachment(s)
Hi,

linux mint 18 stopped with some difficulties, then cannot fully reboot.
I tried fsck and says it's clean.

Attached journal error. No clue. What happens?

Thanks

mrmazda 10-23-2020 11:29 PM

What were the difficulties preceding the stoppage?

What is the mount point in /etc/fstab matching the UUID of the device that timed out?

grimpeur 10-26-2020 03:09 PM

1 Attachment(s)
Thanks. Nothing particular. Last time I normally switched off PC, it was quite slow in stopping.

Second sentence you wrote, sounded me impossible to understand. After reading on the web I typed in the terminal cat /etc7fstab

"media" disk has apparently problems. It is document disk, not system one

mrmazda 10-26-2020 04:38 PM

If you append ",nofail" after .utf8 in /etc/fstab and then boot you should be able to start Mint and then should be able to better diagnose and possibly repair the document disk. If you succeed to repair it, it should automatically return to being automounted.

grimpeur 10-27-2020 02:54 PM

Wow. It works. such UIID seemed corresponding to the document disk (now removed and connected to another pc) and not to boot one. Now If I inquire all UIID of system and data disk, I receive a different UUID and not ****1A608F. Is it possible UUID changes?

Shall I make further diagnostics now?

mrmazda 10-27-2020 07:05 PM

UUIDs do not change unless some process has explicitly been applied to change it. Usually it gets created when the filesystem is created (formatted with mkfs*), and stays that way, but there are ways to change one, such as using 'tune2fs -U'. What you need to do is make sure every line in fstab has only valid components. If a UUID there does not exist, it needs to be changed to a valid one, or the line containing it removed or converted to a comment. Entries in fstab for devices that will not always be available need a nofail or noauto option in order to avoid what happened to you.

If you have multiple external drives only used occasionally, you'd be better off assigning each a unique volume LABEL that makes sense to you, and then mounting by LABEL or by by-label instead of humanly immemorable and perplexing UUIDs.

grimpeur 10-28-2020 03:15 PM

Thank you very much for help and deep explanation.
Yeah, I did it for "discodati", maybe on windows, when I used to had dual boot. Seems it is not possible to label NTFS disks however

mrmazda 10-28-2020 06:27 PM

Quote:

Originally Posted by grimpeur (Post 6179651)
Seems it is not possible to label NTFS disks however

All my NTFS filesystems have labels:
Code:

man ntfslabel


All times are GMT -5. The time now is 12:30 PM.