[PLUG] Mediasonic Probox issues

[Ben Koenig]

The professional way to figure this out is to stop thinking like a professional.

Step away from the command prompt and look at your enclosure as someone who will be using it every single day.

- How many bays does your enclosure have?
-How many ports does it use to connect to your computer?
-What kind of ports are they?
-which ports do they connect to on your computer?

Also, get some sticky notes and label each bay for the job you want it to do. for 2drive RAID 1 I would pick 2 of the bays and label them A and B.

Forget about drive letters. You cant rely on sda/b/c for this so set fdisk aside.

-Ben
Sent from ProtonMail mobile

-------- Original Message --------
On Jan 6, 2022, 12:39 PM, Rich Shepard wrote:

> The Mediasonic Probox has four slots. Originally shown as /dev/sdc,
> /dev/sdd, /dev/sde, and /dev/sdf.
>
> The four disks were formatted as LVM. And I used mdadm to create /dev/md0
> from the last two: sde and sdf.
>
> Looking now at fdisk -l I find:
> The primary GPT table is corrupt, but the backup appears OK, so that will be used.
> Disk /dev/sde: 1.8 TiB, 2000398934016 bytes, 3907029168 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: gpt
> Disk identifier: 87B50654-32EB-48EC-9659-AA9FCA8805BD
>
> Device Start End Sectors Size Type
> /dev/sde1 2048 3907029134 3907027087 1.8T Linux LVM
>
> The primary GPT table is corrupt, but the backup appears OK, so that will be used.
> Disk /dev/sdf: 1.8 TiB, 2000398934016 bytes, 3907029168 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: gpt
> Disk identifier: 3D392BA1-0BA4-43A6-93C2-46B7B0725799
>
> Device Start End Sectors Size Type
> /dev/sdf1 2048 3907029134 3907027087 1.8T Linux LVM
>
> The primary GPT table is corrupt, but the backup appears OK, so that will be used.
> Disk /dev/sdg: 931.5 GiB, 1000204886016 bytes, 1953525168 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: gpt
> Disk identifier: CBB788C9-2244-4FDF-AD06-487E2BAB42F4
>
> Device Start End Sectors Size Type
> /dev/sdg1 2048 1953525134 1953523087 931.5G Linux LVM
>
> The primary GPT table is corrupt, but the backup appears OK, so that will be used.
> Disk /dev/sdh: 931.5 GiB, 1000204886016 bytes, 1953525168 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: gpt
> Disk identifier: 0D48188B-6B6E-49CC-A326-B2EB68FA4631
>
> Device Start End Sectors Size Type
> /dev/sdh1 2048 1953525134 1953523087 931.5G Linux LVM
>
> Disk /dev/md0: 931.4 GiB, 1000070643712 bytes, 1953262976 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
>
> It looks to me that /dev/sdc was changed to /dev/sdg and /dev/sdd was
> changed to /dev/sdh.
>
> I think I'll use cfdisk to remove all of /dev/sd{e,f,g,h} and start with
> fresh drives in the enclosure.
>
> What I want in that enclosure are the two 2TiB drives as a single logical
> volume named data2 with ext4 on each and the two 1TiB drives as a RAID1 with
> ext4 on each. My limited understanding is that the two RAID disks don't need
> to be setup as a LV. Is that correct?
>
> Both /dev/sda and /dev/sdb are in the desktop so what I want is to have the
> two 2TiB disks as /dev/sbc and the two 1TiB disks as /dev/md0.
>
> As a non-professional system/network admin I need advice from you
> professionals to get the results in the next go-around.
>
> TIA,
>
> Rich