[SOLVED] Debian 9 Taking A Long Time To Boot Lots Of Errors
DebianThis forum is for the discussion of Debian Linux.
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.
Thank you Brains for explaining all of that information for me. I appreciate it.
I think I'd like to just boot into Mint and take care of it that way 'if' necessary.
-:::-I've learned not to do things with my Linux boxes when I'm tired. I will re-read your post #44 tomorrow after a good nights sleep and go from there.-:::-
Quote:
But it's highly unlikely you'll need to reinstall mdadm.
I believe you are right.
I don't think that mdadm has it's hooks in the boot process at all. You?
It is possible that mdadm was installed automatically because the installer noticed 3 drives were present.
Yeah, I'm thinking that's what happened:-
Anyway.....I re-read post #44 and basically I need to run this:
Code:
mount /dev/xxxx /mnt
for i in /dev /dev/pts /proc /sys /run; do sudo mount -B $i /mnt$i; done
chroot /mnt
apt install mdadm
exit
for i in /dev /dev/pts /proc /sys /run; do umount /mnt$i; done
umount /mnt
in the terminal of my Mint installation: only if mdadm needs to be installed again, and
than reboot into Debian....right?
When you go to uninstall via command line with apt, it'll give a list of everything that will get uninstalled before you confirm, copy and paste that list into a text editor and store it in Mint. Good to keep track.
When you go to uninstall via command line with apt, it'll give a list of everything that will get uninstalled before you confirm, copy and paste that list into a text editor and store it in Mint. Good to keep track.
Thank you-
If after removing mdadm Debian won't boot I'll have to check first if chroot is installed in Mint.
If after removing mdadm Debian won't boot I'll have to check first if chroot is installed in Mint.
I'll let you know what happens.
I haven't been following the rest of this thread so apologies if I'm off the mark here, but the chroot command comes in the coreutils package and thus is available in Mint. It's in /usr/sbin.
I haven't been following the rest of this thread so apologies if I'm off the mark here, but the chroot command comes in the coreutils package and thus is available in Mint. It's in /usr/sbin.
Considering that KDE is a RAM hog; that's great news.
Is your Debian Testing on an SSD or a regular HDD? How many seconds till a usable DE?
-:::-Taking a break than I'll rm that directory and mark this solved:--:::-
On an SSD, 16GB ram, I would say around 8-10 seconds.
You can also try command: sudo apt autoremove to see if that will remove the directory. Below is from the man page.
Code:
autoremove (apt-get(8))
autoremove is used to remove packages that were automatically installed to satisfy dependencies for other packages and are now no longer needed as dependencies changed or the package(s)
needing them were removed in the meantime.
You should check that the list does not include applications you have grown to like even though they were once installed just as a dependency of another package. You can mark such a
package as manually installed by using apt-mark(8). Packages which you have installed explicitly via install are also never proposed for automatic removal.
On an SSD, 16GB ram, I would say around 8-10 seconds.
You can also try command: sudo apt autoremove to see if that will remove the directory. Below is from the man page.
Code:
autoremove (apt-get(8))
autoremove is used to remove packages that were automatically installed to satisfy dependencies for other packages and are now no longer needed as dependencies changed or the package(s)
needing them were removed in the meantime.
You should check that the list does not include applications you have grown to like even though they were once installed just as a dependency of another package. You can mark such a
package as manually installed by using apt-mark(8). Packages which you have installed explicitly via install are also never proposed for automatic removal.
Thanks to you my Debian system now boots in 5 seconds to get me to the login.
My PS3 just locked up. Seems like there is always something going on.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.