2

I have got myself stuck in a serious situation. There was problem booting my ubuntu after a hard shut-down. I used a live CD to run ubuntu. I installed boot-repair in it and ran it. To my surprise it not only removed my ubuntu but also my windows. Now I am not able to install ubuntu again because of this error. The report generated by boot-repair is in the provided link. Please help

http://paste.ubuntu.com/p/pvGwHrwDb4/ Here are the screenshots of the smart data window from disks utility of my ubuntu partition. Screenshot of ubuntu partition First screen enter image description here

  • Boot to a Ubuntu Live DVD/USB, start the Disks app, and get screenshot(s) of the SMART Data window. – heynnema Jan 2 at 19:41
  • @heynnema added screenshots – Harshit Khetan Jan 3 at 4:54
  • Thanks for the screenshots. Is this a laptop or desktop computer? Other than possibly a loose cable, your disk looks like it is toast. You could try installing a new GPT partition table (this will wipe the drive) and see if you could reinstall OSs, but I don't hold out a lot of hope. – heynnema Jan 3 at 14:37
  • This is Hp Pavilion notebook so a laptop. – Harshit Khetan Jan 3 at 16:47
  • All partitions show up as unknown type. If nothing else, your GPT partition table is toasted. You could try a gparted repair, or a testdisk repair... and maybe you can backup any important stuff... – heynnema Jan 3 at 17:43
1

Have you tried running fsck? It's a utility that checks consistencies in a file system and makes repairs. To run it you'll have to make sure the drive isn't mounted to avoid altering disk data and causing runtime errors. Boot from live DVD/USB and run fsck /dev/sda3 on the drive from your terminal.

  • Running fsck gives fsck.ext2: Input/output error while trying to open /dev/sda3 The superblock could not be read or does not describe a valid ext2/ext3/ext4 filesystem. If the device is valid and it really contains an ext2/ext3/ext4 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> or e2fsck -b 32768 <device> – Harshit Khetan Jan 3 at 9:23

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.