Ubuntu

ubuntu 16.04 boot partition formatted accidentally and OS wont boot, how to recover the OS?

Asked by Atif Baig

Hi,

Im a new Systems admin and have limited knowledge and experience with linux, we are using VMware VCenter to manage a VMs, one of which has a ubuntu server 16.04.2 LTS amd64, the user of that server formatted the boot manager disk accidentally, im trying to recover the server by using the ubuntu server iso file, i am able to use the recovery method to get to the shell, how do i mount the right file system or recover the system from shell? any help with steps/commands would be appreciated.

Thanks

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Solved by:
Atif Baig
Solved:
Last query:
Last reply:
Revision history for this message
Atif Baig (cunyit17) said : 		#1

I was actually able to get to the Ubuntu installer main menu, where there are plenty of option to pick from:
choose language
access software for a blind person using a braulle display
configure keyboard
.
.
.
enter resume mode
partition disks
intsall the system
.
.
continue with boot loader

which option can recover the system?

Thanks

Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#2

Use nautilus and you can mount file systems. You can see all available file systems by running:

sudo parted -l

Why don't you just resetup the host and restore your data from your backups. Much easier. You have backups right?

Revision history for this message
Atif Baig (cunyit17) said : 		#3

unfortunately we dont have backups, but i was able to use to ubuntu server iso file to rescue the system after figuring out which partition has the server files and mounting it to the boot loader. problem solved.

Revision history for this message
Atif Baig (cunyit17) said : 		#4

unfortunately we dont have backups, but i was able to use to ubuntu server iso file to rescue the system after figuring out which partition has the server files and mounting it to the boot loader. problem solved.