How to partition hard drive in Ubuntu 20.04

I’m literally brand-new to Linux and Ubuntu, so please forgive my ignorance and bear with me here. I purchased a Dell Inspiron 5593 recently and immediately installed Ubuntu 20.04 on it. Long story short, the keyboard is screwed up, and the place I bought it from won’t service Linux OS. Gotta be Windows/Mac OSX for some stupid reason.

So now I’m trying to partition the hard drive and reinstall Windows on the the partition. I’ve checked out GParted, but I haven’t been able to follow the documentation. For example, I don’t see any unallocated space on my disk, and I’m not willing to unmount my main disk without knowing what that will do to my computer.

Honestly at this point I’m ripping my hair out and would just appreciate some clear instructions on how to partition a hard drive in Ubuntu 20.04 because I’m clearly too technically illiterate to understand GParted’s documentation.

Go to Source
Author: Yehuda

Corrupted ext4 disk with windows disk manager

I am the main linux person in our team (which is a sad state of affairs), and am trying to fix a problem created by one of our windows users.

They had a 5TB drive with a single ~5TB ext4 partition with a bunch of video files. They weren’t the one who set up the drive, so when they couldn’t access it in windows they went into disk manager and ” converted to GPT” in windows disk manager. Now it isn’t accessible in ubuntu either.

Disk: Seagate ST5000DM

fdisk reports: the wrong disk size

Disk /dev/sdg: 561.5 GiB, 602934566912 bytes, 1177606576 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xa6985519

Testdisk reports the wrong disk size: >Disk /dev/sdg – 602 GB / 561 GiB – ST5000DM 000-1FK178

fsck reports:

fsck from util-linux 2.31.1
e2fsck 1.44.1 (24-Mar-2018)
ext2fs_open2: Bad magic number in super-block
fsck.ext2: Superblock invalid, trying backup blocks…
fsck.ext2: Bad magic number in super-block while trying to open /dev/sdg

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
or
e2fsck -b 32768

Found a PMBR partition table in /dev/sdg

Gdisk reports:
Caution: The CRC for the backup partition table is invalid. This table may
be corrupt. This program will automatically create a new backup partition
table when you save your partitions.

Problem: The secondary header’s self-pointer indicates that it doesn’t reside
at the end of the disk. If you’ve added a disk to a RAID array, use the ‘e’
option on the experts’ menu to adjust the secondary header’s and partition
table’s locations.

Problem: Disk is too small to hold all the data!
(Disk size is 1177606576 sectors, needs to be 9767541168 sectors.)
The ‘e’ option on the experts’ menu may fix this problem.

Problem: GPT claims the disk is larger than it is! (Claimed last usable
sector is 9767541134, but backup header is at
9767541167 and disk size is 1177606576 sectors.
The ‘e’ option on the experts’ menu will probably fix this problem

Problem: partition 1 is too big for the disk.

Partition(s) in the protective MBR are too big for the disk! Creating a
fresh protective or hybrid MBR is recommended.

Identified 6 problems!

File recovery programs can still read the files, so I can fall back on that if I have to, but it will take forever and lead to endless sorting and renaming of files. I am hoping I can ” fix” the partition table to be able to mount the drive and immediately back up the data onto a secure, backed up location.

Thanks for any assistance. Any guidance on what to try is appreciated. I haven’t had to deal with this kind of thing before, my linux usage is pretty vanilla.

Go to Source
Author: Chris Hall

Displaying Full Storage Capacity after removing Wndows 10 after a dual boot

I’m not able to access the available storage list. It only shows a partial section of the memory leaving out the former memory which had Windows 10 installed in it. I’m sending a screenshot just for clarification.
MY hard-disk contains 500GiB but it says only 135GiB left
Kindly help pls.the image shows the partitions and the notification about only showing 135GiB leaving out the rest of the memory

Go to Source
Author: Kelvin

Ubuntu 20.04 Does Not Boot

ANSWER

Looks like this one just needs to have their GRUB re-written to MBR again. It’s not so hard. But given that I did something like this 8 years ago… The concept should still be the same. Steps of what I did to fix it here.

I originally had Ubuntu 18.04 installed on my dell xps 13 (2017). A couple days ago, I replaced it with Ubuntu 20.04 due to constant error messages. Until today, I was able to use it without any trouble.
However, I had to use Windows earlier today, and now when I was trying to boot Ubuntu back, I am unable to do so.

First error message

Unexpected return from initial read: Volume Corrupt buffersize 1000 Failed to load image EFIubuntugrubefi: Volume Corrupt start_image() returned Volume Corrupt

and then windows booted automatically.

In trying to resolve the issue,

  1. Tried reinstalling Ubuntu 20.04 using LiveUSB, but got the error saying the system doesn’t have EFI System Partition
  2. Consulted the forum https://ubuntu.forumming.com/question/5394/unexpected-return-from-initial-read-volume-corrupt.
    In running Boot Repair, I received an error message, sayin EFI System Partition is needed.
  3. Used GPart to try to tweak disk settings (changing the disk partition that holds Ubuntu File System from ext4 to fat32… I didn’t document this process very well)
  4. Followed a tutorial that used Windows command prompt and diskpart, creating an ESP.
  5. Reran Boot Repair (successfully this time)

However, now I encountered a GRUB error

“Minimal BASH like line editing is supported. For the first word, TAB lists possible command completions. anywhere else TAB lists possible device or file completions.”

I’ve been looking up different solutions, but I am having trouble understanding them, and afraid I am messing my disk more and more.

Thank you in advance.

Go to Source
Author: Amanda Jeong