9

I'll tell you the whole story.

I decided to upgrade my natty from alpha to beta after a long time.After the updates has been downloaded, the system crashed during installation. I rebooted the system and during the plymouth screen I greeted with the error message

"Disk Drive / not ready yet or not available"

and options to wait,skip or manually recover

If I choose to skip, it gives the same error,but with /tmp this time.

And if I skip again, it just freezes.

If I choose the option to manually recover, I get a maintenance shell.

Please help.

Jorge Castro
  • 70,934
  • 124
  • 466
  • 653
Mad-scientist
  • 499
  • 1
  • 4
  • 16
  • Thing I have already tried Waiting running fsck fsck -a, -p,-f mount -a running gparted on this drive from a different ubuntu partition – Mad-scientist Apr 14 '11 at 06:10
  • After a system crash during updgrade your files or filesystem may be corrupted. This can best be fixed with a fresh reinstall. – Takkat Apr 14 '11 at 07:48
  • I dont want to do it.Thats the whole point. – Mad-scientist Apr 14 '11 at 08:02
  • I had the same error with a fresh install to 12.04. Worked out the same fix mentioned in Klaus' post. – ijk Aug 12 '12 at 16:43
  • 1
    **NOTE:** [This question](http://askubuntu.com/q/38617/62483) is about the same issue. Hopefully, it can be useful for future users.. – Lucio Feb 06 '13 at 22:47
  • possible duplicate of [Ubuntu 14.04 not booting after error message. /tmp could not be mounted](http://askubuntu.com/questions/453411/ubuntu-14-04-not-booting-after-error-message-tmp-could-not-be-mounted) – bain Sep 18 '14 at 09:32
  • or [Disk drive boot problem: The disk drive for /tmp is not ready yet or is not present!](http://askubuntu.com/questions/454037/disk-drive-boot-problem-the-disk-drive-for-tmp-is-not-ready-yet-or-is-not-pres) – bain Sep 21 '14 at 10:17

2 Answers2

4

This code works fine on my machine (try it just once and the problem should be fixed):

mount -o remount, rw /

My Ubuntu is: Ubuntu 12.04: 3.2.0-49-generic #75-Ubuntu x86_64 GNU/Linux

Eric Carvalho
  • 53,609
  • 102
  • 137
  • 162
user1512848
  • 141
  • 2
0

I ran fsck in manual recovery. But I don't remember which atribute label I used - it was check partition and don't repair. I think it vas -r. Then console aked me if I wanted to fix this erorr. I pushed "y" for one hundred times and now system boot without problem.

Kris Harper
  • 13,397
  • 12
  • 56
  • 73
kunna
  • 11