dmraid tries to mount disk that is part of an array at startup
up vote
0
down vote
favorite
I have setup a software RAID mirror using two disks - /dev/sdb and /dev/sdc - with dmraid a long time ago, so I don't quite remember what I actually did. But I remember that mounting at startup did not work, so I went to mounting the mirror's partitions by a script I ran after logging in each time.
After migrating from ubuntu to Arch and having merged all the mirror's partitions into one, I gave mounting that partition at startup another try, yet without success. What I can see in the system logs is that dmraid-activate-and-mount tries to mount one of the actual disks after activating the array. The respective lines from journalctl are
dmraid-activate-and-mount[266]: RAID set "pdc_iigaihha" was activated
dmraid-activate-and-mount[266]: RAID set "pdc_iigaihhap3" was activated
dmraid-activate-and-mount[266]: mount: /run/media/[user]/Data: /dev/sdc3 already mounted or mount point busy
It varies which of the two disks appears in the message. The job then times out at boot which has me waiting for 90 seconds:
systemd[1]: dev-mapper-pdc_iigaihhap3.device: Job dev-mapper-pdc_iigaihhap3.device/start timed out.
systemd[1]: Timed out waiting for device dev-mapper-pdc_iigaihhap3.device.
I am then presented an emergency logon where I type in my password and continue boot with systemctl default. Afterwards the mirror's partition is correctly mounted at the mount point specified by my fstab. That entry reads
/dev/mapper/pdc_iigaihhap3 /run/media/[user]/Data ext4 rw,exec,nosuid,nodev,uhelper=udisks,noatime 0 0
I cannot use a UUID for mounting because the UUID of the mirror's partition is the same as the UUIDs of the actual drives' partitions. blkid yields
/dev/sdb3: LABEL="Data" UUID="f021de40-1112-4919-a7c1-d4feea107780" TYPE="ext4" PARTUUID="00061046-03"
/dev/sdc3: LABEL="Data" UUID="f021de40-1112-4919-a7c1-d4feea107780" TYPE="ext4" PARTUUID="00061046-03"
/dev/mapper/pdc_iigaihha: PTUUID="00061046" PTTYPE="dos"
/dev/mapper/pdc_iigaihhap3: LABEL="Data" UUID="f021de40-1112-4919-a7c1-d4feea107780" TYPE="ext4"
In case it is helpful here is the output of dmraid -r:
name : pdc_iigaihha
size : 3906249984
stride : 128
type : mirror
status : ok
subsets: 0
devs : 2
spares : 0
And here dmraid -rs output:
/dev/sdc: pdc, "pdc_iigaihha", mirror, ok, 3906249984 sectors, data@ 0
/dev/sdb: pdc, "pdc_iigaihha", mirror, ok, 3906249984 sectors, data@ 0
What am I doing wrong? How can I get the system to just mount the mirror's partition and prevent it from trying to also mount one of the array's members?
linux boot raid mount
asked Nov 20 at 7:57
Ratatwisker
34
add a comment |
up vote
0
down vote
favorite
I have setup a software RAID mirror using two disks - /dev/sdb and /dev/sdc - with dmraid a long time ago, so I don't quite remember what I actually did. But I remember that mounting at startup did not work, so I went to mounting the mirror's partitions by a script I ran after logging in each time.
After migrating from ubuntu to Arch and having merged all the mirror's partitions into one, I gave mounting that partition at startup another try, yet without success. What I can see in the system logs is that dmraid-activate-and-mount tries to mount one of the actual disks after activating the array. The respective lines from journalctl are
dmraid-activate-and-mount[266]: RAID set "pdc_iigaihha" was activated
dmraid-activate-and-mount[266]: RAID set "pdc_iigaihhap3" was activated
dmraid-activate-and-mount[266]: mount: /run/media/[user]/Data: /dev/sdc3 already mounted or mount point busy
It varies which of the two disks appears in the message. The job then times out at boot which has me waiting for 90 seconds:
systemd[1]: dev-mapper-pdc_iigaihhap3.device: Job dev-mapper-pdc_iigaihhap3.device/start timed out.
systemd[1]: Timed out waiting for device dev-mapper-pdc_iigaihhap3.device.
I am then presented an emergency logon where I type in my password and continue boot with systemctl default. Afterwards the mirror's partition is correctly mounted at the mount point specified by my fstab. That entry reads
/dev/mapper/pdc_iigaihhap3 /run/media/[user]/Data ext4 rw,exec,nosuid,nodev,uhelper=udisks,noatime 0 0
I cannot use a UUID for mounting because the UUID of the mirror's partition is the same as the UUIDs of the actual drives' partitions. blkid yields
/dev/sdb3: LABEL="Data" UUID="f021de40-1112-4919-a7c1-d4feea107780" TYPE="ext4" PARTUUID="00061046-03"
/dev/sdc3: LABEL="Data" UUID="f021de40-1112-4919-a7c1-d4feea107780" TYPE="ext4" PARTUUID="00061046-03"
/dev/mapper/pdc_iigaihha: PTUUID="00061046" PTTYPE="dos"
/dev/mapper/pdc_iigaihhap3: LABEL="Data" UUID="f021de40-1112-4919-a7c1-d4feea107780" TYPE="ext4"
In case it is helpful here is the output of dmraid -r:
name : pdc_iigaihha
size : 3906249984
stride : 128
type : mirror
status : ok
subsets: 0
devs : 2
spares : 0
And here dmraid -rs output:
/dev/sdc: pdc, "pdc_iigaihha", mirror, ok, 3906249984 sectors, data@ 0
/dev/sdb: pdc, "pdc_iigaihha", mirror, ok, 3906249984 sectors, data@ 0
What am I doing wrong? How can I get the system to just mount the mirror's partition and prevent it from trying to also mount one of the array's members?
linux boot raid mount
asked Nov 20 at 7:57
Ratatwisker
34
I think the root question may be: why is/dev/sdc3 already mounted or mount point busy? Can you investigate (1) if it's really mounted or mount point busy? (2) why the message mentionssdc3? which (I guess) should never be used directly since the wholesdcis supposed to be a part of your RAID.
– Kamil Maciorowski
Nov 20 at 8:55
@KamilMaciorowski Right after login/dev/sdc3is not mounted, and I don't think the mount point is busy. I don't know how to check for that when the startup jobs runs, though. However, I had this message from time to time when I used to mount the partition which is mapped to/dev/sdb3and/dev/sdc3when I had the UUID infstab. Sometimes mount picked - by chance it seems - one of the actual drives' partition instead or the array's. Them being "already mounted" makes sense in a way because they are part of the array.
– Ratatwisker
Nov 20 at 14:35
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have setup a software RAID mirror using two disks - /dev/sdb and /dev/sdc - with dmraid a long time ago, so I don't quite remember what I actually did. But I remember that mounting at startup did not work, so I went to mounting the mirror's partitions by a script I ran after logging in each time.
After migrating from ubuntu to Arch and having merged all the mirror's partitions into one, I gave mounting that partition at startup another try, yet without success. What I can see in the system logs is that dmraid-activate-and-mount tries to mount one of the actual disks after activating the array. The respective lines from journalctl are
dmraid-activate-and-mount[266]: RAID set "pdc_iigaihha" was activated
dmraid-activate-and-mount[266]: RAID set "pdc_iigaihhap3" was activated
dmraid-activate-and-mount[266]: mount: /run/media/[user]/Data: /dev/sdc3 already mounted or mount point busy
It varies which of the two disks appears in the message. The job then times out at boot which has me waiting for 90 seconds:
systemd[1]: dev-mapper-pdc_iigaihhap3.device: Job dev-mapper-pdc_iigaihhap3.device/start timed out.
systemd[1]: Timed out waiting for device dev-mapper-pdc_iigaihhap3.device.
I am then presented an emergency logon where I type in my password and continue boot with systemctl default. Afterwards the mirror's partition is correctly mounted at the mount point specified by my fstab. That entry reads
/dev/mapper/pdc_iigaihhap3 /run/media/[user]/Data ext4 rw,exec,nosuid,nodev,uhelper=udisks,noatime 0 0
I cannot use a UUID for mounting because the UUID of the mirror's partition is the same as the UUIDs of the actual drives' partitions. blkid yields
/dev/sdb3: LABEL="Data" UUID="f021de40-1112-4919-a7c1-d4feea107780" TYPE="ext4" PARTUUID="00061046-03"
/dev/sdc3: LABEL="Data" UUID="f021de40-1112-4919-a7c1-d4feea107780" TYPE="ext4" PARTUUID="00061046-03"
/dev/mapper/pdc_iigaihha: PTUUID="00061046" PTTYPE="dos"
/dev/mapper/pdc_iigaihhap3: LABEL="Data" UUID="f021de40-1112-4919-a7c1-d4feea107780" TYPE="ext4"
In case it is helpful here is the output of dmraid -r:
name : pdc_iigaihha
size : 3906249984
stride : 128
type : mirror
status : ok
subsets: 0
devs : 2
spares : 0
And here dmraid -rs output:
/dev/sdc: pdc, "pdc_iigaihha", mirror, ok, 3906249984 sectors, data@ 0
/dev/sdb: pdc, "pdc_iigaihha", mirror, ok, 3906249984 sectors, data@ 0
What am I doing wrong? How can I get the system to just mount the mirror's partition and prevent it from trying to also mount one of the array's members?
linux boot raid mount
asked Nov 20 at 7:57
Ratatwisker
34
I have setup a software RAID mirror using two disks - /dev/sdb and /dev/sdc - with dmraid a long time ago, so I don't quite remember what I actually did. But I remember that mounting at startup did not work, so I went to mounting the mirror's partitions by a script I ran after logging in each time.
After migrating from ubuntu to Arch and having merged all the mirror's partitions into one, I gave mounting that partition at startup another try, yet without success. What I can see in the system logs is that dmraid-activate-and-mount tries to mount one of the actual disks after activating the array. The respective lines from journalctl are
dmraid-activate-and-mount[266]: RAID set "pdc_iigaihha" was activated
dmraid-activate-and-mount[266]: RAID set "pdc_iigaihhap3" was activated
dmraid-activate-and-mount[266]: mount: /run/media/[user]/Data: /dev/sdc3 already mounted or mount point busy
It varies which of the two disks appears in the message. The job then times out at boot which has me waiting for 90 seconds:
systemd[1]: dev-mapper-pdc_iigaihhap3.device: Job dev-mapper-pdc_iigaihhap3.device/start timed out.
systemd[1]: Timed out waiting for device dev-mapper-pdc_iigaihhap3.device.
I am then presented an emergency logon where I type in my password and continue boot with systemctl default. Afterwards the mirror's partition is correctly mounted at the mount point specified by my fstab. That entry reads
/dev/mapper/pdc_iigaihhap3 /run/media/[user]/Data ext4 rw,exec,nosuid,nodev,uhelper=udisks,noatime 0 0
I cannot use a UUID for mounting because the UUID of the mirror's partition is the same as the UUIDs of the actual drives' partitions. blkid yields
/dev/sdb3: LABEL="Data" UUID="f021de40-1112-4919-a7c1-d4feea107780" TYPE="ext4" PARTUUID="00061046-03"
/dev/sdc3: LABEL="Data" UUID="f021de40-1112-4919-a7c1-d4feea107780" TYPE="ext4" PARTUUID="00061046-03"
/dev/mapper/pdc_iigaihha: PTUUID="00061046" PTTYPE="dos"
/dev/mapper/pdc_iigaihhap3: LABEL="Data" UUID="f021de40-1112-4919-a7c1-d4feea107780" TYPE="ext4"
In case it is helpful here is the output of dmraid -r:
name : pdc_iigaihha
size : 3906249984
stride : 128
type : mirror
status : ok
subsets: 0
devs : 2
spares : 0
And here dmraid -rs output:
/dev/sdc: pdc, "pdc_iigaihha", mirror, ok, 3906249984 sectors, data@ 0
/dev/sdb: pdc, "pdc_iigaihha", mirror, ok, 3906249984 sectors, data@ 0
What am I doing wrong? How can I get the system to just mount the mirror's partition and prevent it from trying to also mount one of the array's members?
linux boot raid mount
linux boot raid mount
asked Nov 20 at 7:57
Ratatwisker
34
asked Nov 20 at 7:57
Ratatwisker
34
asked Nov 20 at 7:57
Ratatwisker
34
asked Nov 20 at 7:57
Ratatwisker
34
asked Nov 20 at 7:57
Ratatwisker
34
34
I think the root question may be: why is/dev/sdc3 already mounted or mount point busy? Can you investigate (1) if it's really mounted or mount point busy? (2) why the message mentionssdc3? which (I guess) should never be used directly since the wholesdcis supposed to be a part of your RAID.
– Kamil Maciorowski
Nov 20 at 8:55
@KamilMaciorowski Right after login/dev/sdc3is not mounted, and I don't think the mount point is busy. I don't know how to check for that when the startup jobs runs, though. However, I had this message from time to time when I used to mount the partition which is mapped to/dev/sdb3and/dev/sdc3when I had the UUID infstab. Sometimes mount picked - by chance it seems - one of the actual drives' partition instead or the array's. Them being "already mounted" makes sense in a way because they are part of the array.
– Ratatwisker
Nov 20 at 14:35
add a comment |
I think the root question may be: why is/dev/sdc3 already mounted or mount point busy? Can you investigate (1) if it's really mounted or mount point busy? (2) why the message mentionssdc3? which (I guess) should never be used directly since the wholesdcis supposed to be a part of your RAID.
– Kamil Maciorowski
Nov 20 at 8:55
@KamilMaciorowski Right after login/dev/sdc3is not mounted, and I don't think the mount point is busy. I don't know how to check for that when the startup jobs runs, though. However, I had this message from time to time when I used to mount the partition which is mapped to/dev/sdb3and/dev/sdc3when I had the UUID infstab. Sometimes mount picked - by chance it seems - one of the actual drives' partition instead or the array's. Them being "already mounted" makes sense in a way because they are part of the array.
– Ratatwisker
Nov 20 at 14:35
I think the root question may be: why is
/dev/sdc3 already mounted or mount point busy? Can you investigate (1) if it's really mounted or mount point busy? (2) why the message mentions sdc3? which (I guess) should never be used directly since the whole sdc is supposed to be a part of your RAID.– Kamil Maciorowski
Nov 20 at 8:55
I think the root question may be: why is
/dev/sdc3 already mounted or mount point busy? Can you investigate (1) if it's really mounted or mount point busy? (2) why the message mentions sdc3? which (I guess) should never be used directly since the whole sdc is supposed to be a part of your RAID.– Kamil Maciorowski
Nov 20 at 8:55
@KamilMaciorowski Right after login
/dev/sdc3 is not mounted, and I don't think the mount point is busy. I don't know how to check for that when the startup jobs runs, though. However, I had this message from time to time when I used to mount the partition which is mapped to /dev/sdb3 and /dev/sdc3 when I had the UUID in fstab. Sometimes mount picked - by chance it seems - one of the actual drives' partition instead or the array's. Them being "already mounted" makes sense in a way because they are part of the array.– Ratatwisker
Nov 20 at 14:35
@KamilMaciorowski Right after login
/dev/sdc3 is not mounted, and I don't think the mount point is busy. I don't know how to check for that when the startup jobs runs, though. However, I had this message from time to time when I used to mount the partition which is mapped to /dev/sdb3 and /dev/sdc3 when I had the UUID in fstab. Sometimes mount picked - by chance it seems - one of the actual drives' partition instead or the array's. Them being "already mounted" makes sense in a way because they are part of the array.– Ratatwisker
Nov 20 at 14:35
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
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%2fsuperuser.com%2fquestions%2f1376883%2fdmraid-tries-to-mount-disk-that-is-part-of-an-array-at-startup%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
I think the root question may be: why is
/dev/sdc3 already mounted or mount point busy? Can you investigate (1) if it's really mounted or mount point busy? (2) why the message mentionssdc3? which (I guess) should never be used directly since the wholesdcis supposed to be a part of your RAID.– Kamil Maciorowski
Nov 20 at 8:55
@KamilMaciorowski Right after login
/dev/sdc3is not mounted, and I don't think the mount point is busy. I don't know how to check for that when the startup jobs runs, though. However, I had this message from time to time when I used to mount the partition which is mapped to/dev/sdb3and/dev/sdc3when I had the UUID infstab. Sometimes mount picked - by chance it seems - one of the actual drives' partition instead or the array's. Them being "already mounted" makes sense in a way because they are part of the array.– Ratatwisker
Nov 20 at 14:35