[SOLVED] does'nt boot. ACPI vido bus. timed out waiting for device
Linux MintThis forum is for the discussion of Linux Mint.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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.
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?
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.
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
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.