[Bug 214795] Re: fsck recovery shell has no prompt and stderr

[Thomas Hotz]

Is this still an issue for you? Which Ubuntu version do you use? Thank
you for telling us!

** Changed in: sysvinit (Ubuntu)
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to sysvinit in Ubuntu.
https://bugs.launchpad.net/bugs/214795

Title:
  fsck recovery shell has no prompt and stderr

Status in “sysvinit” package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: upstart

  The fsck in rcS.d/30checkfs.sh failed in my case because I had a bogus
  entry in /etc/fstab, actually had a /dev/hda5 instead of /dev/sda5 -
  disk name of the month.

  It opened a rescue shell for me, but without prompt so I didn't
  understand I had got a shell the first times. Moreover, stderr was
  redirected away, so I didn't get any error messages and such. ls -l
  /proc/self/fd showed that 2 was linked to a process that didn't exist
  anylonger. Got it back with exec 2>&1

  I don't when this bug was introduced, I saw it only now because the
  disk driver had changed so I got the above failure. Running up to date
  Hardy, initially installed at alpha 4.

  Steps to reproduce:
  Add something like "/dev/notexist /mnt ext3 defaults 0 0" to your /etc/fstab and reboot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/214795/+subscriptions