On Sat, Feb 16, 2019 at 03:00:08PM +1100, Morrie Wyatt wrote:The one extra step you might need to add to the end of Craig's list would be to force a rebuild of your bootloader configuration (probably Grub) so that the fstab UUID / LABEL changes get propagated into grub's config files.It certainly can't hurt to do that but it shouldn't be necessary. Grub uses UUIDs by default unless you tell it not to. There's a commented out option in /etc/default/grub on debian/ubuntu systems to disable use grub's of UUID: # Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux #GRUB_DISABLE_LINUX_UUID=true There's almost no reason why anyone would need to uncomment that. It might, however, be worthwhile running 'grub-install' on ALL of the drives *after* the system has successfully booted with the new drives installed. That way the grub first stage boot loader will be available no matter which drive the BIOS tries to boot from (this is assuming that it's an old-style BIOS boot, rather than UEFI. UEFI is different, it loads grub directly from a smallish FAT-32 EFI partition). craig -- craig sanders <cas@taz.net.au> _______________________________________________ luv-main mailing list luv-main@luv.asn.au https://lists.luv.asn.au/cgi-bin/mailman/listinfo/luv-main
Hi All.
I fired up gparted
sda1 is found and has very little space left
sdb1 has been found and automatically configured thus:
Partition /dev/sdb1 (key symbol)
Filesystem lvm2 pv
Mount point Ubuntu-vg
Size 1.82TiB Used 1.82TiB Unused 376.00MiB Flags lvm
The second drive shows as /dev/sdc
Partition unallocated
File system unallocated
size 1.82TiB
Used - Unused - Flags (empty)
so I am at a loss where to go now. I am contemplating backing up my only drive, and then plugging in the two new drives and running a server install in Ubuntu, letting it pick them up in the process.
Thanks
Andrew