Not able to superblock 1 harddrive...

  • Hey all.


    My question is this: Does it matter, that i wasnt able to zero the superblock on one of my harddrives before i disassembled my raid5?


    Here is what i did:


    I made a mess in my OMV and wanted to disassemble my raid5, but i wasnt able to use the webgui


    I then booted up the systemrescuecd program:
    http://www.sysresccd.org/


    and i made a mistake by trying to partition "dev/sda" before i had disassembled the raid first.


    Now, i followed this guide:
    http://ubuntuforums.org/showthread.php?t=884556


    and i was able to:


    sudo mdadm --zero-superblock /dev/sdb
    sudo mdadm --zero-superblock /dev/sdc
    sudo mdadm --zero-superblock /dev/sdd
    sudo mdadm --zero-superblock /dev/sde


    No problem there!!


    But i couldent:


    sudo mdadm --zero-superblock /dev/sda


    it gave me this:


    mdadm: Unrecognised md component device - /dev/sda


    but i was able to give sda a partition and a filesystem. So my question is, does it matter that i wasnt able to do the superblock command on the sda drive?



    fdisk -l give me this:




    Thanks for all the support you guys have given me the past year :)

  • I just tried some things:


    i did:
    mdadm -E /dev/sda


    and got:
    MBR Magic : aa55


    and:
    dd if=/dev/zero of=/dev/sda bs=512 count=1


    and got:
    1+0 records in
    1+0 records out
    512 bytes (512 B) copied, 0.436029 s, 1.2 kB/s



    now when i do this:
    mdadm -E /dev/sda


    i get:
    No md superblock detected on /dev/sda.


    just as on my other disks. So cant i assume that my HDD's are back to normal and i shouldent be worried about it?

    • Offizieller Beitrag

    If you use the superblock command and zero the drive (I would use a higher count than 1 though), it should be back to normal. You can also do the following:


    parted /dev/sda mklabel msdos

    omv 7.0-32 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.9 | compose 7.0.9 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • If you use the superblock command and zero the drive (I would use a higher count than 1 though), it should be back to normal. You can also do the following:


    parted /dev/sda mklabel msdos

    i tried that but can't remove lable linux_raid_member from sde to sdi

  • mdadm --zero-superblock /dev/sde /dev/sdf /dev/sdg /dev/sdh /dev/sdi

    i tried that but can't remove lable linux_raid_member from sde to sdi

    mdadm --zero-superblock /dev/sde /dev/sdf /dev/sdg /dev/sdh /dev/sdi

    also check /etc/mdadm/mdadm.conf

    Dell 3050 Micro - i5-7500T 2.70GHz, 16gb Ram, 8-28 watts, OMV 6.

    Plugins - compose, cputemp, diskstats, omv-extras, sharerootfs.

    Drives - 128gb USB pen Backup, 240gb SSD boot, 2tb nvme data/leeching, 16tb Media.

    Docker - nginx-proxy-manager, plex, prowlarr, qbittorrentvpn, radarr, sonarr, vaultwarden, watchtower.


    :/ RAID IS NOT A BACKUP. :/   :/ >> Windows SMB Help << :/

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!