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

Bug #95709 reported by Giuseppe Iuculano
6
Affects Status Importance Assigned to Milestone
initramfs-tools (Ubuntu)
Fix Released
Undecided
Unassigned
Nominated for Feisty by Giuseppe Iuculano
linux-source-2.6.20 (Ubuntu)
Fix Released
Undecided
Unassigned
Nominated for Feisty by Giuseppe Iuculano

Bug Description

Binary package hint: initramfs-tools

My /boot is a software raid1 partition, and after upgrading to feisty I have this error:

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

A workaround is break=mount in grub options, and type exit at busybox prompt, or install and using yaird.

description: updated
Revision history for this message
ico (ico-bukvic) wrote :

Second that. I tried the same thing with software raid with the same result. Non-raid install works just fine.

Haven't tried the workaround, however.

Revision history for this message
Thomas Hotz (thotz-deactivatedaccount) wrote :

Could you please retest with a daily build available from http://cdimage.ubuntu.com/ ? Thanks in advance!

Changed in initramfs-tools:
assignee: nobody → thotz
status: Unconfirmed → Needs Info
Revision history for this message
ico (ico-bukvic) wrote : RE: [Bug 95709] Re: [feisty] /bin/sh:can't access tty;job control turned off

> Could you please retest with a daily build available from
> http://cdimage.ubuntu.com/ ? Thanks in advance!
>
> ** Changed in: initramfs-tools (Ubuntu)
> Assignee: (unassigned) => Thomas Hotz
> Status: Unconfirmed => Needs Info
>
> ** Changed in: initramfs-tools (Ubuntu)
> Sourcepackagename: initramfs-tools => linux-source-2.6.20
>
> --
> [feisty] /bin/sh:can't access tty; job control turned off
> https://launchpad.net/bugs/95709

I just retested it from scratch and no, still the same problem.

Best wishes,

Ico

Revision history for this message
ico (ico-bukvic) wrote :

I tried booting without quiet and splash and the info I got upon the second
boot was as follows:

(btw, I have 3 partitions md0 100GB /, md1 4GB swap, md2 191GB /home on an
A8N32-SLI AMD64 motherboard)

md0 was reported as "not clean -- starting background reconstruction"
after that md1 was stopped
...
Begin: Running /scripts/local-premount
kinit: name_to_dev_t(/dev/md1) = md1(9,1)
kinit: trying to resume from /dev/md1
Attempting manual resume
Read-error on swap-device (9:1:8)
kinit: No reusme image, doing normal boot...
Done.
mount: Mounting /dev/md0 on /root failed: Device or resource busy
...
Running /scripts/local-bottom
mount: Mounting /root/dev on /defv/.static/dev failed: No such file or
directory
Done.
mount: Mounting /sys on /root/sys failed: No such file or directory
mount: Mounting /proc on /root/proc failed: No such file or directory
Target filesystem doesn't have sbin/init

And then comes the BusyBox stuff.

Ico

Revision history for this message
ico (ico-bukvic) wrote :

Just to also confirm that adding break=mount in grub and then typing "exit"
in the busybox prompt as reported by original poster does allow computer to
boot.

Ico

Changed in linux-source-2.6.20:
assignee: thotz → ubuntu-kernel-team
status: Needs Info → Confirmed
Revision history for this message
ico (ico-bukvic) wrote :

Another thing to add in hope this may help. When using the aforesaid fix
(break=mount... exit) md drives go out of sync requiring resyncing.

Ico

Revision history for this message
Giuseppe Iuculano (giuseppe-iuculano) wrote :

I think that fixing this bug should have high priority because makes system unbootable

Revision history for this message
ico (ico-bukvic) wrote :

I agree. This has to be a high prioirity item especially since launchpad has at least another half-dozen bugs of similar nature reported with same symptoms. This is a show-stopper folks...

Revision history for this message
Giuseppe Iuculano (giuseppe-iuculano) wrote :

initramfs-tools (0.85eubuntu10) fix this issue

Changed in linux-source-2.6.20:
status: Confirmed → Fix Released
Changed in linux-source-2.6.20:
status: Unconfirmed → Fix Released
Revision history for this message
deuce (azinas) wrote :

how can you get that and install it on a non-working system?

Revision history for this message
Fredrik (fredrk) wrote :

initramfs-tools (0.85eubuntu10) does NOT fix this issue.

I still have it. But not every boot, just every 10% maybe and a reboot solves the problem.

Revision history for this message
Fredrik (fredrk) wrote :

Still open this up again as the issue isn't solved.

Revision history for this message
Christian Brandt (brandtc) wrote :

I have the same problem with an updated 7.04. But for me half of the boot attempts hangs with "Mounting /dev/md0 on /root failed: Device or resource busy. Manually mounting root from busybox shortly after is possible though.

I have the odd feeling that this is a timing problem, the system is trying to mount the root device too fast. Think I'll try yaird or play with the timing inside mkinitfs.

Revision history for this message
Launchpad Janitor (janitor) wrote : Kernel team bugs

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.