Question

2

Boot mounts failing after power outage

rated 0 times [ 2] [ 0] / answers: 1 / hits: 6838 / 3 Years ago, mon, august 2, 2021, 6:33:26

UPDATE 1

Output of sudo fdisk -l

ubuntu@ubuntu:~$ sudo fdisk -l



Disk /dev/sda: 120.0 GB, 120034123776 bytes

255 heads, 63 sectors/track, 14593 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk identifier: 0x00050e46



   Device Boot      Start         End      Blocks   Id  System

/dev/sda1   *           1        9729    78140139    7  HPFS/NTFS

/dev/sda2            9729       14594    39079937    5  Extended

/dev/sda5            9729       14388    37430272   83  Linux

/dev/sda6           14389       14594     1648640   82  Linux swap / Solaris

ubuntu@ubuntu:~$

ORIGINAL QUESTION

I'm getting the following message when I try to boot up my Ubuntu 10.04 install:

mount: mounting /dev on /root/dev failed: No such file or directory

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.

No init found.  Try passing init= bootarg

This happened after a power failure.

I am currently using the same computer but booted from the Ubuntu 10.04 LiveCD.

How do I recover my system?

Answers

Only authorized users can answer the question. Please sign in first, or register a free account.

breadoules

Add To Favorites

Follow

Total Points: 212

Total Questions: 118

Total Answers: 120

Location: Dominica

Member since Mon, Jun 22, 2020

4 Years ago

answered 3 Years ago oatglori · Accepted Answer

Seeing your fstab I think you have windows in your sda1, im I wrong? The problem is sometimes after a power outage the ntfs gets damaged. If your boot sda1 device were Linux and the ntfs were in sda2, fdsk would repair it automatically during boot. But since the boot is in the same damaged device, it can't.

If you have windows, try booting into windows, reach the desktop, and restart it properly. Next time you boot the sda1 would be corrected and linux should boot normally.