[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.
After many days of reading through pages of google searches it's become clear what the error:
Code:
mdadm:No arrays found in fonfig file or automatically
is all about.
The etc/mdadm/mdadm.config file is simply for creating and managing Raid arrays.
Since I do not have any Raid arrays set up I'm thinking about removing the mdadm.config file all together and see if I still get the error at boot up.
I've looked for the mdadm file on Mint and MX-18 and that config file does not exist. I don't know for sure if this file was automatically generated or somehow was created due to an update.
I'll have to find out with certainty over the next several days and more searching/reading if removing that file is going to be an issue.
I suspect that removing that file won't be a problem as there aren't any Raid arrays set up.
After many days of reading through pages of google searches it's become clear what the error:
Code:
mdadm:No arrays found in fonfig file or automatically
is all about.
The etc/mdadm/mdadm.config file is simply for creating and managing Raid arrays.
Since I do not have any Raid arrays set up I'm thinking about removing the mdadm.config file all together and see if I still get the error at boot up.
I've looked for the mdadm file on Mint and MX-18 and that config file does not exist. I don't know for sure if this file was automatically generated or somehow was created due to an update.
I'll have to find out with certainty over the next several days and more searching/reading if removing that file is going to be an issue.
I suspect that removing that file won't be a problem as there aren't any Raid arrays set up.
Rename it to mdadm.config.bac and reboot. At least it can be restored if actually needed. The /etc/mdadm directory don't exist on my Debian testing. Nor is the mdadm package installed on mine, maybe uninstalling the package altogether.
I have grub-common installed, so likely won't be an issue. Which also suggests the reverse depends is not entirely accurate, I also have udisks2 installed but none of the others.
root@Willy:/home/jo# aptitude install mdadm
The following NEW packages will be installed:
exim4-base{a} exim4-config{a} exim4-daemon-light{a} guile-2.2-libs{a} libgnutls-dane0{a} libgsasl7{a}
libkyotocabinet16v5{a} liblzo2-2{a} libmailutils5{a} libntlm0{a} libunbound8{a} mailutils{a}
mailutils-common{a} mdadm psmisc{a}
0 packages upgraded, 15 newly installed, 0 to remove and 0 not upgraded.
Need to get 10.4 MB/11.1 MB of archives. After unpacking 59.6 MB will be used.
Do you want to continue? [Y/n/?] n
Abort.
root@Willy:/home/jo#
Here's a suggestion:
The code above shows the 14 dependency packages that would get installed if I were to install mdadm. If you run command: apt-get remove mdadm and these are the only other packages that would need be uninstalled also, means mdadm is not installed as a dependency for something else, it may have been installed as a "suggested" or "recommended" package, which in turn means you don't really need it. As long as the list to be removed only contains these or some of these packages, you'd be safe to remove it. It should ask for confirmation before going ahead. If you have synaptic installed, it'll do the same.
If it returns saying there are other packages not in the list above that will need be removed, then you will know which packages depend on it and can decide then whether you want to go ahead or not.
root@Willy:/home/jo# aptitude install mdadm
The following NEW packages will be installed:
exim4-base{a} exim4-config{a} exim4-daemon-light{a} guile-2.2-libs{a} libgnutls-dane0{a} libgsasl7{a}
libkyotocabinet16v5{a} liblzo2-2{a} libmailutils5{a} libntlm0{a} libunbound8{a} mailutils{a}
mailutils-common{a} mdadm psmisc{a}
0 packages upgraded, 15 newly installed, 0 to remove and 0 not upgraded.
Need to get 10.4 MB/11.1 MB of archives. After unpacking 59.6 MB will be used.
Do you want to continue? [Y/n/?] n
Abort.
root@Willy:/home/jo#
Here's a suggestion:
The code above shows the 14 dependency packages that would get installed if I were to install mdadm. If you run command: apt-get remove mdadm and these are the only other packages that would need be uninstalled also, means mdadm is not installed as a dependency for something else, it may have been installed as a "suggested" or "recommended" package, which in turn means you don't really need it. As long as the list to be removed only contains these or some of these packages, you'd be safe to remove it. It should ask for confirmation before going ahead. If you have synaptic installed, it'll do the same.
If it returns saying there are other packages not in the list above that will need be removed, then you will know which packages depend on it and can decide then whether you want to go ahead or not.
Not sure if I want to rm mdadm and it's dependencies or not.
First I'm going to run dpkg -L and see if it's already installed.
The good news is Debian still boots it just takes a while because the error shows about 20 times in tty before taking me to the log in.
Another thing I'm going to try is to boot to a Live Linux CD and try to rename that file. I'll see what that get's me:-
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.