Hi Craig,
I am unsure how much to clip as your response is comprehensive.
But to start /dev/sda1 is my 1 TB drive and it is showing as having boot
and lvm, do not know how root and swap were assigned to sdb1
The extra drives are 2 TB drives
The problem with /dev/sdc1 not being part of the group is beyond me.
I must have done something in gparted to get sdb1 recognised as part of
the group, and not been able to do the same with /dev/sdc1
The fact that /dev/sdb1 is showing as active suggests it may have been
formatted but I do not know how,
On 22/2/19 12:35 pm, Craig Sanders via luv-main wrote:
> On Thu, Feb 21, 2019 at 11:14:13PM +1100, Andrew Greig wrote:
>> Looking at the disks in gparted I have:
>>
>> /dev/sda1
>> File system lvn2 pv
>> Label
>> UUID sI0LJX-JSme-W2Yt-rFiZ-bQcV-lwFN-tSetH5
>> Volume Group ubuntu-vg
>> Members /dev/sda1 /dev/sdb1
>> Partition /dev/sda1
>> Name
>> Flags boot/lvm
>>
>> /dev/sdb1
>> File system lvm2 pv
>> Label
>> UUID 9HV3H6-JIYu-IdaS-2CGr-lkZQ-9xcB-RVu9Ks
>> Status Active
>> Volume group /dev/sda1 /dev/sdb1
>> Logical Volumes root swap-1
>> Partition Path /dev/sdb1
>> Name
>> Flags lvm
>>
>> /dev/sdc1
>> File system lvm2 pv
>> Label
>> UUID mqbYsB-xpm2-7c11-RLN5-q47a-A0bB-wcefad
>> Status Not active(not a member of any volume group)Volume Group
>> Members
>> Logical Volumes
>> Partition Path /dev/sdc1
>> Name
>> Flags lvm
>
> It looks like you've added one of the two new 3TB drives to the same
volume
> group as your root fs and swap partition. The other 3TB drive has
been turned
> into an unrelated volume group. Why?
No idea
>
> Which drive is the old 1TB drive? and which are the new 3TB drives?
/dev/sda1 is the old drive and /dev/sdb1 and /dev/sdc1 are the new drives
>
> My *guess* is that sdb1 is the old 1TB drive (because that's the only one
> where the root and swap-1 LVs are mentioned). If that's the case,
then I'll
> also guess that the 1TB drive is plugged into the second SATA
port....so when
> you plugged the new drives in, you plugged one of them into the first
SATA
> port. Try swapping the cables for those two drives around so that
the 1TB
> drive is in the first port.
>
> try running 'fdisk -l'. That will show each disk and all partitions on
> it, including the brand, model, and size of the drive. knowing the
logical
> identifiers is only half the story, you also need to know which
physical drive
> corresponds to those identifiers.
andrew@andrew-desktop:~$ sudo fdisk -l
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 1953523711 1953521664 931.5G 8e Linux LVM
Disk /dev/sdb: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0xc3e8f29f
Device Boot Start End Sectors Size Id Type
/dev/sdb1 2048 3907028991 3907026944 1.8T 8e Linux LVM
Disk /dev/sdc: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x7325946b
Device Boot Start End Sectors Size Id Type
/dev/sdc1 2048 3907028991 3907026944 1.8T 8e Linux LVM
>
> Once you have this information, i strongly recommend writing it down or
> printing it so you always have it available when planning what to do.
>
>
>> My current fstab is this
>> andrew@andrew-desktop:~$ cat /etc/fstab
>> # /etc/fstab: static file system information.
>> #
>> # Use 'blkid' to print the universally unique identifier for a
>> # device; this may be used with UUID= as a more robust way to name
devices
>> # that works even if disks are added and removed. See fstab(5).
>> #
>> # <file system> <mount point> <type> <options> <dump> <pass>
>> /dev/mapper/ubuntu--vg-root / ext4
errors=remount-ro 0 1
>> /dev/mapper/ubuntu--vg-swap_1 none swap sw
0 0
>> andrew@andrew-desktop:~$
>>
>> So /dev/sdb1 is part of a lvm group but /dev/sdc1 is not
>>
>> What command do I use to get these added to the fstab? I haven't
consciously
>> formatted either of the two new drives,is there a step I have missed?
>
> dunno, there isn't enough info to safely give any direct
instructions. the
> best I can give is generic advice that you'll have to adapt to your
hardware
> and circumstances.
>
> But the first thing you need to do is undo the existing mess - why
did you add
> one of the new drives to the existing volume group (VG)? and, since
you added
> the new drive, why didn't you just create a new logical volume (LV),
format
> it, and start using it?
This is my problem, my understanding of lvm is minimal, it allows the
partitions to grow or shrink to best use the disk space. That is it.
lvm was set up as a default in the Ubuntu install
>
> You'll need to check that it isn't being actively used in the VG, and
then
> remove that drive from the VG before you do anything else.
I am heading down to MSY soon to get a new SSD they do not have a 500Gb
Crucial MX500 (out of stock) they do have a Crucial 1TB SSD however.
I used to use a hotswap box in the days of IDE ribbon cables, is that
the sort of thing you are suggesting I use for the old 1TB sata drive
Thanks
Andrew
_______________________________________________
luv-main mailing list
[email protected]
https://lists.luv.asn.au/cgi-bin/mailman/listinfo/luv-main
