Recent content by BigBullShinner

  1. BigBullShinner

    Block Device Issue/ resizing: SOLVED

    Awesome advice! the resize worked perfectly without messing anything up. Needless to say it was time to also do a reinstall by the time I got around to testing it out, but I'm glad I know how to do that and that it can work. Greatly appreciate the responses from everybody.
  2. BigBullShinner

    Block Device Issue/ resizing: SOLVED

    I'll give that a go once I know I am ready to do a fresh install in case something goes awry and report back. Greatly appreciate the tip!
  3. BigBullShinner

    Block Device Issue/ resizing: SOLVED

    here's what I got: results: $ sudo vgs [sudo] password for ******: VG #PV #LV #SN Attr VSize VFree zorin-vg 1 2 0 wz--n- <452.02g <333.50g $ sudo lvs LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert root...
  4. BigBullShinner

    Block Device Issue/ resizing: SOLVED

    Wow, thanks for the rundown. I really appreciate that detailed process outline. I am still gun-shy of getting into the custom installation/partitioning process. I tend to get pretty bogged down with new techniques, which custom installs and partitioning is for me still. Even though I have done a...
  5. BigBullShinner

    Block Device Issue/ resizing: SOLVED

    I am not really resistant to rebuilding but am trying to delay it while maximizing what I can do with my current setup (so yah, probably a bit resistant ;). Getting my setup dialed in actually has taken me quite a long time and I haven't come close to diminishing returns by checking out my...
  6. BigBullShinner

    Block Device Issue/ resizing: SOLVED

    Got it. I'll check that out and post the results here later.
  7. BigBullShinner

    Block Device Issue/ resizing: SOLVED

    Yes, that is the device. I only know there is not enough space because when I try to import more virtual machines into virtualbox it says not enough space. Also in Disks I can select the Block device and it gives the free space available there. After running those commands both came out with...
  8. BigBullShinner

    Block Device Issue/ resizing: SOLVED

    Here is the full output from Terminal: Disk /dev/nvme0n1: 465.8 GiB, 500107862016 bytes, 976773168 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...
  9. BigBullShinner

    Block Device Issue/ resizing: SOLVED

    Looking that way. If so, it's gonna be back to Linux Mint for sure:)
  10. BigBullShinner

    Block Device Issue/ resizing: SOLVED

    Here's the output. I *'d out the disk identifier because I don't know if that is a security risk, let me know if needed: Disk /dev/nvme0n1: 465.8 GiB, 500107862016 bytes, 976773168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size...
  11. BigBullShinner

    Block Device Issue/ resizing: SOLVED

    I see that it is not recommended but I'm still considering giving it a try because it will avoid having to do a fresh install possibly.
  12. BigBullShinner

    Block Device Issue/ resizing: SOLVED

    Thanks for the welcome! More info on my setup: 1. On ZorinOS 15.3 2. Used Clonezilla to create clone and to restore. I used Disks to format the SSD before restoring. 3. I used G-parted after restoring to grow the partition of the restored Image, but the Block Device didn't grow along with it.
  13. BigBullShinner

    Block Device Issue/ resizing: SOLVED

    Hello, Hopefully I haven't missed this discussion in other posts but after searching a bit I am not finding any about my specific issue. My problem is that I have a Block Device that is apparently the home of my filesystem and is 128 gb in size with about 40 GB free. I recently upgraded my...
Top