After updates getting RAID is Not working- closed

  • I have a raid 5 with 3 disks
    I did some updates and now after boot I have no raid


    tried doing " /proc/mdstat" and am getting /proc/mdstat: Permission denied


    Help?
    What now?

    • Offizieller Beitrag

    Sounds like mdadm isn't running. What is the output of:


    service mdadm status


    If it says it isn't running, try:


    service mdadm start


    What did you update?

    omv 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.10 | compose 7.1.2 | k8s 7.0-6 | 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!


  • I Updated all the updates here,
    I installed latest sickbeard (sickrage) using the /omv.sh method (the plugin that lets u install all the programs like cps and sickbeard)
    Before that (a few days) i tried to install virtual-box, but it failed and now when I run "upgrade" I get problems with virtualbox


    Edit:
    I get an error in the log that my shares are not accessible, and that my mysql is too full.
    I do not have any shared folders in omv admin (where I had a few) and I cannot access my smb shares (because they dont have access to shared folder (in omv main web screen)


    Another Edit:
    I installed virtualbox again and it installed correctly, I uploaded the syslog
    Edit:
    Since I can see my /media/5eb dir, my data is intact I just do not know how to reach it from the outside

    Code
    root@omv:/media/5eb927dd-91b5-4c42-9d37-ac34832a6384# ls /media/
    5eb927dd-91b5-4c42-9d37-ac34832a6384  backup  cdrom  cdrom0  floppy  floppy0
    root@omv:/media/5eb927dd-91b5-4c42-9d37-ac34832a6384# /proc/mdstat
    -bash: /proc/mdstat: Permission denied
    • Offizieller Beitrag

    Just noticed... You should be using this:


    cat /proc/mdstat


    Also, what is the output of:


    dpkg -l | grep openmediavault
    df -h

    omv 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.10 | compose 7.1.2 | k8s 7.0-6 | 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!

    • Offizieller Beitrag

    You have a floppy drive in your system?? :lol:


    I don't see anything wrong in syslog other than the raid array stopping. I assume the raid drives aren't plugged in usb ports? What is the output of:


    fdisk -l
    blkid
    cat /etc/mdadm/mdadm.conf

    omv 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.10 | compose 7.1.2 | k8s 7.0-6 | 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!

  • No floppy, why the question??



    blkid hangs for a long time

    • Offizieller Beitrag

    According to syslog, there is a floppy...


    If you have a raid array, there is no evidence of it. blkid would tell me more but since it is hanging, I would guess you have one or more drives failing or bad cables or bad motherboard (if the drives aren't connected by usb).

    omv 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.10 | compose 7.1.2 | k8s 7.0-6 | 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!

  • Code
    root@omv:~# blkid
    /dev/sda1: UUID="faa5130c-6167-40dc-91dd-763e8eaeeb76" TYPE="ext4" 
    /dev/sda5: UUID="0ec15acf-4503-42b0-8f4b-99be9135ecd5" TYPE="swap" 
    /dev/sdb1: UUID="7dbda842-31b7-80c6-ea9c-aac8e318eab2" LABEL="openmediavault:missing" TYPE="linux_raid_member" 
    /dev/sdd: UUID="7dbda842-31b7-80c6-ea9c-aac8e318eab2" LABEL="openmediavault:missing" TYPE="linux_raid_member" 
    /dev/sdc: UUID="7dbda842-31b7-80c6-ea9c-aac8e318eab2" LABEL="openmediavault:missing" TYPE="linux_raid_member" 
    root@omv:~#
    • Offizieller Beitrag

    Did you create the raid array in the OMV web interface? Strange that one drive is using a partition. You could try the following:


    Code
    mdadm --assemble --run --force /dev/md127 /dev/sdb1 /dev/sdc /dev/sdd


    I think blkid is taking a long time because of the floppy drive it thinks is there. You should disable the floppy controller (fdc) in the bios.

    omv 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.10 | compose 7.1.2 | k8s 7.0-6 | 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!

  • Raid was not created in omv but in cli

    Code
    root@omv:/media/5eb927dd-91b5-4c42-9d37-ac34832a6384# mdadm --assemble --run --force /dev/md127 /dev/sdb1 /dev/sdc /dev/sdd
    mdadm: /dev/md127 has been started with 2 drives (out of 3).


    Code
    root@omv:/media/5eb927dd-91b5-4c42-9d37-ac34832a6384# cat /proc/mdstat 
    Personalities : [raid6] [raid5] [raid4] 
    md127 : active raid5 sdb1[2] sdc[4]
          5860528128 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/2] [_UU]
    
    unused devices: <none>
    • Offizieller Beitrag

    Why did you create the array in cli? Looks like sdd is having problems. You should be able to access your array now though.

    omv 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.10 | compose 7.1.2 | k8s 7.0-6 | 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!

  • it did not work for me in web because I started with 2 disks only (degragaded)
    and there was no way to do that in web


    I can access my files, but not all of them, heck only a smal portion can be seen at all
    this is not good :(

    • Offizieller Beitrag

    If the array isn't rebuilding and your files aren't there, I am afraid there isn't much you can do other than try to recover them with photorec.

    omv 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.10 | compose 7.1.2 | k8s 7.0-6 | 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!

  • Ok, so to make a very long story shorter.


    After all this I rebooted my server, and took out the defective disk.
    The array said degrageted, and started to work. (2 disks)
    I was rejoiced.
    I thought I was in the clear, one disk down, but no biggie.


    I rebooted the server again, without backing my important data.
    It did not come up....
    apparently there were disk prooblems, that fsck needed to start fixing, and it would not start, (I got the message on a subsequent reboot, that it has not been run for 25 reboots and so it would run).


    Well, I finnaly managed to do a little fixing, (stopped in the middle of it because I did not know what it was doing exactly, and because it wanted me to do it manually, "yes","yes", "yes", "yes" - it gets tiresome.


    My raid actually came up and I copied a terra of stuff (documents, pictures, kids stuff in hebrew which is very hard to come by).
    and now when I boot it says I need to do ctrl+d to resume login or manual fcsk.


    I am thinking about reformatting the whole raid (now that my import stuff is safe - I can download movies, and tv shows later).
    What do you think? manual fixing or refromat?

  • It tells you that the drive you've removed is gone missing... thats all.


    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!

  • The degragaded was actually a blessing, because after that I was able to get my data.


    Do you think that running an fsck on a degraded raid 5 will show errors that are not there?
    So are you saying the errors I see are not real?

  • I'm onlx talking about the ctrl+d message, not about anything that fsck may show you.


    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 here is where I am at right now (and I do realize I get into stuff becuase I jump, instead of crawling, but this is how I learn).


    I bought a new drive, and put it in the machine,could not load the raid, because it wold not alow me so I said, f*** it, lets go with bruth force (not the best idea I know , but I am tired of this :) ).
    I wiped the drives in the omv console (physical disks), and added the drive in system (thinking if all the drives are wiped the raid will go away).


    Then I preceded to create a new raid 5 (using omv console). That took like 17 hours and now it reports that my raid is ok.
    But....


    1. in storage/file systems - I see device:n/a mounted:n/a ... and I cannot delete this line (which I figure is relevant to the old raid?), nor can I create a file system for the new raid.
    2. when I do " ls -la /media/", I still see directories "5eb927dd-91b5-4c42-9d37-ac34832a6384" (which is the old raid, where is it comming from?)

    Code
    root@omv:~# ls -la /media/
    total 24
    drwxr-xr-x  6 root  root  4096 Mar 18 23:39 .
    drwxr-xr-x 30 root  root  4096 Jul 10 07:33 ..
    drwx------  6 root  root  4096 Jul  1 20:59 5eb927dd-91b5-4c42-9d37-ac34832a6384
    drwxr-xr-x  2 admin users 4096 Mar 18 23:39 backup
    lrwxrwxrwx  1 root  root     6 Dec  7  2013 cdrom -> cdrom0
    drwxr-xr-x  2 root  root  4096 Dec  7  2013 cdrom0
    lrwxrwxrwx  1 root  root     7 Dec  7  2013 floppy -> floppy0
    drwxr-xr-x  2 root  root  4096 Dec  7  2013 floppy0


    Code
    root@omv:~# ls -la /media/5eb927dd-91b5-4c42-9d37-ac34832a6384/
    total 24
    drwx------  6 root root 4096 Jul  1 20:59 .
    drwxr-xr-x  6 root root 4096 Mar 18 23:39 ..
    drwxr-xr-x  3 root root 4096 Jul  1 19:53 downloads
    drwxr-xr-x  5 root root 4096 Jul 11 12:24 general
    drwxrwxrwx 12 root root 4096 Jul  8 19:19 torrents
    drwx------  3 root root 4096 Jul  1 20:59 tv


    Edit - add data:

    Code
    root@omv:~# cat /proc/mdstat
    Personalities : [raid6] [raid5] [raid4]
    md0 : active raid5 sdb[0] sdd[2] sdc[1]
          5860528128 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/3] [UUU]
    
    
    unused devices: <none>




    Code
    root@omv:~# blkid
    /dev/sda1: UUID="faa5130c-6167-40dc-91dd-763e8eaeeb76" TYPE="ext4"
    /dev/sda5: UUID="0ec15acf-4503-42b0-8f4b-99be9135ecd5" TYPE="swap"
    /dev/sdb: UUID="c234f0e0-aa4a-7316-7bdd-b677b613572c" LABEL="omv:NewRaid" TYPE="linux_raid_member"
    /dev/sdc: UUID="c234f0e0-aa4a-7316-7bdd-b677b613572c" LABEL="omv:NewRaid" TYPE="linux_raid_member"
    /dev/md0: UUID="7dbda842-31b7-80c6-ea9c-aac8e318eab2" LABEL="openmediavault:missing" TYPE="linux_raid_member"
    /dev/sdd: UUID="c234f0e0-aa4a-7316-7bdd-b677b613572c" LABEL="omv:NewRaid" TYPE="linux_raid_member"

Jetzt mitmachen!

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