boot - /bin/sh: can't access tty; job control turned off

Hi,

Does the kernel display any error messages before entering the shell prompt?

If possible, can you take a digital picture of the console when it has entered the initramfs shell prompt, or failing this copy the error messages down... Once you've done this please attach the output to this bug. Thanks.

Thanks for your prompt reply. I do not get any flashing messages, just the Ubuntu progress bar. Here's what I see when boot drops to the prompt:
BusyBox v1.1.3 (Debian 1:1.1.3-3ubuntu3) Built-in shell (ash)
Enter 'help' for a list of built-in commands.

/bin/sh: can't access tty; job control turned off
(initramfs)

Seeing the prompt response from you folks, I started poking around. In casper.log I have:
/init: /init: 1: cannot open /dev/fd0: no such device or address
(this is repeated a dozen or so times, then at the end:)
Unable to find a medium containing a live file system.

This box has a CD rom, floppy, and an IDE hard drive.

Hi,

Using Fiesty Beta live CD on my brand new Core 2 Duo System, Intel GA-965P-DS3P, 2GB ram, nVidia 7300 GT PCIE Graphics Hauppage PVR150 PCI IDE CD-ROM and a SATA2 HDD. I get the same (?) or a similar problem with system starting to boot and goes to;

udevd-event[2065] : run_program '/sbin/modprobe' abnormal exit

BusyBox v1.1.3 (Debian 1:1.1.3-3ubuntu3) Built-in shell (ash)
Enter 'help' for a list of built-in commands.

/bin/sh: can't access tty; job control turned off
(initramfs)

Machine has passed memtest, CD is ok I have checked. When I get dropped into busy box, if I cat casper.log I am told

Unable to find a medium containing a live file system

I get a similar message (different version of busybox and no udev error) if I try with a 6.06LTS live cd (I havent checked casper.log yet) any ideas? Will put up photos as attachemnts in a minute.

P.S I also got udev complaining about fd0 (as others in forums etc appear to be seing) however I turned the floppy drive off in BIOS and that went away.

Fiesty 7.04 Beta error

Dapper 6.06 LTS error

Retried 6.06LTS and there is nothing in casper.log. When trying 6.06 the splash gets to mounting root filesystem, which doesnt suceed.

going `ls /cdrom` from the busybox shell shows that /cdrom is empty, I presume this is where the live file system is supposed to be?

Back to Ubuntu 7.04 beta, tried putting SATA controller into AHCI in BIOS, no change. I also see that my CDROM is configured as slave, so I will try making it a master next.

CDROM is now master - no change still get dropped to busybox.

Also when I noted in https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/96084/comments/3 that the CD checked out ok I should clarify what I meant.

The CD checks out on another machine, it does not check out on this machine, if I try to check the CD for defects the ubuntu splash starts with the `bouncy slider` progress bar and then I get;

udevd-event[2061] : run_program '/sbin/modprobe' abnormal exit

BusyBox v1.1.3 (Debian 1:1.1.3-3ubuntu3) Built-in shell (ash)
Enter 'help' for a list of built-in commands.

/bin/sh: can't access tty; job control turned off
(initramfs)

splash progress on ubuntu 6.06

so I have now booted without the quiet and splash kernel options and have noticed an opps during startup, console scroll back photo sequence to follow.

last one :)

removed Hauppage PCI card, SATA HDD and USB Flash drive and still get the same problem

pulled an IDE HDD, with a working install of Fiesty + kernel updates etc from another machine and it boots just fine, dmesg attached.

attached lspci

> Mainboard: GA-965P-DS3P
This should be fixed in a daily build.

Thomas: Thanks for the pointer, download a full iso again, ouch, I live in NZ and have a data cap of 1 Gb/month, so have pretty much screwed my data cap for the month getting the Beta iso

Will try to see if I can use debian-installer or ubuntu-installer from my working HDD (IDE) to get the non-working (SATA) one installed

So its been a night of learning!! you dont have to get the full iso there are MinimalCDs https://help.ubuntu.com/community/Installation/MinimalCD once you have the initial install underway you can drop to a shell (Ctrl+Alt+F#) and use a CD (the tray will open) or a USB flash drive to frantically copy all debs you have previously downloaded from another machine via USB or writeable CD to /target/var/cache/apt/archives (drastically reducing the amount of downloading the MinimalCD installer will have to do).

Then you can try mounting the squashfs image in the LiveCD to extract the debs on there, only there arent any wthin the compressed filesystem (all availiable debs are on the CD outside the squashfis image)! The way the LiveCD installer works is it copies the contents of casper/filesystem.squashfs over the drives mounted on /target and then attempts to update the nevessary packages, so the LiveCD hasnt got many debs on it.

The only gotcha with the live CD is the MinimalCD doesnt haev squashfs support (/poc/filesystems does not list squashfs) so by the time I had worked out which package I needed to get linux-image-2.6.20-14-generic which contains squashfs.ko to enable me to mount filesystem.squashfs image myself the MinimalCD installer had started downlading linux-image-2.6.20-14-generic. No point in downloading it twice and slowing down the transfer rate - off to be.

2 reccommendations;

1. It might be a good idea for the MinimalCD to come with squashfs support for crazies like me in the future :)

2. It might be good to able to download off the web individual precompiled kernel modules of the correct version, i.e squashfs.ko from `lib/modules/2.6.20-14-generic/kernel/ubuntu/fs/squashfs/squashfs.ko` rather than having to download all 28.4 MB of linux-image-2.6.20-14-generic_2.6.20-14.22_i386.deb which would have allowed me to mimic the LiveCD installer and speed up the install process.

Oh yeah by the way the current MinimalCD boots just fine on a GA-965P-DS3P!

Reads previous post and hangs head in shame at spelling and grammar! (I am supposed to be off to bed)

For the interested I did try installing ubiquity (ubuntu-installer), etc on my working IDE system, ignoring the notes in synaptic about it not doing a lot that was terribly useful, but even when I managed to disable the migration assistant, /dev/sda1 was already mounted and ubiquity gives no GUI way of bypassing the migration-assistant stage - bug?, which I sorted by passing a command line switch to ubuquity. With no LiveCD in the system there was no filesystem.squashfs for ubiquity to dump over /target so it died pretty early in the process.

Then I explored Netbooting and MinimalCD's I got halfway through installing tftp on another box until I realised that the MinimalCD was so small.

It is really time for sleep now!

I believe I have a similar problem, but I fail to notice the modprobe abnormal exit, or it doesn't happen in my case. There are other things as well:
1. The 7.04 LiveCD boots only from my CD drive (IDE Slave) but not on my DVD drive (IDE Master) (April 4th image). This happens always. Whenever I boot from my CD drive it tries the floppy a number of times and then boots ok, but when I try to boot from the DVD drive it tries the floppy a whole lot more and then fails with the well known error message.
2. If I wait a bit I get the following error messages:
[ 60.101981] ata2.01: failed to set xfermode (err_mask=0x4)
[ 95.974137] ata2.01: failed to set xfermode (err_mask=0x4)
[ 131.706301] ata2.01: failed to set xfermode (err_mask=0x4)
[ 136.705051] ata2.00: failed to set xfermode (err_mask=0x40)
3. Looking through the init and casper scripts I understand they are looking for a loop device in /sys/block, but the only items I have there are:
ram0 - ram15 fd0 sda sr0
sda - my hard drive, sr0 - my dvd drive, my cd drive is not there (though not needed when the LiveCD is in the DVD drive)
4. comparing the output of udevinfo from my HDD and DVD drives, the DVD seems to be missing information: The E: ID_SERIAL is empty and E: ID_SERIAL_SHORT contains unreadable characters, while they are both ok for my HDD

lspci attached

master ar2ro: have you tried disabling your floppy drive in bios to reduce the console spew? so you can see what is actucally happening.

Have you tried booting without the quiet and splash kernel command line options and then scrolling back through the obot messages to see where it dies?

To do this throw the LiveCD in the drive boot from the LiveCD and when you get to the LiveCD boot menu press F6 and edit the boot command line removing the "quiet" and "splash" options.

kmicic: how are you getting on with your bug? it looks like I hijacked you bug with a possibly unrelated issue - apologies if I did.

Don't worry about it, Mark. Your active participation is just what the
community needs to make linux better. Mine's an old laptop - I just
thought I'd do my part and report that the v. 7 live CD doesn't boot.
Good luck with yours.

Paul

Mark wrote:
> kmicic: how are you getting on with your bug? it looks like I hijacked
> you bug with a possibly unrelated issue - apologies if I did.
>
>

Mark: No, I didn't disable the floppy, I'll try it a bit later today. I did boot without the quiet and splash options, but it scrolls damn fast during the boot so I can't really keep up with all those messages, and I don't know how to scroll back up once I'm in the initramfs prompt. I did even boot with the debug kernel option but the debug log didn't help me too much. Is there a way to get all those boot messages to a file available from the initramfs?

Ar2ro: Shift+PgUp should scroll up Shift+PgDown should scroll down (once you have scrolled up) although the size of the scroll back buffer is limited.

I am not sure if `dmesg` will work from the busybox prompt, it is normally the way you see the contents when in a terminal or shell.

If dmesg doesnt work and you need a way to get back beyond the limit of the buffer, the size of the boot buffer appears to be adjustable when compiling the kernel - which wont help you a lot, so the alternative is to try a video camera - funny I know but I´ll admit to using it for this very bug!

This bug also appears to be related to our bug https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/84964

dmesg doesn't work under busybox, I already tried that. I made a few photos with my mobile phone though they're low quality. Right now I'm downloading the today's daily image, and I'll get to testing right after I get it. I attached the few LQ photos I made, though they won't be much help probably.

Ok, I tried the most up-to-date image and here's what I got:

1. The situation is exactly the same trying out of the box. It runs on my CD drive, but fails and ends in initramfs prompt when booted from my DVD drive.
2. I tried looking through the messages as far as I could go, and there was *no* modprobe abnormal exit, so as far as I can tell, that's not the case for me. Something else is failing.
3. I tried the solution suggested in the bug 84964 you pointed, and indeed, adding `irqpoll ` to kernel options solves the problem of booting from my DVD drive.

I copied over the logs and lspci outputs from both boots (from CD and DVD drives) so if you need any of those just ask.

Also, since I booted from the DVD without the splash and quiet options I also found two more things:

1. There is a failed action during system shutdown, i.e.
`* Unmounting temporary filesystems...
umount: /cow not found [fail]`
2. When the CD is ejected at the last stage of the shutdown, pressing ENTER doesn't work, it just appends ^M and does nothing more... is input ignored without usplash running?

Well that's about it, if you need any more info or testing just let me know.

ar2ro: can you please upload a dmesg from the working setup, bug 84964 is related to jmicron pata/sata controllers (I have one on my Gigabyte GA-965P-DS3P motherboard) however your lspci doesnt appear to indicate any jmicron hardware - I have checked the attachment to comment 25 but I could be blind :)

Here's the dmesg from the boot from my DVD drive (with kernel option irqpoll). As far as I know I don't have a jmicron controller ;) Not to mention any SATA support at all. It's a pretty old machine.

Now that I think about it, by the working setup you might mean my working edgy installation, so here's the dmesg from this one as well ;)

I see the identical problem on a Dell PowerEdge 4400 server running 7.04 beta. This also works fine with 6.04.

I have almost the exact same HW configuration as Mark (Core 2 Duo E6400, Gigabyte GA-965P-DS3 (Intel 965P Chipset), 2Gb RAM, nVidia 7300 GT, JMicron controller enabled with 250 Gb SATA drive on AHCI mode, IDE DVD-ROM and DVD-RW attached to the motherboard's only IDE port.

I've tried to start the Kubuntu 7.04 beta live system / installation dvd from both DVD Drives and the booting process stops in the same way as Mark stated.

"I've tried to start the Kubuntu 7.04 beta live system / installation dvd from both DVD Drives and the booting process stops in the same way as Mark stated." (Guido).

That goes for me too -- with an Nvidia 6800 video card.

Guido Scalise: you need to get a newer kernel seing as you are using the LiveCD you need to get a new LiveCD :( or you could try disabling the JMicron controller from BIOS and sticking with the intel SATA ports see bug 84964 (havent tried myself) although you would need a SATA CD/DVD drive to boot the LiveCD from. Which I didnt have and you dont appear to have.

hap0: see comments to Guido

Dave Ritchie: dmesg from working 6.04? lpsci?

Master Ar2ro: I havent forgotten you, tomorrow is Friday after that its the weekend and I should have some time to look at your hardware specs (dmesg etc)

Mark: the problem here is that I have my HDD (with a Windows partition) connected in the JMicron controller (as the ICH8 doesn't provide NCQ nor AHCI mode -ICH8R does-), and both DVD drives are on the JMicron IDE port as well, and I don't want to end messing up my Windows installation.

FWIW, I just started having this problem (boot to busybox prompt) on reboots after doing update/upgrade a couple hours ago. Been using 7.04b on ASUS Z62FM laptop, with few problems (like no sound) until now. Tried booting to 2.6.20-13-generic recovery mode, and it started up ok (and with sound again). -- Bob

I'm now experiencing this problem after installing updates this morning. I'm booting the old 2.6.20-13-generic, X didn't load at first, had to change the driver in the xorg.conf back to nv from nvidia in order to get X to load at all. Everything was working perfectly until this morning's update.

Since I noticed the info that kernel is fixed (on irc #ubuntu+1 topic) I tried booting the latest daily build image, but it's still the same for me. It doesn't boot from my DVD drive without the irqpoll kernel option (just ends in the busybox as usual). Just thought I'd let you know, since I don't know if that info was to consider this bug as well ;)

Thanks for the reply - I will check this out.

Best regards,
Dave Ritchie

-----Original Message-----
From: Master Ar2ro [mailto:<email address hidden>]
Sent: Tuesday, April 17, 2007 12:48 PM
To: <email address hidden>
Subject: [Bug 96084] Re: boot - /bin/sh: can't access tty; job control
turned off

Since I noticed the info that kernel is fixed (on irc #ubuntu+1 topic) I
tried booting the latest daily build image, but it's still the same for
me. It doesn't boot from my DVD drive without the irqpoll kernel option
(just ends in the busybox as usual). Just thought I'd let you know,
since I don't know if that info was to consider this bug as well ;)

--
boot - /bin/sh: can't access tty; job control turned off
https://bugs.launchpad.net/bugs/96084
You received this bug notification because you are a direct subscriber
of the bug.

I'm still stuck with the same error. I have a Core 2 Duo E6400, Gigabyte GA-965P-DS3 (Intel 965P Chipset), 1Gb RAM, nVidia 6800 Ultra. I only have IDE drives right now--both and 80GB IDE HDD, and IDE DVD-RW attached to the motherboard's only IDE port. I have the JMicron setting in BIOS set to IDE.

I've tried to start the Kubuntu 7.04 beta live system and the booting process stops in the same way as reported here:

udevd-event[2061] : run_program '/sbin/modprobe' abnormal exit

BusyBox v1.1.3 (Debian 1:1.1.3-3ubuntu3) Built-in shell (ash)
Enter 'help' for a list of built-in commands.

/bin/sh: can't access tty; job control turned off
(initramfs)

Steve,

The -13 kernel burnt into the 7.04 beta live CD will not work, you
need to get kernel -14 or later.

On 4/18/07, Steven Boothe <email address hidden> wrote:
> I'm still stuck with the same error. I have a Core 2 Duo E6400, Gigabyte
> GA-965P-DS3 (Intel 965P Chipset), 1Gb RAM, nVidia 6800 Ultra. I only
> have IDE drives right now--both and 80GB IDE HDD, and IDE DVD-RW
> attached to the motherboard's only IDE port. I have the JMicron setting
> in BIOS set to IDE.
>
> I've tried to start the Kubuntu 7.04 beta live system and the booting
> process stops in the same way as reported here:
>
> udevd-event[2061] : run_program '/sbin/modprobe' abnormal exit
>
> BusyBox v1.1.3 (Debian 1:1.1.3-3ubuntu3) Built-in shell (ash)
> Enter 'help' for a list of built-in commands.
>
> /bin/sh: can't access tty; job control turned off
> (initramfs)
>
> --
> boot - /bin/sh: can't access tty; job control turned off
> https://bugs.launchpad.net/bugs/96084
> You received this bug notification because you are a direct subscriber
> of the bug.
>

On 4/7/07, Master Ar2ro wrote:
> I believe I have a similar problem, but I fail to notice the modprobe abnormal exit, or it doesn't happen in my case. There are other things as well:
> 1. The 7.04 LiveCD boots only from my CD drive (IDE Slave) but not on my DVD drive (IDE Master) (April 4th image). This happens always. Whenever I boot from my CD drive it tries the floppy a number of times and then boots ok, but when I try to boot from the DVD drive it tries the floppy a whole lot more and then fails with the well known error message.
> 2. If I wait a bit I get the following error messages:
> [ 60.101981] ata2.01: failed to set xfermode (err_mask=0x4)
> [ 95.974137] ata2.01: failed to set xfermode (err_mask=0x4)
> [ 131.706301] ata2.01: failed to set xfermode (err_mask=0x4)
> [ 136.705051] ata2.00: failed to set xfermode (err_mask=0x40)
> 3. Looking through the init and casper scripts I understand they are looking for a loop device in /sys/block, but the only items I have there are:
> ram0 - ram15 fd0 sda sr0
> sda - my hard drive, sr0 - my dvd drive, my cd drive is not there (though not needed when the LiveCD is in the DVD drive)
> 4. comparing the output of udevinfo from my HDD and DVD drives, the DVD seems to be missing information: The E: ID_SERIAL is empty and E: ID_SERIAL_SHORT contains unreadable characters, while they are both ok for my HDD

Ar2ro:

Since edgy, ubuntu is now using libata in place of drivers/ide etc,
this means the handling of ide drives has changed very significantly.
Handling of hdds and cds/dvds has become more integrated.

Please check out bug 103410 which may be more what you are
experiencing and for some kernel related xfermode error see
http://<email address hidden>/msg03088.html

Cant help on the udev stuff unfortunately.

I confirm that I am having similar problems. I mention some things here: http://ubuntuforums.org/showthread.php?p=2486432#post2486432

Under Edgy, I experience random freezes and it appears that the JMicron controller has something to do with this according to you and some bug posts. However, my understanding is that Feisty fixes some/all of these problems? For the time being, I have decided to disable the JMicron stuff in BIOS and see how Edgy fares. The error messages do go away, but I have yet to see if I still experience crashing.

 Earlier, I tried installing Feisty to see if it remedied the problem. No luck. I am not able to even reach the installation. I get an error message like the one in the appended image (some of the numbers may have been different before i disabled jmicron in bios).

Follow-up:
So, as far as edgy is concerned, disabling the JMicron controller does nothing to fix the problem :). Also, when I ran the install CD for feisty after reenabling it, the numbers following "ata" are something more liky 7.00 and 6.00.

Some more information. I noticed messages like the following in my /var/log/dist-upgrade/term.log (the X and Y are just some version numbers from the kernel, but it seemed to be overall universal so i omitted the specific ones):

update-initramfs: Generating /boot/initrd.img-2.6.X-Y-generic
cp: cannot state `/etc/udev/rules.d/05-options.rules': No such file or directory

cp: cannot state `/etc/udev/rules.d/85-brltty.rules': No such file or directory

Searching for GRUB installation directory ... found: /boot/grub
You shouldn't call /sbin/update-grub. Please call /usr/sbin/update-grub instead!

1. /usr/share/doc/grub/NEWS.Debian.gz
file and follow its instructions.
Your /etc/kernel-img.conf needs to be updated. Read grub's NEWS.Debian[1]
Running postinst hook script /sbin/update-grub.
cp: cannot state `/etc/udev/rules.d/05-options.rules': No such file or directory

cp: cannot state `/etc/udev/rules.d/85-brltty.rules': No such file or directory
update-initramfs: Generating /boot/initrd.img-2.6.17-11-generic
Running depmod.

After I reboot, I get almost what I did when trying to boot the cd:

Starting up...
Loading, please wait...
[ 35.998671] ata5.00: failed to set xfermode (err_mask=0x4)
....(similar ones repeat about 5 times)...
    Check root= bootarg cat /prov/cmdline
    or midding modules, devices: cat /proc/modules ls /dev
ALERT! /dev/disk/by-uuid/40c43667-f776-4843-8e5d-b69ac3628546 does not exist. Dropping to a shell!

From here on I get exactly what I got when trying to boot the CD (the BusyBox stuff I posted above.

Man, i have a compaq n160 and i tryed to install ubuntu 7.04 i have no OS im my notebook, but i cant install ubuntu... the message i have is this message

BusyBox v1.1.3 (Debian 1:1.1.3-3ubuntu3) Built-in shell (ash)
Enter 'help' for a list of built-in commands.

/bin/sh: can't access tty; job control turned off
(initramfs)

How to solve it? need information?

The system doesnt boot!! i cant install it!

Regards,
Fabio

Having the same problem with a pretty old Compaq Evo. Ubuntu 6.10 works fine on this box, but I cannot even boot 7.04 livecd. I've tried every boot option I know of :)
Here is my dmesg and lspci -vv outputs from 6.10.

Hi
I struggled for many hours with the problem "can't access tty; job control turned off". My last ditch effort was to burn the iso image onto a CD. Previoulsy, I had burned the image onto a DVD. Using a plain old CD solved this problem for me

good luck

LiveCD NOT BOOTING of on many configurations is classified as: "importance - MEDIUM"?! What would be "importance highest" - a PC exploding?
This is a showstopper, not a 'medium impact' bug! I believe that a distribution should be stopped until this is rectified.

I have the same "/bin/sh: can't access tty; job control turned off" when trying to boot from LiveCD 7.04 (CDs, not DVDs).
Configuration: motherboard Gigabyte GA-7N400 Pro2 with AMD Athlon XP 3000+, 1GB RAM, nothing unusual in hardware.
LiveCD which DOES NOT boot: Kubuntu 7.04
LiveCDs which boots fine: Ubuntu 7.04. Yes, Ubuntu 7.04 boots fine for me, it is Kubuntu 7.04 which does not.
Also booting fine: Ubuntu 6.10, Kubuntu 6.10, Xubuntu 6.10

cheers, Derek

Hi all, i tryed to install with the Xubuntu CD but has the same problem..
Then i tryed to install with ubuntu 7.04 alternate CD and now i'm using ubuntu... all the installarion was ok!

Regards,
Fabio

I am having the same problem. My computer config is: Core 2 Duo E6300, Gigabyte GA-965P-S3, 2 GB RAM, eVga 7900GS, Pioneer DVR-112D.

I have tried a few different configurations. If I have the FDD in or if I have it disabled, I get the error above. If I have no FDD in, but it's enabled in the BIOS, I get "[xx.xxxx] Buffer I/O error on device fd0, logical block 0".

Booting into the alternate CD, I get to the "Detect CD Drive" step. but it can't find one. Listing the contents of /dev/, I can see that there is no "cdrom". My DVD drive is connected to the only IDE port on the board.

I hope this information helps anyone trying to fix this problem. I really want to try out Feisty.

I am having the same issue with my Toshiba Tecra S3 (PTS30C-MT101E), which was working with 6.10 quite happily. I followed the instructions to upgrade, downloaded the update from the net and rebooted into the error below:

BusyBox v1.1.3 (Debian 1:1.1.3-3ubuntu3) Built-in shell (ash)
Enter 'help' for a list of built-in commands.

/bin/sh: can't access tty; job control turned off
(initramfs)

I downloaded the final release of the LiveCD and everything works fine now. I installed it last night without any incident.

I have a Core 2 Duo E6400, Gigabyte GA-965P-DS3 (Intel 965P Chipset), 1Gb RAM, nVidia 6800 Ultra. I only have IDE drives right now--both and 80GB IDE HDD, and IDE DVD-RW attached to the motherboard's only IDE port. I have the JMicron setting in BIOS set to IDE.

I have the same problem hp omnibook xpress, ubuntu and kubuntu 7.04 final.. I tried in one desktop and it`s run ok.. that say it´s not the cd.. y have a Kubuntu herd 4 and that work well, tested a couple of minutes before this post...

Following may be useless, but on the hope that it might add some insight for some problem-solver, I will post it:
I installed Ubuntu 6.06 from an ISO disk I burned. I installed it on a Western Digital 80Gb external Hard Drive (USB) connected to a Compaq Presario with an Athlon 3000+ processor. It installed and booted from the external drive fine. I then updated to Ubuntu 7.04 Desktop. The 7.04 install again booted fine from the WD external drive, once, twice, maybe three times. On the third or fourth time I tried to boot I got the /bin/sh: can't access tty; job turned off message.

Because I know nothing about Ubutu commands and the help menu is not at all intuitive for me, I simply gave up, shut down and attempted to reboot--no luck--same result: /bin/sh: can"t access....etc.

Using the same ISO disk as before I reinstalled 6.06 (erasing the disk in the process) on the WD external drive. I've rebooted fromn the same external drive twice since then with no problems. I will not attempt to update to 7.04 unless I see that there is a definitive fix to the can't access tty issue.

One final observation, Although I'm still new to Ubuntu, I have experienced the phenomenon of having an install boot faultlessly once, twice or three times, only to fail on the fourth and successive boot attempts. In that previous circumstance I had installed the system on an 8 Gb USB-connected flash drive.

As was the case with 7.04, the 6.06 version that was reinstalled on the Western Digital hard drive booted twice uneventfully. The third attempt to boot produced the /bin/sh: can't access....etc. message. Although millions may successfully be runnning Ubuntu, after many weeks of playing with it, I have concluded that I am evidently not sophisticated enough to use Ubuntu. Good luck to all in sorting out this bug.

if you have a WD drive, go to the WD website and download one of their
ISO's that can check your drive. You may have a bad drive.

Also to try is one of the older kernel versions that appear in GRUB when
you start up. That worked for me on my laptop.

Larry Wolfe wrote:
> As was the case with 7.04, the 6.06 version that was reinstalled on the
> Western Digital hard drive booted twice uneventfully. The third attempt
> to boot produced the /bin/sh: can't access....etc. message. Although
> millions may successfully be runnning Ubuntu, after many weeks of
> playing with it, I have concluded that I am evidently not sophisticated
> enough to use Ubuntu. Good luck to all in sorting out this bug.
>
>

Many thanks for the advice. I followed both suggestions.

From the Western Digital site I downloaded something called Data Lifeguard
and used it to run an extended diagnostic test of the drive. After running
48 minutes and testing every sector, the drive passed. So I'm reasonably
sure that the drive is not the problem.

I have two possible kernels bto use: 2.6.15-28-386 and 2.6.15-26-386. I get
the same /bin/sh can't access tty...etc. message with each one. There is
also a "Recovery" option under each kernel. I tried that once and at some
point in the boot process, it wanted me to enter a command. I had no idea
what I needed to enter to continue the boot so I just exited and shut down.

The thing that baffles me so is that if I reinstalled 6.06 from the ISO disk
that I burned, the thing will boot fine for one or two times, then it fails
and gives the /bin/sh can't...etc.

Thanks again for the suggestions. I've subscribed to receive all the posts
on this bug, but if you see a fix or work-around elsewhere, I'd be grateful
if you'd pass it on to me.

Regards,
Larry Wolfe
----- Original Message -----
From: "gmerrick" <email address hidden>
To: <email address hidden>
Sent: Friday, April 27, 2007 9:44 PM
Subject: Re: [Bug 96084] Re: boot - /bin/sh: can't access tty; job control
turned off

if you have a WD drive, go to the WD website and download one of their
ISO's that can check your drive. You may have a bad drive.

Also to try is one of the older kernel versions that appear in GRUB when
you start up. That worked for me on my laptop.

Larry Wolfe wrote:
> As was the case with 7.04, the 6.06 version that was reinstalled on the
> Western Digital hard drive booted twice uneventfully. The third attempt
> to boot produced the /bin/sh: can't access....etc. message. Although
> millions may successfully be runnning Ubuntu, after many weeks of
> playing with it, I have concluded that I am evidently not sophisticated
> enough to use Ubuntu. Good luck to all in sorting out this bug.
>
>

--
boot - /bin/sh: can't access tty; job control turned off
https://bugs.launchpad.net/bugs/96084
You received this bug notification because you are a direct subscriber
of the bug.

Hi:

1. I do have three forms of Ubuntu 7.04: The "live desktop cd", the "alternate cd", and the "dvd"

2. I have 4 totally different machines:

a. Three "pata" controlled machines, of various plumage
b. One "sata" controlled machine

3. None of the above mentioned forms of Ubuntu 7.04 are working with the "pata" controlled machines: I get the now famous "can't access tty; job control turned off", followed by several "initramfs" messages

4. The "live desktop cd" IS working with the "sata" controlled machine

5. I have "upgraded" one "pata" machine from Ubuntu 6.10 to Ubuntu 7.04 via the internet/repositories, without any problems; that system is using kernel 2.6.17

My personal Opinion: There IS a difference between Ubuntu 6.10 amd Ubuntu 7.04..... From the above I do conclude that Ubuntu 7.04 was written for "sata" controlled machines, and does NOT support "pata" controlled machines.

What is the difference??: It might be the 2.6.20 kernel used by Ubuntu 7.04, in which case I believe Ubuntu will have to re-write Ubuntu 7.04, this time with "pata" supported.... I do believe that people using "sata" controlled systems won't have that many problems!!

Hi again:

In order not to confuse people with my "pata and sata controlled systems", I am adding these, defining those terms:

1. http://en.wikipedia.org/wiki/AT_Attachment

2. http://en.wikipedia.org/wiki/Serial_ATA

It's a kernel module problem. My suggestion is that you back up your
important data, and then use the 6.10 live cd and do a clean install.

this time round, make sure that you have a /home partition and a /root
partition. That way you don't need to reformat your entire hard drive
every time.

Glen Merrick

Larry Wolfe wrote:
> Many thanks for the advice. I followed both suggestions.
>
> >From the Western Digital site I downloaded something called Data Lifeguard
> and used it to run an extended diagnostic test of the drive. After running
> 48 minutes and testing every sector, the drive passed. So I'm reasonably
> sure that the drive is not the problem.
>
> I have two possible kernels bto use: 2.6.15-28-386 and 2.6.15-26-386. I get
> the same /bin/sh can't access tty...etc. message with each one. There is
> also a "Recovery" option under each kernel. I tried that once and at some
> point in the boot process, it wanted me to enter a command. I had no idea
> what I needed to enter to continue the boot so I just exited and shut down.
>
> The thing that baffles me so is that if I reinstalled 6.06 from the ISO disk
> that I burned, the thing will boot fine for one or two times, then it fails
> and gives the /bin/sh can't...etc.
>
> Thanks again for the suggestions. I've subscribed to receive all the posts
> on this bug, but if you see a fix or work-around elsewhere, I'd be grateful
> if you'd pass it on to me.
>
> Regards,
> Larry Wolfe
> ----- Original Message -----
> From: "gmerrick" <email address hidden>
> To: <email address hidden>
> Sent: Friday, April 27, 2007 9:44 PM
> Subject: Re: [Bug 96084] Re: boot - /bin/sh: can't access tty; job control
> turned off
>
>
> if you have a WD drive, go to the WD website and download one of their
> ISO's that can check your drive. You may have a bad drive.
>
> Also to try is one of the older kernel versions that appear in GRUB when
> you start up. That worked for me on my laptop.
>
> Larry Wolfe wrote:
>
>> As was the case with 7.04, the 6.06 version that was reinstalled on the
>> Western Digital hard drive booted twice uneventfully. The third attempt
>> to boot produced the /bin/sh: can't access....etc. message. Although
>> millions may successfully be runnning Ubuntu, after many weeks of
>> playing with it, I have concluded that I am evidently not sophisticated
>> enough to use Ubuntu. Good luck to all in sorting out this bug.
>>
>>
>>
>
>

I don't know how to answer that one, I know that this computer I am
using now has 6 pata drives and 2 sata drives in it and 2 of the pata
drives are on a pci addon card.

If you cannot get pata working in 7.04 there may be additional issues
with that particular kernel that they released with it.

one thing to check is modprobe and do an internet search to see what
kernel modules your chipsets require. One other thing to try is the
alternate I386 distrobution as opposed to the live cd.

Glen Merrick

hoagies wrote:
> Hi:
>
> 1. I do have three forms of Ubuntu 7.04: The "live desktop cd", the
> "alternate cd", and the "dvd"
>
> 2. I have 4 totally different machines:
>
> a. Three "pata" controlled machines, of various plumage
> b. One "sata" controlled machine
>
> 3. None of the above mentioned forms of Ubuntu 7.04 are working with
> the "pata" controlled machines: I get the now famous "can't access tty;
> job control turned off", followed by several "initramfs" messages
>
> 4. The "live desktop cd" IS working with the "sata" controlled machine
>
> 5. I have "upgraded" one "pata" machine from Ubuntu 6.10 to Ubuntu 7.04
> via the internet/repositories, without any problems; that system is
> using kernel 2.6.17
>
> My personal Opinion: There IS a difference between Ubuntu 6.10 amd
> Ubuntu 7.04..... From the above I do conclude that Ubuntu 7.04 was
> written for "sata" controlled machines, and does NOT support "pata"
> controlled machines.
>
> What is the difference??: It might be the 2.6.20 kernel used by Ubuntu
> 7.04, in which case I believe Ubuntu will have to re-write Ubuntu 7.04,
> this time with "pata" supported.... I do believe that people using
> "sata" controlled systems won't have that many problems!!
>
>

hehe....
Pata = EIDE
SATA = serial ata

glen

hoagies wrote:
> Hi again:
>
> In order not to confuse people with my "pata and sata controlled
> systems", I am adding these, defining those terms:
>
> 1. http://en.wikipedia.org/wiki/AT_Attachment
>
> 2. http://en.wikipedia.org/wiki/Serial_ATA
>
>

Regarding the discussion of 7.04 being geared for SATA vs. PATA, let me just reiterate that it works fine in my PATA only box.

I downloaded the final release of the LiveCD and installed it without any of these issues that I had from the previous beta.

I have a Core 2 Duo E6400, Gigabyte GA-965P-DS3 (Intel 965P Chipset), 1Gb RAM, nVidia 6800 Ultra. I only have IDE drives right now--both and 80GB PATA/IDE HDD, and PATA/IDE DVD-RW attached to the motherboard's only PATA/IDE port. I have the JMicron setting in BIOS set to IDE.

Cheers.

Many thanks to hoagies, gmerrick and hop0 for the suggestions. I knew I had a lot of research to do before I could even comprehend what was being said (I'm an old guy who is barely literate in computers), so I took the easy way out. I again downloaded the desktop verison of 7.04, burned an ISO CD and installed it on the Western Digital external hard drive (USB connection). Even though I know the definition of insanity is repeating the same process and expecting different results, it appears that at least this one time, it may have worked.

In all previous installations of of 7.04 and 6.06 the system never displayed the boot options at start-up, now when the machine is powered up, the several boot options are displayed with Ubuntu Kernel 2.6.20-15-generic being the default which will boot unless I intervene and select another. Since this latest installation of 7.04 I must have successfuly rebooted six or seven times...not once did I encounter the dreaded /bin/sh: cant access....etc. Fingers will remain crossed for quite a while, but so far so good.

I wish I could add some insight that would be helpful to people who continue to have trouble with this particular bug, but, even if it was me (and not software or hardware) doing something wrong, I don't know what it could have been.

Thanks again to all and good luck!

In my case I get this boot error SOME TIMES after succesful installation (3 times in about 10 boots)
I all 3 cases I rebooted with ctrl-alt-del and the next boot was succesfull

whoops...my misunderstanding. I certainly hope Ubuntu get's this fixed
soon because I have quite a few servers at work that have sata HD's in
them, that I want to be able to upgrade.

hap0 wrote:
> Regarding the discussion of 7.04 being geared for SATA vs. PATA, let me
> just reiterate that it works fine in my PATA only box.
>
> I downloaded the final release of the LiveCD and installed it without
> any of these issues that I had from the previous beta.
>
> I have a Core 2 Duo E6400, Gigabyte GA-965P-DS3 (Intel 965P Chipset),
> 1Gb RAM, nVidia 6800 Ultra. I only have IDE drives right now--both and
> 80GB PATA/IDE HDD, and PATA/IDE DVD-RW attached to the motherboard's
> only PATA/IDE port. I have the JMicron setting in BIOS set to IDE.
>
> Cheers.
>
>

I'm glad you finally got it working. Just remember to back up your
important data, just in case!

Glen Merrick

-------------------------

Larry Wolfe wrote:
> Many thanks to hoagies, gmerrick and hop0 for the suggestions. I knew I
> had a lot of research to do before I could even comprehend what was
> being said (I'm an old guy who is barely literate in computers), so I
> took the easy way out. I again downloaded the desktop verison of 7.04,
> burned an ISO CD and installed it on the Western Digital external hard
> drive (USB connection). Even though I know the definition of insanity
> is repeating the same process and expecting different results, it
> appears that at least this one time, it may have worked.
>
> In all previous installations of of 7.04 and 6.06 the system never
> displayed the boot options at start-up, now when the machine is powered
> up, the several boot options are displayed with Ubuntu Kernel
> 2.6.20-15-generic being the default which will boot unless I intervene
> and select another. Since this latest installation of 7.04 I must have
> successfuly rebooted six or seven times...not once did I encounter the
> dreaded /bin/sh: cant access....etc. Fingers will remain crossed for
> quite a while, but so far so good.
>
> I wish I could add some insight that would be helpful to people who
> continue to have trouble with this particular bug, but, even if it was
> me (and not software or hardware) doing something wrong, I don't know
> what it could have been.
>
> Thanks again to all and good luck!
>
>

I have an ASUS P4B266 Mainboard (Intel 845D Chipset, ide disk and cdrom) and a 1.6GHZ Pentium. I get permanently the same error booting the 7.04 CD.
However kubuntu 6.061 works fine on the system.
Looking into casper.log: the system tries to open /dev/fd0, /dev/sr0 and finally fails with message: "Unable to find a medium containing
a live file system". But somehow the system accesses /dev/hda (I have a noisy disk). From the initramfs system I tried to access (mount) the cdrom: but I was not successful.
I looks to me like the cdrom device driver of the initramfs does not work properly (one of the modules).

In my case (were the error was random) I later also noted random hard-disk errors (my system needed fsck and a lot of crosslinks and other errors were found).
I will fix this and see if the can't access tty will appear again

I've been looking whenever I can for solutions/work-arounds and I found that someone else with a similar problem created a "Core 2 Duo Support" page in the Ubuntu Wiki (https://wiki.ubuntu.com/Core_2_Duo_Support). I don't know if this can help everyone here but, for anyone here who doesn't see their CD drive in /dev/, there is a solution that I haven't tested yet. It appears to be a problem with PATA support, so your two options are to either get a SATA CD drive or get an adapter to connect your PATA drive to the SATA connector. When my new drive arrives, I will get back to you with the results.

Hi,

I just upgraded a Ubuntu desktop to version 7.04 from 6.10 (which worked perfectly) and experienced the same problem with the "can't access tty; job control turned off" error. However, I found the solution for this particular machine quite simple and painless.

When the machine was booting, I pressed escape at the Grub prompt to go to the boot menu (see the first photo). By default, Ubuntu was trying to boot the kernel "2.6.20-15-386" (top of the list, second photo), but I found if I selected the "2.6.20-15-generic" kernel, the computer booted with no problem! (Actually, at first X complained of not being able to load the "nvidia" driver, so I simply changed the entry in my xorg.conf back to "nv" - but I think this is a separate issue).

Once the computer was up and running, I edited the "/boot/grub/menu.lst" file to boot the "2.6.20-15-generic" kernel by default, and the compter has been running like a charm ever since.

If anyone wants more info, I'm happy to help!

The computer is a Pentium III, with an ATA hard drive.

Hi,
I spent my weekend trying to get 7.04 liveCD of Ubuntu, kubuntu installed on my SAMSUNG X10 (Laptop) and it was a catastrophic failure. And this with the official CDs. It is interesting to note that I can reinstall Ubuntu 6.10 from the LiveCD without any problem. I don't know how to help you to fix this bug since none of the things I have done work. I have found a temporary solution that I wont detail there because it might be considered as starting a distro war. Which is absolutely not my intention.

If anyone wants more info, I would be happy to help as much as I can.

As I said in previous posts, this is now a kernel issue which Ubuntu
needs to deal with.

Glen Merrick

yml wrote:
> Hi,
> I spent my weekend trying to get 7.04 liveCD of Ubuntu, kubuntu installed on my SAMSUNG X10 (Laptop) and it was a catastrophic failure. And this with the official CDs. It is interesting to note that I can reinstall Ubuntu 6.10 from the LiveCD without any problem. I don't know how to help you to fix this bug since none of the things I have done work. I have found a temporary solution that I wont detail there because it might be considered as starting a distro war. Which is absolutely not my intention.
>
> If anyone wants more info, I would be happy to help as much as I can.
>
>

I am not sure to understand why you believe that this is a kernel issue
because it does not happen with other recent distribution like for example
mandriva 2007.1.

On 5/9/07, gmerrick <email address hidden> wrote:
>
> As I said in previous posts, this is now a kernel issue which Ubuntu
> needs to deal with.
>
> Glen Merrick
>
> yml wrote:
> > Hi,
> > I spent my weekend trying to get 7.04 liveCD of Ubuntu, kubuntu
> installed on my SAMSUNG X10 (Laptop) and it was a catastrophic failure. And
> this with the official CDs. It is interesting to note that I can
> reinstall Ubuntu 6.10 from the LiveCD without any problem. I don't know
> how to help you to fix this bug since none of the things I have done work. I
> have found a temporary solution that I wont detail there because it might be
> considered as starting a distro war. Which is absolutely not my intention.
> >
> > If anyone wants more info, I would be happy to help as much as I can.
> >
> >
>
> --
> boot - /bin/sh: can't access tty; job control turned off
> https://bugs.launchpad.net/bugs/96084
> You received this bug notification because you are a direct subscriber
> of the bug.
>

It is a kernel issue because Ubuntu builds the kernel to suit their
distro, in previous versions of the kernel (2.6.17.10) SATA devices such
as on my latop work fine, however later versions of the kernel
(2.6.17.11 onwards including 2.6.20.15) do not work and cause the error
that we are all complaining about.

I also know that Ubuntu builds their kernels because one of the projects
I work on at my employer uses Ubuntu exclusively on a bunch of servers.
We use the desktop build and even though Ubuntu should be able to access
8GB of ram in version 5.10, it cannot because of the build specification
that Ubuntu chose when developing their kernel.

Glen Merrick

yml wrote:
> I am not sure to understand why you believe that this is a kernel issue
> because it does not happen with other recent distribution like for example
> mandriva 2007.1.
>
>
> On 5/9/07, gmerrick <email address hidden> wrote:
>
>> As I said in previous posts, this is now a kernel issue which Ubuntu
>> needs to deal with.
>>
>> Glen Merrick
>>
>> yml wrote:
>>
>>> Hi,
>>> I spent my weekend trying to get 7.04 liveCD of Ubuntu, kubuntu
>>>
>> installed on my SAMSUNG X10 (Laptop) and it was a catastrophic failure. And
>> this with the official CDs. It is interesting to note that I can
>> reinstall Ubuntu 6.10 from the LiveCD without any problem. I don't know
>> how to help you to fix this bug since none of the things I have done work. I
>> have found a temporary solution that I wont detail there because it might be
>> considered as starting a distro war. Which is absolutely not my intention.
>>
>>> If anyone wants more info, I would be happy to help as much as I can.
>>>
>>>
>>>
>> --
>> boot - /bin/sh: can't access tty; job control turned off
>> https://bugs.launchpad.net/bugs/96084
>> You received this bug notification because you are a direct subscriber
>> of the bug.
>>
>>
>
>

Hi:

I am getting sick of this bug without (k)ubuntu 7.04, (or kernel 2.6.20-x), doing anything about this bug., like issuing a new version of the distro, fixing it.

Besides this thread, there are others running in parallel with this thread, all covering the same topic.

Here are some of my postings::

http://ubuntuforums.org/showthread.php?t=421849&highlight=96084

http://www.linuxmint.com/forum/viewtopic.php?t=2546

"Linux Mint" is a very nice distro, 98% ubuntu based.

I have the same problem, but with subsequent ctrl-alt-delete the computer boots well.
I have no sata devices, I have checked all logs and can't find something noteworthy.
If it is a kernel issue I think version 2.6.20 urgently needs an fix, because I have a double swap space problem as well: https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/96715

I have a problem with mandriva, never solved, but with ubuntu work with a
Floopy disk, same problem ubuntu and Kubuntu,

--
Dany Aguilar

After 2 weeks of smooth operation I am sure I no longer have any issue with my hard disks (it was a loose connector causing me some problems before) but I still get this error every once in a while [1]. So I can positively confirm what I earlier said:

> In my case I get this boot error SOME TIMES after successful
> installation (3 times in about 10 boots)
> I all 3 cases I rebooted with ctrl-alt-del and the next boot was successful

(Again note that the error appears when I boot from my hard disk after a succesful installation NOT when I boot from the liveCD)
___________
[1] I rarely reboot my PC so I can't make good statistics.

/bin/sh: can't access tty; job control turned off

I m new in ubuntu ....but meet this problem when installing it...but finally i solve the problem...i think for those who hav floppy disk in computer will seldom/never meet this problem..cause my computer don't hav floppy disk...and my solution is:-
1. Get a pendrive atleast 1gb and copy all the ubuntu cd's content to the pendrive.
2. Then boot ubuntu cd with the pendrive plug in
3. Then install ubuntu.

P/s :I think this problem relate to the dev0 and dev1(don't know correct or not about the letter dev0) it seems like the ubunto boot will put the cd-rom as dev0 if dun hav floppy disk in that computer, if there is floppy there it will be dev0 for floppy and dev1 for cd-rom and i think the booting will only read the data from dev1 hence if there is no floppy disk there the cd-rom will be dev0 then the system can't read data from a null dev1...but if we add a pendrive or cd-rom into computer then the path dev1 will be the pendrive or extra cd-rom(if we add cd-rom to it then better we direct boot from that extra cd-rom.

I have 7.04 installed on two systems, one is a desktop using an Abit IC7-G with two WD250's hanging off the Intel SATA controller in software RAID1. The other is a server using an Asus P5W64WS with a PCIe-based 3Ware 9650SE 8 port card with two drives in RAID1 and the remainder in RAID6 (read: no drives are connected to the motherboard SATA / IDE controllers). In other words, two totally different systems that use completely different hardware and methods to access the root filesystem. The desktop is a relatively old machine (built 2 years ago), while the server is new. Both systems experience the bug....though I admit I don't see it as frequently on the server since I seldom boot it.

I'm attaching a screenshot of the end of the boot process from the desktop machine running 2.6.20-15-generic. I can't use the recently upgraded kernel (2.6.20-16-generic) because it hangs the box just after it jumps from the bootloader. No error...just a black screen. Not much to go on, I know, but I figured I'd throw my hardware configurations in here along with some proof of the failure.

I've been having the same problem doing an initial install (over Win2k) of Ubuntu 7.04 desktop edition from LiveCD. However, I do appear to have found a solution to the problem - for myself anyway.

The PC is an old Dell GX110 machine which comes with a slimline CD-ROM drive but I happen to have a free normal-size DVD-RW drive so I unplugged the CD-ROM drive and connected the DVD-RW drive instead. The LiveCD booted fine this time.

Don't know if that might be useful information for anyone. Could it be an issue with the ATA instruction set being used by the latest kernel?

Richard

OK. Just found this in a random FAQ searching for Busybox and the above error:

> Why do I keep getting "sh: can't access tty; job control turned off" errors? Why doesn't Control-C work
> within my shell?
>
> Job control will be turned off since your shell can not obtain a controlling terminal. This typically happens
> when you run your shell on /dev/console. The kernel will not provide a controlling terminal on the
> /dev/console device. Your should run your shell on a normal tty such as tty1 or ttyS0 and everything will
> work perfectly. If you REALLY want your shell to run on /dev/console, then you can hack your kernel (if
> you are into that sortof thing) by changing drivers/char/tty_io.c to change the lines where it sets
> "noctty = 1;" to instead set it to "0". I recommend you instead run your shell on a real console...

What this suggests to me is that the Busybox error is irrelevant. The bug/problem/whatever is arising before Busybox is invoked and that "bug" then results in Busybox being started. Busybox cannot give a controlling terminal on the /dev/console device so hence the error.

The problem with a clean install, though, is that you can't see the error which causes the Busybox shell to be invoked. You just get the Ubuntu logo and the progress bar.

I'm having the same problem with an MSI-6534 (845M) motherboard. It looks like the ata_piix driver is getting loaded before the ide driver and hooking the CDROM before the IDE driver can get to it. Something similar is described here:

http://www.thinkwiki.org/wiki/Problems_with_SATA_and_Linux#DVD_drive_not_recognized

with potential fixes...I haven't had a chance yet to rebuild the CD to see if this solves the problem.

Wingnut

I found a solution to the problem: I had an old CDROM (Samsung SM-316) I replaced it withe a new
NEC AD 7170 and the installation of kubuntu 7.04 works!

Go to bios and turn ACPI option to disable, that works for me..

I Have an ASUS A7N8X-E

         //Daniel Zippert

I have meet the same problme, following is detail
I use my IBM T43 with ubuntu 7.04 for servral month, and after the reboot this night, i can't login the system.
display 'can't access tty...etc'.

I want to konw the status of this bug, is it closed? and how about the solution?
I have many important data in my computer, so I just want to konw how can I login into my ubunut from BusyBox prompt?

Please send me email if any one konw how to recover my data, my email address is <email address hidden>,,many thanks.

PS: If i want to re-install ubuntu, how to ensure the data not lost?

Hey folks. this bug is a symptom of a problem that is way higher up the
Debian food chain. the fix for this needs to come from the Debian
distro folks.

If 7.04 does not work for you stick with 6.10, it's stable and it
works. I have no idea whether or not this issue will be fixed by 7.10.

Glen Merrick

zhongdai wrote:
> I have meet the same problme, following is detail
> I use my IBM T43 with ubuntu 7.04 for servral month, and after the reboot this night, i can't login the system.
> display 'can't access tty...etc'.
>
> I want to konw the status of this bug, is it closed? and how about the solution?
> I have many important data in my computer, so I just want to konw how can I login into my ubunut from BusyBox prompt?
>
> Please send me email if any one konw how to recover my data, my email
> address is <email address hidden>,,many thanks.
>
> PS: If i want to re-install ubuntu, how to ensure the data not lost?
>
>

Zippert wrote:
> Go to bios and turn ACPI option to disable, that works for me..
>
> I Have an ASUS A7N8X-E
>
> //Daniel Zippert
>
>
That does not work for my TecraS3 laptop.

Relevant system Specs:
Processor: Intel P4
Hards Drives: 2 IDE-40 GBs each(slave and master)
OS: windows XP Pro (originally installed)

Tip:
Made sure that Windows was booting up normally and then booted from the Ubuntu Live CD to get Ubuntu desktop from the CD

Issue:
Got the error message after installing Ubuntu and restarting computer...freezes up at the Ubuntu splash/Progress Bar screen

Resolution:
1] Used Linux System rescue disk to invoke GParted: Edited Partitions
      a) Made the Ubuntu partition( ) a PRIMARY partition-did NOT make it BOOTABLE by the "manage flag" in GParted
          i} The partition was earlier "LOGICAL" which DOES not work
         ii} The BOOTABLE partition right now in GParted window is still set at MS Windows XP Pro
2] Used Ubuntu Live CD to install on to the Hard drive
      a) chose the manual option to partition the Hard Drive
          i} Set the Ubuntu Partition (mount point= /;file system= ext3)
      b) chose to install GRUB in the Ubuntu partition
          i} GRUB installs by default to the C:/ partition used by Windows and imposes itself on the MBR so it shows up on restart before the Windows bootloader
3] Used GParted again to make the Ubuntu partition bootable instead of the Windows XP partion
       a) Both the Ubuntu and Windows XP partions reside on the same Hard Drive ( IDE Master)
4] Restarted the computer
      a) Edited GRUB to select the default Operating system
          i} In my case I chose Windows XP as my default Operating System in GRUB

i am pulling my hair out!!! Why can't ubuntu fix this "can't access tty" bug; the live cd works beautifully on my "Dell Inspiron; too the same CD home to my PC and cant boot. There must be a fix.

Help!

The best "fix" for this is to use Ubuntu 6.10 until an upstream fix is
brought back down to the Ubuntu Development team.

tfria wrote:
> i am pulling my hair out!!! Why can't ubuntu fix this "can't access tty"
> bug; the live cd works beautifully on my "Dell Inspiron; too the same CD
> home to my PC and cant boot. There must be a fix.
>
> Help!
>
>

thanks for the quick response; i will try 6.10

On 7/12/07, gmerrick <email address hidden> wrote:
>
> The best "fix" for this is to use Ubuntu 6.10 until an upstream fix is
> brought back down to the Ubuntu Development team.
>
> tfria wrote:
> > i am pulling my hair out!!! Why can't ubuntu fix this "can't access tty"
> > bug; the live cd works beautifully on my "Dell Inspiron; too the same CD
> > home to my PC and cant boot. There must be a fix.
> >
> > Help!
> >
> >
>
> --
> boot - /bin/sh: can't access tty; job control turned off
> https://bugs.launchpad.net/bugs/96084
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Thomas J. Fria, PhD
Wall, NJ

Yes, it seems this bug is being encountered alot. Google searched forums are coming up with thousands of un-answered problem threads.

I have the same problem. Pretty much a brand new Dell Latitude D830. Not sure of the mobo or some of the other hardware. It is running an Intel Centrino Duo, and it seems that alot of people having boot problems are having this error.

I am having the same error with Ubuntu, and Kubutnu 7.04. I need to try and find an old 6.10 disk, if thats what I need to do to make this work. I love Ubuntu, and wish this would work sometime soon or its back to gates-ware. blech!

Hi!

Where exactly do you have the problem...Is it after installing Ubuntu onto
the Latitude Hard drive.?

Regards
Sanjay

On 7/28/07, Robert C. Mullins <email address hidden> wrote:
>
> Yes, it seems this bug is being encountered alot. Google searched
> forums are coming up with thousands of un-answered problem threads.
>
> I have the same problem. Pretty much a brand new Dell Latitude D830.
> Not sure of the mobo or some of the other hardware. It is running an
> Intel Centrino Duo, and it seems that alot of people having boot
> problems are having this error.
>
> I am having the same error with Ubuntu, and Kubutnu 7.04. I need to try
> and find an old 6.10 disk, if thats what I need to do to make this work.
> I love Ubuntu, and wish this would work sometime soon or its back to
> gates-ware. blech!
>
> --
> boot - /bin/sh: can't access tty; job control turned off
> https://bugs.launchpad.net/bugs/96084
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Hi!

Where exactly do you have the problem...Is it after installing Ubuntu onto
the Inspiron Hard drive.?
If yes make sure that the Ubuntu partition is "PRIMARY" NOT logical or it
will get stuck while booting with the ERROR in the post
Rule for GRUB....Install it on the Ubuntu partition...if U got a Windows OS
as well installed....make the Windows Bootloader in the Windows partition to
give you the Linux boot option when the computer first boots up...that way U
can get to GRUB boot options and then get Ubuntu to boot up from your
computer's Hard Drive...Good Luck!

Regards
Sangos

On 7/12/07, tfria <email address hidden> wrote:
>
> i am pulling my hair out!!! Why can't ubuntu fix this "can't access tty"
> bug; the live cd works beautifully on my "Dell Inspiron; too the same CD
> home to my PC and cant boot. There must be a fix.
>
> Help!
>
> --
> boot - /bin/sh: can't access tty; job control turned off
> https://bugs.launchpad.net/bugs/96084
> You received this bug notification because you are a direct subscriber
> of the bug.
>

The error occurs on the Tecra S3 Laptop right after the first reboot,
when Unbuntu 7.04 Live CD has completed the install and tells you to
remove the disk and reboot. The system will come up on its own and then
hangs at that point.

sangos wrote:
> Hi!
>
>
> Where exactly do you have the problem...Is it after installing Ubuntu onto
> the Inspiron Hard drive.?
> If yes make sure that the Ubuntu partition is "PRIMARY" NOT logical or it
> will get stuck while booting with the ERROR in the post
> Rule for GRUB....Install it on the Ubuntu partition...if U got a Windows OS
> as well installed....make the Windows Bootloader in the Windows partition to
> give you the Linux boot option when the computer first boots up...that way U
> can get to GRUB boot options and then get Ubuntu to boot up from your
> computer's Hard Drive...Good Luck!
>
> Regards
> Sangos
>
> On 7/12/07, tfria <email address hidden> wrote:
>
>> i am pulling my hair out!!! Why can't ubuntu fix this "can't access tty"
>> bug; the live cd works beautifully on my "Dell Inspiron; too the same CD
>> home to my PC and cant boot. There must be a fix.
>>
>> Help!
>>
>> --
>> boot - /bin/sh: can't access tty; job control turned off
>> https://bugs.launchpad.net/bugs/96084
>> You received this bug notification because you are a direct subscriber
>> of the bug.
>>
>>
>
>

I can't even get the live disk to boot. I put the disk in, go to the bios set it up to boot from cd/dvd rom drive. Ubuntu starts booting, I get to the splash screen/progress bar where the orange bar glides back and forth, then dumps me into that weird prompt.

U might try the DVD version of Ubuntu which has a larger repertory of software burnt in and possibly additional drivers. It is possible that the CD(if that’s what ur using) may not come with the native drivers to run ur hardware. The DVD also gives additional options to get Ubuntu installed on your computer....Good luck!
PS Of course make sure U have A DVD drive to boot the DVD disk.

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of Robert C. Mullins
Sent: Sunday, July 29, 2007 12:59 AM
To: <email address hidden>
Subject: [Bug 96084] Re: boot - /bin/sh: can't access tty; job control turned off

I can't even get the live disk to boot. I put the disk in, go to the
bios set it up to boot from cd/dvd rom drive. Ubuntu starts booting, I
get to the splash screen/progress bar where the orange bar glides back
and forth, then dumps me into that weird prompt.

--
boot - /bin/sh: can't access tty; job control turned off
https://bugs.launchpad.net/bugs/96084
You received this bug notification because you are a direct subscriber
of the bug.

I had the same problem and I fixed it by using the Linux rescue disk and use GParted tool in it to make the Ubuntu Partition Primary (And therefore bootable; Logical partitions ARE NOT bootable if that’s where Ubuntu is sitting!?). Some of the guides misguide on this(don’t remember which!) GRUB also needs to be installed on a Primary Partition( or it will screw up the Ubuntu boot up from the Hard drive).

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of gmerrick
Sent: Sunday, July 29, 2007 12:40 AM
To: <email address hidden>
Subject: Re: [Bug 96084] Re: boot - /bin/sh: can't access tty; job control turned off

The error occurs on the Tecra S3 Laptop right after the first reboot,
when Unbuntu 7.04 Live CD has completed the install and tells you to
remove the disk and reboot. The system will come up on its own and then
hangs at that point.

sangos wrote:
> Hi!
>
>
> Where exactly do you have the problem...Is it after installing Ubuntu onto
> the Inspiron Hard drive.?
> If yes make sure that the Ubuntu partition is "PRIMARY" NOT logical or it
> will get stuck while booting with the ERROR in the post
> Rule for GRUB....Install it on the Ubuntu partition...if U got a Windows OS
> as well installed....make the Windows Bootloader in the Windows partition to
> give you the Linux boot option when the computer first boots up...that way U
> can get to GRUB boot options and then get Ubuntu to boot up from your
> computer's Hard Drive...Good Luck!
>
> Regards
> Sangos
>
> On 7/12/07, tfria <email address hidden> wrote:
>
>> i am pulling my hair out!!! Why can't ubuntu fix this "can't access tty"
>> bug; the live cd works beautifully on my "Dell Inspiron; too the same CD
>> home to my PC and cant boot. There must be a fix.
>>
>> Help!
>>
>> --
>> boot - /bin/sh: can't access tty; job control turned off
>> https://bugs.launchpad.net/bugs/96084
>> You received this bug notification because you are a direct subscriber
>> of the bug.
>>
>>
>
>

--
boot - /bin/sh: can't access tty; job control turned off
https://bugs.launchpad.net/bugs/96084
You received this bug notification because you are a direct subscriber
of the bug.

Naw....Too much effort to get an OS running.
I am happy with 6.10. It installs effortlessly and it does what I need
it to do. This just underlines the issues that Ubuntu and Debian need
to take to fix the problem. I shouldn't have to "hack" the system in
order for a basic install to function. Besides, when I tried installing
7.04 it was onto a primary partition and the issue kept happening.

Glen Merrick

sangos wrote:
> I had the same problem and I fixed it by using the Linux rescue disk and
> use GParted tool in it to make the Ubuntu Partition Primary (And
> therefore bootable; Logical partitions ARE NOT bootable if that’s where
> Ubuntu is sitting!?). Some of the guides misguide on this(don’t remember
> which!) GRUB also needs to be installed on a Primary Partition( or it
> will screw up the Ubuntu boot up from the Hard drive).
>
> -----Original Message-----
> From: <email address hidden> [mailto:<email address hidden>] On Behalf Of gmerrick
> Sent: Sunday, July 29, 2007 12:40 AM
> To: <email address hidden>
> Subject: Re: [Bug 96084] Re: boot - /bin/sh: can't access tty; job control turned off
>
> The error occurs on the Tecra S3 Laptop right after the first reboot,
> when Unbuntu 7.04 Live CD has completed the install and tells you to
> remove the disk and reboot. The system will come up on its own and then
> hangs at that point.
>
> sangos wrote:
>
>> Hi!
>>
>>
>> Where exactly do you have the problem...Is it after installing Ubuntu onto
>> the Inspiron Hard drive.?
>> If yes make sure that the Ubuntu partition is "PRIMARY" NOT logical or it
>> will get stuck while booting with the ERROR in the post
>> Rule for GRUB....Install it on the Ubuntu partition...if U got a Windows OS
>> as well installed....make the Windows Bootloader in the Windows partition to
>> give you the Linux boot option when the computer first boots up...that way U
>> can get to GRUB boot options and then get Ubuntu to boot up from your
>> computer's Hard Drive...Good Luck!
>>
>> Regards
>> Sangos
>>
>> On 7/12/07, tfria <email address hidden> wrote:
>>
>>
>>> i am pulling my hair out!!! Why can't ubuntu fix this "can't access tty"
>>> bug; the live cd works beautifully on my "Dell Inspiron; too the same CD
>>> home to my PC and cant boot. There must be a fix.
>>>
>>> Help!
>>>
>>> --
>>> boot - /bin/sh: can't access tty; job control turned off
>>> https://bugs.launchpad.net/bugs/96084
>>> You received this bug notification because you are a direct subscriber
>>> of the bug.
>>>
>>>
>>>
>>
>
>

Use F6 to enter "Other Options" and add "all_generic_ide" at the end of the line.

I was getting this problem. I changed my bios settings for my SATA disk to Compatabilty Mode and Ubuntu then booted without any problems.

Further hereto, (to recap):

1. I do have 3 "older p-ata" systems, completely "incompatible", (and "unworkable") with all versions of (k)ubuntu 7.04, including Linux Mint "Cassandra", based on (k)ubuntu 7.04
2. Lindows/Linspire/Freespire has come out with "Freespire 2.0.0.0", also completely based on (k)ubuntu 7.04
3. This "Freespire 2.0.0.0 Live CD" takes a long time to "load"
4. However, it resolves "all issues" with my "older p-ata" systems

I do have an "inimical attitude" towards Lindows/Linspire/Freespire for being one of the distros "having gone to bed with M$"......... Notwithstanding "that", I must give them full credit for having resolved the "p-ata" problem..... More power to them..... The "power" (k)ubuntu 7.04 never had, or showed!!

ive had this error message,
i googled,
it suggested its because i have an AMD chip
and the standard ubuntu cd works on Intel chips
so i'm downloading a AMD version from:

http://www.ubuntu.com/

Download URL: http://releases.ubuntu.com/feisty/ubuntu-7.04-desktop-amd64.iso
Ubuntu Edition: Ubuntu 7.04 desktop
Computer Platform: amd64
Download Location: http://releases.ubuntu.com/

[[dicegeorge]]

My girlfriends little sister needed a laptop for internet office and some other small things. I've been watching Ubuntu for some time and i downloaded it an hour ago.
I came across this problem as well.

I have a P3-800 old laptop that has been doing service for some time.

I found my solution when i added the option (via F6 in bootup menu) all_generic_ide;
this resulted in an error and the message "try the option irqpoll"

Instead of adding "all_generic_ide" i added "irqpoll" and the little creature started living suddenly...

hoping this will help others.

Regarding /bin/sh: Can’t access tty; job control turned off

Apparently, there are a bizillion reasons that this error occurs, but in my case, it was because the Ubuntu Live CD couldn't recognize some of the hardware on the machine I was installing to. (I was able to install it successfully on other machines--it was just one troublesome machine).

Here is what worked for me:

   1. When the bootup screen appears, press F6
   2. Type the following: acpi=off irqpoll
   3. Press the Enter key.
   4. View the Live CD and install Ubuntu.

You have to make sure that this problem is resolved when Ubuntu boots, too. To do that:

   1. Boot your computer so that GRUB is displayed.
   2. Press the "e" key to go into edit mode.
   3. Press "o" to add a new line to the script.
   4. Type the following: acpi=off irqpoll
   5. Press the Escape key.

In the event that acpi=off doesn't work try replacing the entry above with one of the following:

    * acpi=force irqpoll
    * nacpitimer irqpoll

You may have to revisit the second set of steps when you upgrade ubuntu.

I hope this helps.

I had the same problem installing Ubuntu 7.10.

Adding irqpoll to the startup in GRUB as recommended above does allow me to proceed to install and use Ubuntu 7.10

Adding irqpoll to the Live CD boot options also worked for me. After the install, I had to add it to the grub options as well.

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Thank you for the follow up information, however, you may remove my address
from the bug subscriber list. I have installed Ubuntu 8.04 and am able to
boot from Ubuntu or Windows at my option. The system has worked worked
flawlessly for several months.
Thanks again.

Larry Wolfe

----- Original Message -----
From: "Leann Ogasawara" <email address hidden>
To: <email address hidden>
Sent: Thursday, August 28, 2008 20:50
Subject: [Bug 96084] Re: boot - /bin/sh: can't access tty; job control
turned off

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the
upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would
appreciate it if you could please test this newer 2.6.27 Ubuntu kernel.
There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-
image-2.6.27-* package is currently available for you to install and
test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer
2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4.
Please watch http://www.ubuntu.com/testing for Alpha5 to be announced.
You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the
bug reported here or if the issue remains. More importantly, please
open a new bug report for each new bug/regression introduced by the
2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please
specifically note if the issue does or does not appear in the 2.6.26
kernel. Thanks again, we really appreicate your help and feedback.

** Tags added: cft-2.6.27

--
boot - /bin/sh: can't access tty; job control turned off
https://bugs.launchpad.net/bugs/96084
You received this bug notification because you are a direct subscriber
of the bug.

---
avast! Antivirus: Outbound message clean.
Virus Database (VPS): 080828-0, 08/28/2008
Tested on: 8/29/2008 7:50:47 AM
avast! - copyright (c) 1988-2008 ALWIL Software.
http://www.avast.com

This bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status . Thank you again for taking the time to report this bug and helping to make Ubuntu better. Feel free to submit any future bugs you may find.

LinkedIn
------------

Bug,

I'd like to add you to my professional network on LinkedIn.

- Tom

Tom Fria
Clinical Audiologist at Department of Veterans Affairs
Greater New York City Area

Confirm that you know Tom Fria:
https://www.linkedin.com/e/-4rawsv-hnx94qf3-j/isd/17989283458/5IfIT8D5/?hs=false&tok=2BlHcU02Ol2m01

--
You are receiving Invitation to Connect emails. Click to unsubscribe:
http://www.linkedin.com/e/-4rawsv-hnx94qf3-j/XjVg-eC45zKbR9uMZsau8R2_Rb04UJr23GnVDE/goo/96084%40bugs%2Elaunchpad%2Enet/20061/I5918931975_1/?hs=false&tok=2_au__vJKl2m01

(c) 2012 LinkedIn Corporation. 2029 Stierlin Ct, Mountain View, CA 94043, USA.