Debian Buster: mount raid 0 with no superblocks on boot
I have a OCZ RevoDrive, which is a PCIe SSD that actually consists of some butchered Marvell raid controller with two disks attached to it. As a result, the RevoDrive shows up as two disks
[ 8.198602] oczpcie 0000:06:00.0: Device oczpcie_6_0_0_ssd, model OCZ-REVODRIVE3, firmware revision 2.25, sectors 234441648
[ 8.218591] oczpcie 0000:06:00.0: Device oczpcie_6_0_1_ssd, model OCZ-REVODRIVE3, firmware revision 2.25, sectors 234441648
In order to use the disk one has to know that both devices are actually a raid 0, because (as far as i can tell) there is no raid metadata stored on the disk. I start the raid manually using
mdadm --build /dev/md0 --raid-devices=2 --level=0 /dev/oczpcie_6_0_0_ssd /dev/oczpcie_6_0_1_ssd
My actual problem is that I would like to mount the Windows on that disk automatically at boot time, but I can't make it work. Essentially I don't know how.
I am on Debian Buster. I did set up /etc/mdadm/mdadm.conf
with a DEVICE
an an ARRAY
-line, to use the two oczpcie*
disks to build an array /dev/md/windows
. However, the mdadm service is masked in systemd and it turns out mdadm is not even a systemd service but an old-school init script /etc/init.d/mdadm
, which is used by systemd if and when systemd sees fit. As far as I can tell systemd will start mdadm only if it detects raid superblocks on disks. Unfortunately, there aren't raid superblocks on my OCZ disks. As a result the mdadm init script is never triggered, my mdadm.conf
never read and the array never built.
I suppose I could hack a systemd service that is a shell script which does everything I do manually atm, but that seems like a bad approach. How do I make Debian start and mount that array? (I suppose mounting is as trivial as an /etc/fstab
entry. My problem most likely is only to get mdadm to start during boot.)
debian raid
add a comment |
I have a OCZ RevoDrive, which is a PCIe SSD that actually consists of some butchered Marvell raid controller with two disks attached to it. As a result, the RevoDrive shows up as two disks
[ 8.198602] oczpcie 0000:06:00.0: Device oczpcie_6_0_0_ssd, model OCZ-REVODRIVE3, firmware revision 2.25, sectors 234441648
[ 8.218591] oczpcie 0000:06:00.0: Device oczpcie_6_0_1_ssd, model OCZ-REVODRIVE3, firmware revision 2.25, sectors 234441648
In order to use the disk one has to know that both devices are actually a raid 0, because (as far as i can tell) there is no raid metadata stored on the disk. I start the raid manually using
mdadm --build /dev/md0 --raid-devices=2 --level=0 /dev/oczpcie_6_0_0_ssd /dev/oczpcie_6_0_1_ssd
My actual problem is that I would like to mount the Windows on that disk automatically at boot time, but I can't make it work. Essentially I don't know how.
I am on Debian Buster. I did set up /etc/mdadm/mdadm.conf
with a DEVICE
an an ARRAY
-line, to use the two oczpcie*
disks to build an array /dev/md/windows
. However, the mdadm service is masked in systemd and it turns out mdadm is not even a systemd service but an old-school init script /etc/init.d/mdadm
, which is used by systemd if and when systemd sees fit. As far as I can tell systemd will start mdadm only if it detects raid superblocks on disks. Unfortunately, there aren't raid superblocks on my OCZ disks. As a result the mdadm init script is never triggered, my mdadm.conf
never read and the array never built.
I suppose I could hack a systemd service that is a shell script which does everything I do manually atm, but that seems like a bad approach. How do I make Debian start and mount that array? (I suppose mounting is as trivial as an /etc/fstab
entry. My problem most likely is only to get mdadm to start during boot.)
debian raid
add a comment |
I have a OCZ RevoDrive, which is a PCIe SSD that actually consists of some butchered Marvell raid controller with two disks attached to it. As a result, the RevoDrive shows up as two disks
[ 8.198602] oczpcie 0000:06:00.0: Device oczpcie_6_0_0_ssd, model OCZ-REVODRIVE3, firmware revision 2.25, sectors 234441648
[ 8.218591] oczpcie 0000:06:00.0: Device oczpcie_6_0_1_ssd, model OCZ-REVODRIVE3, firmware revision 2.25, sectors 234441648
In order to use the disk one has to know that both devices are actually a raid 0, because (as far as i can tell) there is no raid metadata stored on the disk. I start the raid manually using
mdadm --build /dev/md0 --raid-devices=2 --level=0 /dev/oczpcie_6_0_0_ssd /dev/oczpcie_6_0_1_ssd
My actual problem is that I would like to mount the Windows on that disk automatically at boot time, but I can't make it work. Essentially I don't know how.
I am on Debian Buster. I did set up /etc/mdadm/mdadm.conf
with a DEVICE
an an ARRAY
-line, to use the two oczpcie*
disks to build an array /dev/md/windows
. However, the mdadm service is masked in systemd and it turns out mdadm is not even a systemd service but an old-school init script /etc/init.d/mdadm
, which is used by systemd if and when systemd sees fit. As far as I can tell systemd will start mdadm only if it detects raid superblocks on disks. Unfortunately, there aren't raid superblocks on my OCZ disks. As a result the mdadm init script is never triggered, my mdadm.conf
never read and the array never built.
I suppose I could hack a systemd service that is a shell script which does everything I do manually atm, but that seems like a bad approach. How do I make Debian start and mount that array? (I suppose mounting is as trivial as an /etc/fstab
entry. My problem most likely is only to get mdadm to start during boot.)
debian raid
I have a OCZ RevoDrive, which is a PCIe SSD that actually consists of some butchered Marvell raid controller with two disks attached to it. As a result, the RevoDrive shows up as two disks
[ 8.198602] oczpcie 0000:06:00.0: Device oczpcie_6_0_0_ssd, model OCZ-REVODRIVE3, firmware revision 2.25, sectors 234441648
[ 8.218591] oczpcie 0000:06:00.0: Device oczpcie_6_0_1_ssd, model OCZ-REVODRIVE3, firmware revision 2.25, sectors 234441648
In order to use the disk one has to know that both devices are actually a raid 0, because (as far as i can tell) there is no raid metadata stored on the disk. I start the raid manually using
mdadm --build /dev/md0 --raid-devices=2 --level=0 /dev/oczpcie_6_0_0_ssd /dev/oczpcie_6_0_1_ssd
My actual problem is that I would like to mount the Windows on that disk automatically at boot time, but I can't make it work. Essentially I don't know how.
I am on Debian Buster. I did set up /etc/mdadm/mdadm.conf
with a DEVICE
an an ARRAY
-line, to use the two oczpcie*
disks to build an array /dev/md/windows
. However, the mdadm service is masked in systemd and it turns out mdadm is not even a systemd service but an old-school init script /etc/init.d/mdadm
, which is used by systemd if and when systemd sees fit. As far as I can tell systemd will start mdadm only if it detects raid superblocks on disks. Unfortunately, there aren't raid superblocks on my OCZ disks. As a result the mdadm init script is never triggered, my mdadm.conf
never read and the array never built.
I suppose I could hack a systemd service that is a shell script which does everything I do manually atm, but that seems like a bad approach. How do I make Debian start and mount that array? (I suppose mounting is as trivial as an /etc/fstab
entry. My problem most likely is only to get mdadm to start during boot.)
debian raid
debian raid
asked 11 mins ago
BananguinBananguin
5,2651338
5,2651338
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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%2funix.stackexchange.com%2fquestions%2f495494%2fdebian-buster-mount-raid-0-with-no-superblocks-on-boot%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 Unix & Linux Stack Exchange!
- 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%2funix.stackexchange.com%2fquestions%2f495494%2fdebian-buster-mount-raid-0-with-no-superblocks-on-boot%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