Mounting Raid Partition
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I've been struggling for hours on how to successfully mount my Raid partition. I'm using Ubuntu 18.04 and have created a 2.0TB Raid-10 array (using 4 x 1.0TB SSDs) as shown here.
I do not have deep technical knowledge but why cannot I not access the remaining volume.
If I run sudo lvscan I get:
ACTIVE '/dev/vg/swap' [<14.90 GiB] inherit
ACTIVE '/dev/vg/root' [32.59 GiB] inherit
ACTIVE '/dev/vg/temp' [9.31 GiB] inherit
ACTIVE '/dev/vg/var' [<4.66 GiB] inherit
ACTIVE '/dev/vg/home' [186.26 GiB] inherit
Further, df -h shows:
Filesystem Size Used Avail Use% Mounted on
udev 16G 0 16G 0% /dev
tmpfs 3.2G 2.3M 3.2G 1% /run
/dev/mapper/vg-root 32G 5.1G 26G 17% /
tmpfs 16G 252M 16G 2% /dev/shm
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 16G 0 16G 0% /sys/fs/cgroup
/dev/nvme2n1p1 487M 6.1M 480M 2% /boot/efi
/dev/mapper/vg-home 183G 1.6G 172G 1% /home
/dev/mapper/vg-var 4.6G 1.9G 2.5G 43% /var
/dev/mapper/vg-temp 9.2G 96M 8.6G 2% /tmp
tmpfs 3.2G 88K 3.2G 1% /run/user/1000
/dev/loop0 54M 54M 0 100% /snap/core18/719
/dev/loop1 91M 91M 0 100% /snap/core/6405
/dev/loop2 35M 35M 0 100% /snap/gtk-common-themes/1122
/dev/loop3 170M 170M 0 100% /snap/gimp/113
/dev/loop4 147M 147M 0 100% /snap/chromium/595
And sudo vgscan shows
Reading volume groups from cache.
Found volume group "vg" using metadata type lvm2
Running sudo pvscan I see the below which is exactly what I would like to access
PV /dev/md0 VG vg lvm2 [<1.82 TiB / <1.58 TiB free]
Total: 1 [<1.82 TiB] / in use: 1 [<1.82 TiB] / in no VG: 0 [0 ]
Any ideas what I have done wrong here, appears I only have access to about <250gb of storage. Here is how the individual drives have been partitioned:
I've just noticed that there is only one SSD that is mounted at /boot/efi, while the others are like the image directly above.
My /etc/fstab file looks as such:
EDIT: out for sudo vgdisplay is:
partitioning raid lvm
asked Feb 16 at 13:07
DarthtraderDarthtrader
1535
|
show 3 more comments
I've been struggling for hours on how to successfully mount my Raid partition. I'm using Ubuntu 18.04 and have created a 2.0TB Raid-10 array (using 4 x 1.0TB SSDs) as shown here.
I do not have deep technical knowledge but why cannot I not access the remaining volume.
If I run sudo lvscan I get:
ACTIVE '/dev/vg/swap' [<14.90 GiB] inherit
ACTIVE '/dev/vg/root' [32.59 GiB] inherit
ACTIVE '/dev/vg/temp' [9.31 GiB] inherit
ACTIVE '/dev/vg/var' [<4.66 GiB] inherit
ACTIVE '/dev/vg/home' [186.26 GiB] inherit
Further, df -h shows:
Filesystem Size Used Avail Use% Mounted on
udev 16G 0 16G 0% /dev
tmpfs 3.2G 2.3M 3.2G 1% /run
/dev/mapper/vg-root 32G 5.1G 26G 17% /
tmpfs 16G 252M 16G 2% /dev/shm
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 16G 0 16G 0% /sys/fs/cgroup
/dev/nvme2n1p1 487M 6.1M 480M 2% /boot/efi
/dev/mapper/vg-home 183G 1.6G 172G 1% /home
/dev/mapper/vg-var 4.6G 1.9G 2.5G 43% /var
/dev/mapper/vg-temp 9.2G 96M 8.6G 2% /tmp
tmpfs 3.2G 88K 3.2G 1% /run/user/1000
/dev/loop0 54M 54M 0 100% /snap/core18/719
/dev/loop1 91M 91M 0 100% /snap/core/6405
/dev/loop2 35M 35M 0 100% /snap/gtk-common-themes/1122
/dev/loop3 170M 170M 0 100% /snap/gimp/113
/dev/loop4 147M 147M 0 100% /snap/chromium/595
And sudo vgscan shows
Reading volume groups from cache.
Found volume group "vg" using metadata type lvm2
Running sudo pvscan I see the below which is exactly what I would like to access
PV /dev/md0 VG vg lvm2 [<1.82 TiB / <1.58 TiB free]
Total: 1 [<1.82 TiB] / in use: 1 [<1.82 TiB] / in no VG: 0 [0 ]
Any ideas what I have done wrong here, appears I only have access to about <250gb of storage. Here is how the individual drives have been partitioned:
I've just noticed that there is only one SSD that is mounted at /boot/efi, while the others are like the image directly above.
My /etc/fstab file looks as such:
EDIT: out for sudo vgdisplay is:
partitioning raid lvm
asked Feb 16 at 13:07
DarthtraderDarthtrader
1535
1
Since you put your RAID/dev/md0under control of LVM, you wouldn't mount the RAID directly but rather manage available space through LVM and mount the resulting logical volumes like it is done with /, /home, /tmp ... already. Usingvgdisplayshould reveal how much space is left in the volume group. And depending on what you actually want to achieve, you can create a new logical volume that can be mounted then or grow one or more of the existing ones.
– Thomas
Feb 16 at 13:24
Please show the output ofsudo vgdisplay.
– Michael Hampton
Feb 16 at 15:15
See above @Thomas
– Darthtrader
Feb 17 at 2:01
@Thomas I just want to use the remaining file space to install applications separate to the OS as well as store large data files. Plain vanilla stuff.
– Darthtrader
Feb 17 at 2:19
1
maybe this helps?
– Thomas
Feb 18 at 6:57
|
show 3 more comments
I've been struggling for hours on how to successfully mount my Raid partition. I'm using Ubuntu 18.04 and have created a 2.0TB Raid-10 array (using 4 x 1.0TB SSDs) as shown here.
I do not have deep technical knowledge but why cannot I not access the remaining volume.
If I run sudo lvscan I get:
ACTIVE '/dev/vg/swap' [<14.90 GiB] inherit
ACTIVE '/dev/vg/root' [32.59 GiB] inherit
ACTIVE '/dev/vg/temp' [9.31 GiB] inherit
ACTIVE '/dev/vg/var' [<4.66 GiB] inherit
ACTIVE '/dev/vg/home' [186.26 GiB] inherit
Further, df -h shows:
Filesystem Size Used Avail Use% Mounted on
udev 16G 0 16G 0% /dev
tmpfs 3.2G 2.3M 3.2G 1% /run
/dev/mapper/vg-root 32G 5.1G 26G 17% /
tmpfs 16G 252M 16G 2% /dev/shm
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 16G 0 16G 0% /sys/fs/cgroup
/dev/nvme2n1p1 487M 6.1M 480M 2% /boot/efi
/dev/mapper/vg-home 183G 1.6G 172G 1% /home
/dev/mapper/vg-var 4.6G 1.9G 2.5G 43% /var
/dev/mapper/vg-temp 9.2G 96M 8.6G 2% /tmp
tmpfs 3.2G 88K 3.2G 1% /run/user/1000
/dev/loop0 54M 54M 0 100% /snap/core18/719
/dev/loop1 91M 91M 0 100% /snap/core/6405
/dev/loop2 35M 35M 0 100% /snap/gtk-common-themes/1122
/dev/loop3 170M 170M 0 100% /snap/gimp/113
/dev/loop4 147M 147M 0 100% /snap/chromium/595
And sudo vgscan shows
Reading volume groups from cache.
Found volume group "vg" using metadata type lvm2
Running sudo pvscan I see the below which is exactly what I would like to access
PV /dev/md0 VG vg lvm2 [<1.82 TiB / <1.58 TiB free]
Total: 1 [<1.82 TiB] / in use: 1 [<1.82 TiB] / in no VG: 0 [0 ]
Any ideas what I have done wrong here, appears I only have access to about <250gb of storage. Here is how the individual drives have been partitioned:
I've just noticed that there is only one SSD that is mounted at /boot/efi, while the others are like the image directly above.
My /etc/fstab file looks as such:
EDIT: out for sudo vgdisplay is:
partitioning raid lvm
asked Feb 16 at 13:07
DarthtraderDarthtrader
1535
I've been struggling for hours on how to successfully mount my Raid partition. I'm using Ubuntu 18.04 and have created a 2.0TB Raid-10 array (using 4 x 1.0TB SSDs) as shown here.
I do not have deep technical knowledge but why cannot I not access the remaining volume.
If I run sudo lvscan I get:
ACTIVE '/dev/vg/swap' [<14.90 GiB] inherit
ACTIVE '/dev/vg/root' [32.59 GiB] inherit
ACTIVE '/dev/vg/temp' [9.31 GiB] inherit
ACTIVE '/dev/vg/var' [<4.66 GiB] inherit
ACTIVE '/dev/vg/home' [186.26 GiB] inherit
Further, df -h shows:
Filesystem Size Used Avail Use% Mounted on
udev 16G 0 16G 0% /dev
tmpfs 3.2G 2.3M 3.2G 1% /run
/dev/mapper/vg-root 32G 5.1G 26G 17% /
tmpfs 16G 252M 16G 2% /dev/shm
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 16G 0 16G 0% /sys/fs/cgroup
/dev/nvme2n1p1 487M 6.1M 480M 2% /boot/efi
/dev/mapper/vg-home 183G 1.6G 172G 1% /home
/dev/mapper/vg-var 4.6G 1.9G 2.5G 43% /var
/dev/mapper/vg-temp 9.2G 96M 8.6G 2% /tmp
tmpfs 3.2G 88K 3.2G 1% /run/user/1000
/dev/loop0 54M 54M 0 100% /snap/core18/719
/dev/loop1 91M 91M 0 100% /snap/core/6405
/dev/loop2 35M 35M 0 100% /snap/gtk-common-themes/1122
/dev/loop3 170M 170M 0 100% /snap/gimp/113
/dev/loop4 147M 147M 0 100% /snap/chromium/595
And sudo vgscan shows
Reading volume groups from cache.
Found volume group "vg" using metadata type lvm2
Running sudo pvscan I see the below which is exactly what I would like to access
PV /dev/md0 VG vg lvm2 [<1.82 TiB / <1.58 TiB free]
Total: 1 [<1.82 TiB] / in use: 1 [<1.82 TiB] / in no VG: 0 [0 ]
Any ideas what I have done wrong here, appears I only have access to about <250gb of storage. Here is how the individual drives have been partitioned:
I've just noticed that there is only one SSD that is mounted at /boot/efi, while the others are like the image directly above.
My /etc/fstab file looks as such:
EDIT: out for sudo vgdisplay is:
partitioning raid lvm
partitioning raid lvm
asked Feb 16 at 13:07
DarthtraderDarthtrader
1535
asked Feb 16 at 13:07
DarthtraderDarthtrader
1535
edited Feb 17 at 2:07
Darthtrader
asked Feb 16 at 13:07
DarthtraderDarthtrader
1535
asked Feb 16 at 13:07
DarthtraderDarthtrader
1535
asked Feb 16 at 13:07
DarthtraderDarthtrader
1535
1535
1
Since you put your RAID/dev/md0under control of LVM, you wouldn't mount the RAID directly but rather manage available space through LVM and mount the resulting logical volumes like it is done with /, /home, /tmp ... already. Usingvgdisplayshould reveal how much space is left in the volume group. And depending on what you actually want to achieve, you can create a new logical volume that can be mounted then or grow one or more of the existing ones.
– Thomas
Feb 16 at 13:24
Please show the output ofsudo vgdisplay.
– Michael Hampton
Feb 16 at 15:15
See above @Thomas
– Darthtrader
Feb 17 at 2:01
@Thomas I just want to use the remaining file space to install applications separate to the OS as well as store large data files. Plain vanilla stuff.
– Darthtrader
Feb 17 at 2:19
1
maybe this helps?
– Thomas
Feb 18 at 6:57
|
show 3 more comments
1
Since you put your RAID/dev/md0under control of LVM, you wouldn't mount the RAID directly but rather manage available space through LVM and mount the resulting logical volumes like it is done with /, /home, /tmp ... already. Usingvgdisplayshould reveal how much space is left in the volume group. And depending on what you actually want to achieve, you can create a new logical volume that can be mounted then or grow one or more of the existing ones.
– Thomas
Feb 16 at 13:24
Please show the output ofsudo vgdisplay.
– Michael Hampton
Feb 16 at 15:15
See above @Thomas
– Darthtrader
Feb 17 at 2:01
@Thomas I just want to use the remaining file space to install applications separate to the OS as well as store large data files. Plain vanilla stuff.
– Darthtrader
Feb 17 at 2:19
1
maybe this helps?
– Thomas
Feb 18 at 6:57
1
1
Since you put your RAID
/dev/md0 under control of LVM, you wouldn't mount the RAID directly but rather manage available space through LVM and mount the resulting logical volumes like it is done with /, /home, /tmp ... already. Using vgdisplay should reveal how much space is left in the volume group. And depending on what you actually want to achieve, you can create a new logical volume that can be mounted then or grow one or more of the existing ones.– Thomas
Feb 16 at 13:24
Since you put your RAID
/dev/md0 under control of LVM, you wouldn't mount the RAID directly but rather manage available space through LVM and mount the resulting logical volumes like it is done with /, /home, /tmp ... already. Using vgdisplay should reveal how much space is left in the volume group. And depending on what you actually want to achieve, you can create a new logical volume that can be mounted then or grow one or more of the existing ones.– Thomas
Feb 16 at 13:24
Please show the output of
sudo vgdisplay.– Michael Hampton
Feb 16 at 15:15
Please show the output of
sudo vgdisplay.– Michael Hampton
Feb 16 at 15:15
See above @Thomas
– Darthtrader
Feb 17 at 2:01
See above @Thomas
– Darthtrader
Feb 17 at 2:01
@Thomas I just want to use the remaining file space to install applications separate to the OS as well as store large data files. Plain vanilla stuff.
– Darthtrader
Feb 17 at 2:19
@Thomas I just want to use the remaining file space to install applications separate to the OS as well as store large data files. Plain vanilla stuff.
– Darthtrader
Feb 17 at 2:19
1
1
maybe this helps?
– Thomas
Feb 18 at 6:57
maybe this helps?
– Thomas
Feb 18 at 6:57
|
show 3 more comments
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1118750%2fmounting-raid-partition%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1118750%2fmounting-raid-partition%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
Since you put your RAID
/dev/md0under control of LVM, you wouldn't mount the RAID directly but rather manage available space through LVM and mount the resulting logical volumes like it is done with /, /home, /tmp ... already. Usingvgdisplayshould reveal how much space is left in the volume group. And depending on what you actually want to achieve, you can create a new logical volume that can be mounted then or grow one or more of the existing ones.– Thomas
Feb 16 at 13:24
Please show the output of
sudo vgdisplay.– Michael Hampton
Feb 16 at 15:15
See above @Thomas
– Darthtrader
Feb 17 at 2:01
@Thomas I just want to use the remaining file space to install applications separate to the OS as well as store large data files. Plain vanilla stuff.
– Darthtrader
Feb 17 at 2:19
1
maybe this helps?
– Thomas
Feb 18 at 6:57