Skip to content

Commit

Permalink
^
Browse files Browse the repository at this point in the history
  • Loading branch information
sohanglal committed Feb 13, 2024
1 parent aa259c6 commit 7207083
Show file tree
Hide file tree
Showing 4 changed files with 28 additions and 27 deletions.
4 changes: 2 additions & 2 deletions index.xml
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@
<title>kde partition manager fiasco</title>
<link>https://sohanglal.github.io/kde-partition-manager-fiasco</link>
<guid>https://sohanglal.github.io/kde-partition-manager-fiasco</guid>
<description> wanted shrink Kubuntu to make space for NixOS Maybe drive was mounted but still alot of the same issues were observed when searching online ultimate search term kde partition manager shrink size in superblock and physical size differ filesystems - “Either the superblock or the partition table is likely to be corrupt!” after partition resized - Unix &amp; Linux Stack Exchange According to this answer ran e2fsck, a destructive operation just because I was afraid of the command line and didn’t want to use parted long process resize2fs would’ve deleted rest of the partitions went off sleep seeked a better solution filesystems - “Either the superblock or the partition table is likely to be corrupt!” after partition resized - Unix &amp; Linux Stack Exchange found this using growpart to fill the unallocated space, atleast won’t have to delete nixos and windows reserved partitions partition - How to recover filesystem and physical size mismatch - Unix &amp; Linux Stack Exchange then came across this solution to use parted basically partition table via parted got updated but resize2fs failed to resize the filesystem simple solution is to update the partition table to the original standard used sudo fdisk -l to read start and end sectors entered parted /dev/nvme0n1 resizepart 4 859174911s gave sector number for perfect granuality Parted - ArchWiki had to e2fsck again this reversed all the destructive changes that I made the day before Kubuntu still wouldn’t boot for some reason the files in /boot vanished backup was there on desktop copied those files from Desktop to /boot started working again even though the boot partition is mounted on /boot/efi, kubuntu had installed the files in /boot which is p4 and /boot/efi is on p1 To boot into kubuntu using the backup files, used this guide: Classic SysAdmin: How to Rescue a Non-booting GRUB 2 on Linux - Linux Foundation grub&gt; set root=(hd0,1) grub&gt; linux /boot/vmlinuz-3.</description>
<description> wanted to shrink Kubuntu to make space for NixOS Maybe the drive was mounted but still alot of the same issues were observed when searching online regarding kde partition manager ultimate search term kde partition manager shrink size in superblock and physical size differ filesystems - “Either the superblock or the partition table is likely to be corrupt!” after partition resized - Unix &amp; Linux Stack Exchange According to this answer ran e2fsck, a destructive operation just because I was afraid of the command line and didn’t want to use parted long process resize2fs would’ve deleted rest of the partitions slept seeked a better solution filesystems - “Either the superblock or the partition table is likely to be corrupt!” after partition resized - Unix &amp; Linux Stack Exchange found this using growpart to fill the unallocated space, atleast won’t have to delete nixos and windows reserved partitions partition - How to recover filesystem and physical size mismatch - Unix &amp; Linux Stack Exchange then came across this solution to use parted basically partition table via parted got updated but resize2fs failed to resize the filesystem simple solution is to update the partition table to the original standard used sudo fdisk -l to read start and end sectors entered parted /dev/nvme0n1 resizepart 4 859174911s gave sector number for perfect granuality Parted - ArchWiki had to e2fsck again this reversed all the destructive changes that I made the day before Kubuntu still wouldn’t boot for some reason the files in /boot vanished backup was there on desktop copied those files from Desktop to /boot started working again even though the boot partition is mounted on /boot/efi, kubuntu had installed the files in /boot which is p4 and /boot/efi is on p1 To boot into kubuntu using the backup files, used this guide: Classic SysAdmin: How to Rescue a Non-booting GRUB 2 on Linux - Linux Foundation grub&gt; set root=(hd0,1) grub&gt; linux /boot/vmlinuz-3.</description>
<pubDate>Fri, 12 Jan 2024 19:38:56 GMT</pubDate>
</item><item>
<title>resizing boot partition</title>
Expand All @@ -39,7 +39,7 @@
<title>setup github ssh</title>
<link>https://sohanglal.github.io/setup-github-ssh</link>
<guid>https://sohanglal.github.io/setup-github-ssh</guid>
<description> generate key ssh-keygen -t ed25519 -C [email protected] cat ~/.ssh/id_ed25519.pub copy key to github cat ~/.ssh/id_ed25519.pub | xclip -sel c https://github.</description>
<description> generate key ssh-keygen -t ed25519 -C &quot;[email protected]&quot; cat ~/.ssh/id_ed25519.pub cat ~/.ssh/id_ed25519.pub | xclip -sel c copy key to github - https://github.</description>
<pubDate>Sat, 11 Nov 2023 06:11:52 GMT</pubDate>
</item><item>
<title>Calisthenics + HIIT</title>
Expand Down
Loading

0 comments on commit 7207083

Please sign in to comment.