On Fri, Jun 26, 2020 at 6:43 AM wrote:
> On Fri, Jun 26, 2020 at 06:38:09AM -0300, Franz wrote:
>
> > Next time I would suggest a very simple and reliable backup of the old
> > disk, install Qubes on the new disk, restore backup on the new disk and
> > you'll have a clean new system with no
On Fri, Jun 26, 2020 at 06:38:09AM -0300, Franz wrote:
> Next time I would suggest a very simple and reliable backup of the old
> disk, install Qubes on the new disk, restore backup on the new disk and
> you'll have a clean new system with no problems.
uh. even in the best case, this is a _lot_
On Thu, Jun 25, 2020 at 7:45 PM wrote:
> On Thu, Jun 25, 2020 at 10:29:33PM +, 'Matt Drez' via qubes-users
> wrote:
> > How to safely raise it to the maximum size (1TB ) and not just an
> > arbitrary number that's close enough?
>
> which "it"?
> if you bought a "1TB disk", that usualy means
On Thu, Jun 25, 2020 at 10:29:33PM +, 'Matt Drez' via qubes-users wrote:
> How to safely raise it to the maximum size (1TB ) and not just an
> arbitrary number that's close enough?
which "it"?
if you bought a "1TB disk", that usualy means 931GiB.
the pvresize dance means the pv is now as
This worked (see below). Thank you so much. You rock!
Only one question remained:
How to safely raise it to the maximum size (1TB ) and not just an arbitrary
number that's close enough?
[@dom0 ~]$ sudo pvresize --setphysicalvolumesize 900g
On Thu, Jun 25, 2020 at 08:54:51PM +, Matt Drez wrote:
> This is where I am at now (below). What would be the best course of
> action. What would you if this was your mess to clean up? :)
> WARNING: Device
> /dev/mapper/luks-55a20051-8c1a-435e-a1c8-862493f2d576 has size of
> 1948924598
This is where I am at now (below). What would be the best course of action.
What would you if this was your mess to clean up? :)
[@dom0 ~]$ sudo pvs
WARNING: Device /dev/mapper/luks-55a20051-8c1a-435e-a1c8-862493f2d576 has
size of 1948924598 sectors which is smaller than corresponding PV size
On Thu, Jun 25, 2020 at 08:05:11PM +, Matt Drez wrote:
> That makes total sense. Well, I'm glad I didn't screw everything up
> but now how do I reverse what I have done so I could achieve my goal?
> How can I "take away" the 100% free space I assigned to root and give
> it to the whole system?
> > [@dom0 ~]$ sudo lvs qubes_dom0/pool00
> > LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
> > pool00 qubes_dom0 twi-aotz-- 347.98g 87.01 58.34
>
> if you want to enlarge logical volume qubes_dom0/pool00, you
> should enlarge qubes_dom0/pool00, not random other devices.
>
On Wed, Jun 24, 2020 at 07:49:56PM +, Matt Drez wrote:
> [@dom0 ~]$ sudo lvextend -l +100%FREE /dev/mapper/qubes_dom0-root
this means you resized your dom0 root volume.
that is probably not what you were trying to do.
you can check if that worked with "df -h /" or
"lsblk -d
sorry, I was a cottonheaded-ninnymuggins. I was supposed to run the lvextend
against the /dev/mapper/qubes_dom0-root
Now I did it but for some reason the lvs still won't see the full size
[@dom0 ~]$ sudo lvextend -l +100%FREE /dev/mapper/qubes_dom0-root
WARNING: Sum of all thin volume
I've got this far but got stuck (see last output):
[@dom0 ~]$ sudo pvs
/dev/mapper/luks-55a20051-8c1a-435e-a1c8-862493f2d576: read failed after 0 of
512 at 998053052416: Input/output error
/dev/mapper/luks-55a20051-8c1a-435e-a1c8-862493f2d576: read failed after 0 of
512 at 998053171200:
On Wed, Jun 24, 2020 at 04:38:21PM +, Matt Drez wrote:
> None of the three commands you gave showed 900+GB
you can doublecheck the partition and luks device already have the
right size with ...
lsblk -d /dev/nvme* /dev/mapper/luks-*
if these show 900+GB you are good to go with the lvm
> i dont fully understand that gparted screenshot, but it looks like
> you resized the partition already.
>
> so whats missing is on one of the LVM layers of the stack.
>
> check with "pvs", it should list a /dev/mapper/luks-something.
> does that PV have the right PSize of 900+ GB?
> if not,
On Tue, Jun 23, 2020 at 04:11:56PM +, 'Matt Drez' via qubes-users wrote:
> I was trying to move my Qubes to a bigger disk. I used clonezilla to
> clone it. I was able to successfully boot up but Qubes was still
> complaining that my disk is full. For some reason it doesn't want to
> use the
15 matches
Mail list logo
