|
Target file system doesn't have /sbin/init
When I boot up Etch, I occasionally (but increasinlgy often) get the message
Target file system doesn't have /sbin/int
after which the booting process comes to a halt and I get thrown into BusyBox.
Rebooting once or twice eventually does get me into the system.
I haven't got a clue what could be wrong. Someone suggested reinstalling udev but that didn't help a bit. In fact, since I did, I have the impression that I'm getting the error more often if anything.
Could this be related to the "controller bug" that is/was known to affect Etch: on systems with multiple controllers, Etch may fail to recognize the proper controller. I have three controllers (Promise PCI Sata card, onboard JMicron and Intel ICH8) so that would leave plenty of room for mistakes.
Or could it be a consequence of the boot directory being on xfs? I hear that XFS does have some adverse effects on GRUB but then again, I'm booting from the GRUB that was installed by Mandriva, which is on ext3. I originally installed Etch with Lilo on the MBR but that failed (I suspect this was precisely because of the controller bug I already mentioned). Whatever, everything ran fine until a month ago - then those messages started coming up; on top of that, I was suddenly having audio issues where the system failed to recognize my Soundblaster and started using OSS by default instead of ALSA (I have been able to solve this onein the meantime, by the way).
Last edited by jay73; 06-21-2007 at 01:37 PM.
|
