RAID card overwrites disk's filesystem signature - and fstab can't mount it












0















I have a RAID card (Sil3124) in an Ubuntu 18.10 machine. I want to connect independent disks (ext4) to it.



After connecting, I find an entry in lsblk with FSTYPE = silicon_medley_raid_member (the same goes for blkid).



Trying to mount, unsurprisingly, results in this error: mount: /tmp/drive: unknown filesystem type 'silicon_medley_raid_member'.



Using wipefs I see there are two fs signatures on the same disk/partition.



DEVICE OFFSET       TYPE                       UUID                                  LABEL
sda 0x45dd825e60 silicon_medley_raid_member
sda 0x438 ext4 86119597-b945-4dec-a7a5-8cf313f93b40 mydisk


If I wipe the "raid" one, lsblk recognises the disk normally and I can mount it normally, with my files there as expected. However, when I reboot, the "raid" signature is there again, so I suppose the raid card rewrites it every boot.



The problem is that I want to mount the drive with fstab, and while the "raid" signature is there I can't find a way for fstab to mount it, as the disk is not findable by UUID or label while the weird signature is there.



The raid card menu is very simple, and I tried all options for single-disk mounts, but the raid signature is always written.



Is there any way to avoid that signature being written, or for fstab to find the "right" signature? If not, is it even possible to run a script pre-fstab to execute wipefs manually (although this feels like a dirty hack)?










share|improve this question























  • Can you plug the drives in to non-raid ports?

    – Appleoddity
    Dec 27 '18 at 3:58











  • Unfortunately all motherboard SATA ports are in use (although yes, for testing purposes I have tried and it works normally, provided I wipe the raid signature the first time).

    – Guilherme Borges
    Dec 27 '18 at 4:09











  • Why not create partitions on these disks? It appears the RAID signature is at the end of the disk.

    – Daniel B
    Dec 27 '18 at 4:43











  • Yes, that does work, thanks.

    – Guilherme Borges
    Dec 28 '18 at 21:24
















0















I have a RAID card (Sil3124) in an Ubuntu 18.10 machine. I want to connect independent disks (ext4) to it.



After connecting, I find an entry in lsblk with FSTYPE = silicon_medley_raid_member (the same goes for blkid).



Trying to mount, unsurprisingly, results in this error: mount: /tmp/drive: unknown filesystem type 'silicon_medley_raid_member'.



Using wipefs I see there are two fs signatures on the same disk/partition.



DEVICE OFFSET       TYPE                       UUID                                  LABEL
sda 0x45dd825e60 silicon_medley_raid_member
sda 0x438 ext4 86119597-b945-4dec-a7a5-8cf313f93b40 mydisk


If I wipe the "raid" one, lsblk recognises the disk normally and I can mount it normally, with my files there as expected. However, when I reboot, the "raid" signature is there again, so I suppose the raid card rewrites it every boot.



The problem is that I want to mount the drive with fstab, and while the "raid" signature is there I can't find a way for fstab to mount it, as the disk is not findable by UUID or label while the weird signature is there.



The raid card menu is very simple, and I tried all options for single-disk mounts, but the raid signature is always written.



Is there any way to avoid that signature being written, or for fstab to find the "right" signature? If not, is it even possible to run a script pre-fstab to execute wipefs manually (although this feels like a dirty hack)?










share|improve this question























  • Can you plug the drives in to non-raid ports?

    – Appleoddity
    Dec 27 '18 at 3:58











  • Unfortunately all motherboard SATA ports are in use (although yes, for testing purposes I have tried and it works normally, provided I wipe the raid signature the first time).

    – Guilherme Borges
    Dec 27 '18 at 4:09











  • Why not create partitions on these disks? It appears the RAID signature is at the end of the disk.

    – Daniel B
    Dec 27 '18 at 4:43











  • Yes, that does work, thanks.

    – Guilherme Borges
    Dec 28 '18 at 21:24














0












0








0








I have a RAID card (Sil3124) in an Ubuntu 18.10 machine. I want to connect independent disks (ext4) to it.



After connecting, I find an entry in lsblk with FSTYPE = silicon_medley_raid_member (the same goes for blkid).



Trying to mount, unsurprisingly, results in this error: mount: /tmp/drive: unknown filesystem type 'silicon_medley_raid_member'.



Using wipefs I see there are two fs signatures on the same disk/partition.



DEVICE OFFSET       TYPE                       UUID                                  LABEL
sda 0x45dd825e60 silicon_medley_raid_member
sda 0x438 ext4 86119597-b945-4dec-a7a5-8cf313f93b40 mydisk


If I wipe the "raid" one, lsblk recognises the disk normally and I can mount it normally, with my files there as expected. However, when I reboot, the "raid" signature is there again, so I suppose the raid card rewrites it every boot.



The problem is that I want to mount the drive with fstab, and while the "raid" signature is there I can't find a way for fstab to mount it, as the disk is not findable by UUID or label while the weird signature is there.



The raid card menu is very simple, and I tried all options for single-disk mounts, but the raid signature is always written.



Is there any way to avoid that signature being written, or for fstab to find the "right" signature? If not, is it even possible to run a script pre-fstab to execute wipefs manually (although this feels like a dirty hack)?










share|improve this question














I have a RAID card (Sil3124) in an Ubuntu 18.10 machine. I want to connect independent disks (ext4) to it.



After connecting, I find an entry in lsblk with FSTYPE = silicon_medley_raid_member (the same goes for blkid).



Trying to mount, unsurprisingly, results in this error: mount: /tmp/drive: unknown filesystem type 'silicon_medley_raid_member'.



Using wipefs I see there are two fs signatures on the same disk/partition.



DEVICE OFFSET       TYPE                       UUID                                  LABEL
sda 0x45dd825e60 silicon_medley_raid_member
sda 0x438 ext4 86119597-b945-4dec-a7a5-8cf313f93b40 mydisk


If I wipe the "raid" one, lsblk recognises the disk normally and I can mount it normally, with my files there as expected. However, when I reboot, the "raid" signature is there again, so I suppose the raid card rewrites it every boot.



The problem is that I want to mount the drive with fstab, and while the "raid" signature is there I can't find a way for fstab to mount it, as the disk is not findable by UUID or label while the weird signature is there.



The raid card menu is very simple, and I tried all options for single-disk mounts, but the raid signature is always written.



Is there any way to avoid that signature being written, or for fstab to find the "right" signature? If not, is it even possible to run a script pre-fstab to execute wipefs manually (although this feels like a dirty hack)?







linux ubuntu mount fstab






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Dec 27 '18 at 3:43









Guilherme BorgesGuilherme Borges

12




12













  • Can you plug the drives in to non-raid ports?

    – Appleoddity
    Dec 27 '18 at 3:58











  • Unfortunately all motherboard SATA ports are in use (although yes, for testing purposes I have tried and it works normally, provided I wipe the raid signature the first time).

    – Guilherme Borges
    Dec 27 '18 at 4:09











  • Why not create partitions on these disks? It appears the RAID signature is at the end of the disk.

    – Daniel B
    Dec 27 '18 at 4:43











  • Yes, that does work, thanks.

    – Guilherme Borges
    Dec 28 '18 at 21:24



















  • Can you plug the drives in to non-raid ports?

    – Appleoddity
    Dec 27 '18 at 3:58











  • Unfortunately all motherboard SATA ports are in use (although yes, for testing purposes I have tried and it works normally, provided I wipe the raid signature the first time).

    – Guilherme Borges
    Dec 27 '18 at 4:09











  • Why not create partitions on these disks? It appears the RAID signature is at the end of the disk.

    – Daniel B
    Dec 27 '18 at 4:43











  • Yes, that does work, thanks.

    – Guilherme Borges
    Dec 28 '18 at 21:24

















Can you plug the drives in to non-raid ports?

– Appleoddity
Dec 27 '18 at 3:58





Can you plug the drives in to non-raid ports?

– Appleoddity
Dec 27 '18 at 3:58













Unfortunately all motherboard SATA ports are in use (although yes, for testing purposes I have tried and it works normally, provided I wipe the raid signature the first time).

– Guilherme Borges
Dec 27 '18 at 4:09





Unfortunately all motherboard SATA ports are in use (although yes, for testing purposes I have tried and it works normally, provided I wipe the raid signature the first time).

– Guilherme Borges
Dec 27 '18 at 4:09













Why not create partitions on these disks? It appears the RAID signature is at the end of the disk.

– Daniel B
Dec 27 '18 at 4:43





Why not create partitions on these disks? It appears the RAID signature is at the end of the disk.

– Daniel B
Dec 27 '18 at 4:43













Yes, that does work, thanks.

– Guilherme Borges
Dec 28 '18 at 21:24





Yes, that does work, thanks.

– Guilherme Borges
Dec 28 '18 at 21:24










0






active

oldest

votes











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1388001%2fraid-card-overwrites-disks-filesystem-signature-and-fstab-cant-mount-it%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
















draft saved

draft discarded




















































Thanks for contributing an answer to Super User!


  • 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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1388001%2fraid-card-overwrites-disks-filesystem-signature-and-fstab-cant-mount-it%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

"Incorrect syntax near the keyword 'ON'. (on update cascade, on delete cascade,)

Alcedinidae

RAC Tourist Trophy