> > > > Thank you, it was "dep" indeed! > > Then remove those additional files, check that MODULES=most is set in > /etc/initramfs-tools/initramfs.conf, do a "update-initramfs -u -kall", > and you should be good to go. >
The driver policy file? It is safe to just remove it? Btw, isn't a bit dangerous to use -kall? The documentation says the kall will make the change affect all the initramfs on the machine. If the one actually working gets modified and starts to have problems I could not be able to boot for good, couldn't? Just to explore the safest way, if i make a copy of the initramfs actually present in /boot (/boot/initrd.img-3.16.0-4-amd64 (bad one, not booting) and /boot/initrd.img-3.2.0-4-amd64 (good one, booting) ), then I do update-initramfs and it doesn't work, to restore the previous situation, rewriting the modified initramfs file with the old one is enough? Or alternatively I can create a new initramfs from scratch and boot that one? > > > Reading here, though I think they were talking about ubuntu, ( > > https://ubuntuforums.org/showthread.php?t=1365365) there is a module to > > manage raid called dmraid. Maybe including that could solve the problem? > > No, dmraid is for Controller-based SoftRAID, often used with Windows Great, thanks! betta
