Re: Target filesystem
On Fri, Jun 09, 2006 at 07:47:45AM -0400, Brent Clark wrote: > Hey all > > I seem to be experiencing problems booting up (Thank goodness for Knoppix) > > There are a host of errors, but the end message is: > > Target filesystem doesn't have /sbin/init > /bin/sh: can't access tty; job control turned off and then I get busybox > > From googling this seems a common problem. > > Would anyone know how to force this to work? you are posting to the wrong ml, debian-security has _nothing_ to do with early boot! and the actual error message is just above from what you pasted. > From what I gather it cant detect the filesystem (think its a modprobe > problem) do you run latest udev 0.093-1 version? (if not upgrade) do you pass the correct boot param in grub root=/dev/sdaX or /dev/hdaX presumambly. is your root device created? check ls $ROOT in rescue console. if not and with wrong udev and old 2.6.15 use modprobe ide-disk > If anyone can assist, it would be most appreciated. > > Kind Regards > Brent Clark please take the effort to research correct ml debian-user-$lang or file a bug against initramfs-tools if the problem persists. regards -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Target filesystem
On Fri, Jun 09, 2006 at 07:47:45AM -0400, Brent Clark wrote: > I seem to be experiencing problems booting up (Thank goodness for Knoppix) Why not just a Debian rescue CD? > There are a host of errors, but the end message is: > Target filesystem doesn't have /sbin/init I think your kernel just get a wrong device for root filesystem, i.e. the actual root fs is on, say, /dev/hdX and the kernel uses /dev/hdY (which is readable, but not root, e.g. /var, /usr or whatever). > Would anyone know how to force this to work? > From what I gather it cant detect the filesystem (think its a modprobe > problem) Since you have offered next to zero information about your problem, I may just guess: 1) You have a stock kernel but no initrd specified in boot configuration. 2) Your kernel gets wrong root fs. I think against the "can't detect filesystem" idea because a device with unknown filesystem is unmountable. P.S. You should definitely provide more info about your setup. Telepathic skills are not common among people. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Target filesystem
Brent Clark wrote: Hari Sekhon wrote: Are you getting a message saying it's attempting to resume before this happens? Hi Hari I just remembered everything was fine, until I dist-upgrade yesterday. Udev was upgraded. Maybe I just reinstall. Regards Brent Clark -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Target filesystem
Hari Sekhon wrote: Are you getting a message saying it's attempting to resume before this happens? Hi Hari I cant remeber seeing a resume (will need to reboot my machine and recheck), but in the interim Could you please explain what is been tried to be resumed (whats happening). Kind Regards Brent Clark -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Target filesystem
Brent Clark wrote: Hey all I seem to be experiencing problems booting up (Thank goodness for Knoppix) There are a host of errors, but the end message is: Target filesystem doesn't have /sbin/init /bin/sh: can't access tty; job control turned off and then I get busybox From googling this seems a common problem. Would anyone know how to force this to work? From what I gather it cant detect the filesystem (think its a modprobe problem) If anyone can assist, it would be most appreciated. Kind Regards Brent Clark Are you getting a message saying it's attempting to resume before this happens? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Target filesystem
Hey all I seem to be experiencing problems booting up (Thank goodness for Knoppix) There are a host of errors, but the end message is: Target filesystem doesn't have /sbin/init /bin/sh: can't access tty; job control turned off and then I get busybox From googling this seems a common problem. Would anyone know how to force this to work? From what I gather it cant detect the filesystem (think its a modprobe problem) If anyone can assist, it would be most appreciated. Kind Regards Brent Clark -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
