Failed to mount error on Raid 5

  • Greetings,


    I'm running .5.48 with a usb external hard drive. After the install, I loaded 3x4TB hard drives from my old raid 5 that was also part of OMV. I wiped those drives doing a quick wipe and then built the raid. Now, when I try to mount the raid, i get this:


    Error #6000:
    exception 'OMVException' with message 'Failed to mount '5144add1-94fd-4eff-8c54-23ca6309ec05': ' in /usr/share/openmediavault/engined/rpc/filesystemmgmt.inc:873
    Stack trace:
    #0 [internal function]: OMVRpcServiceFileSystemMgmt->mount(Array, Array)
    #1 /usr/share/php/openmediavault/rpcservice.inc(125): call_user_func_array(Array, Array)
    #2 /usr/share/php/openmediavault/rpc.inc(62): OMVRpcServiceAbstract->callMethod('mount', Array, Array)
    #3 /usr/sbin/omv-engined(495): OMVRpc::exec('FileSystemMgmt', 'mount', Array, Array, 1)
    #4 {main}


    Also noticed that the OS disk is now mounted as dev/SDD.


    I've seen other posts for this but no real solution. Does anyone have an idea why this is happening and the fix?

  • In the error message, you should have another error message above the textfield, we need this too.


    Also, you could try 'mount -a' via CLI to force mount the hard disk and see if that works.


    Greetings
    David

    "Well... lately this forum has become support for everything except omv" [...] "And is like someone is banning Google from their browsers"


    Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.

    Upload Logfile via WebGUI/CLI
    #openmediavault on freenode IRC | German & English | GMT+1
    Absolutely no Support via PM!

  • First part of error message:
    Failed to mount '5144add1-94fd-4eff-8c54-23ca6309ec05':


    When I try to force mount:
    Vault:~# mount -a /dev/md127
    mount: wrong fs type, bad option, bad superblock on /dev/md127,
    missing codepage or helper program, or other error
    In some cases useful info is found in syslog - try
    dmesg | tail or so

  • I just thought about mount -a without /dev/md127 in the end, but ok.


    Please post the output of cat /proc/mdstat and mdadm --detail /dev/md127


    Greetings
    David

    "Well... lately this forum has become support for everything except omv" [...] "And is like someone is banning Google from their browsers"


    Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.

    Upload Logfile via WebGUI/CLI
    #openmediavault on freenode IRC | German & English | GMT+1
    Absolutely no Support via PM!

  • As you requested:


    cat /proc/mdstat
    Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
    md127 : active raid5 sda[0] sdc[2] sdb[1]
    7814034432 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/3] [UUU]


    mdadm --detail /dev/md127
    /dev/md127:
    Version : 1.2
    Creation Time : Wed Aug 20 21:42:27 2014
    Raid Level : raid5
    Array Size : 7814034432 (7452.04 GiB 8001.57 GB)
    Used Dev Size : 3907017216 (3726.02 GiB 4000.79 GB)
    Raid Devices : 3
    Total Devices : 3
    Persistence : Superblock is persistent


    Update Time : Fri Aug 22 16:04:04 2014
    State : clean
    Active Devices : 3
    Working Devices : 3
    Failed Devices : 0
    Spare Devices : 0


    Layout : left-symmetric
    Chunk Size : 512K


    Name : G54Vault:UltraNAS (local to host G54Vault)
    UUID : e712089f:c058a280:52ab67ae:7b6e1f45
    Events : 36


    Number Major Minor RaidDevice State
    0 8 0 0 active sync /dev/sda
    1 8 16 1 active sync /dev/sdb
    2 8 32 2 active sync /dev/sdc

  • Erm... on what kind of hard drive is your OS installed?


    Greetings
    David

    "Well... lately this forum has become support for everything except omv" [...] "And is like someone is banning Google from their browsers"


    Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.

    Upload Logfile via WebGUI/CLI
    #openmediavault on freenode IRC | German & English | GMT+1
    Absolutely no Support via PM!

  • So its a normal 2,5" hdd?


    Are you maybe using a custom kernel? I had someone on the IRC just an hour ago who had the exact same problem which we nailed down to a custom kernel which didn't had support for ACL enabled.


    Greetings
    David

    "Well... lately this forum has become support for everything except omv" [...] "And is like someone is banning Google from their browsers"


    Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.

    Upload Logfile via WebGUI/CLI
    #openmediavault on freenode IRC | German & English | GMT+1
    Absolutely no Support via PM!

  • Try mkdir /mnt/test101 && mount -t ext4 /dev/md127 /mnt/test101 if it's an ext4 filesystem.


    not smart enough to do that!


    Oh its not that hard... about ten commands which are just copy&paste :P


    Greetings
    David

    "Well... lately this forum has become support for everything except omv" [...] "And is like someone is banning Google from their browsers"


    Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.

    Upload Logfile via WebGUI/CLI
    #openmediavault on freenode IRC | German & English | GMT+1
    Absolutely no Support via PM!

  • This is what I get:


    Code
    mkdir /mnt/test101 && mount -t ext4 /dev/md127 /mnt/test101
    mount: wrong fs type, bad option, bad superblock on /dev/md127,
           missing codepage or helper program, or other error
           In some cases useful info is found in syslog - try
           dmesg | tail  or so
    • Offizieller Beitrag

    How about: fsck.ext4 /dev/md127

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.4 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


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


    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!

  • fsck.ext4 /dev/md127 produces:


    Error reading block 1953529856 (Invalid argument). Ignore error<y>? cancelled!


    UltraNAS: Invalid argument while reading block 1953529856


    UltraNAS: Invalid argument reading journal superblock


    fsck.ext4: Invalid argument while checking ext3 journal for UltraNAS

  • Are you sure its a ext4 filesystem?


    Greetings
    David

    "Well... lately this forum has become support for everything except omv" [...] "And is like someone is banning Google from their browsers"


    Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.

    Upload Logfile via WebGUI/CLI
    #openmediavault on freenode IRC | German & English | GMT+1
    Absolutely no Support via PM!

  • fdisk -l /dev/md127


    Greetings
    David

    "Well... lately this forum has become support for everything except omv" [...] "And is like someone is banning Google from their browsers"


    Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.

    Upload Logfile via WebGUI/CLI
    #openmediavault on freenode IRC | German & English | GMT+1
    Absolutely no Support via PM!

    • Offizieller Beitrag

    and blkid

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.4 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


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


    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!

  • FDISK:


    and BLKID

    Code
    blkid
    /dev/sdb: UUID="e712089f-c058-a280-52ab-67ae7b6e1f45" LABEL="G54Vault:UltraNAS" TYPE="linux_raid_member"
    /dev/sdc: UUID="e712089f-c058-a280-52ab-67ae7b6e1f45" LABEL="G54Vault:UltraNAS" TYPE="linux_raid_member"
    /dev/sda: UUID="e712089f-c058-a280-52ab-67ae7b6e1f45" LABEL="G54Vault:UltraNAS" TYPE="linux_raid_member"
    /dev/md127: LABEL="UltraNAS" UUID="5144add1-94fd-4eff-8c54-23ca6309ec05" TYPE="ext4"
    /dev/sdd1: UUID="b315dd3f-c7f6-435f-9f30-e0c5912cf74e" TYPE="ext4"
    /dev/sdd5: UUID="bce1c064-7c8b-4435-95ec-562b64fb08ec" TYPE="swap"
    • Offizieller Beitrag

    It is definitely ext4. Something is damaged though. Did it ask you to force a rewrite? You should say yes.

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.4 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


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


    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!

Jetzt mitmachen!

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