Posts by nomax

    Just checked - /dev/sdb seems to be already removed from the array, could it be that mdadm has done that just by itself? Would it be safe now to physically remove the faulty drive and connect the new one?


    If mdadm doesn't report the array as stopped the second command will report the array as busy :)


    /dev/sdb is that the drive with the bad sectors

    Yes it is. It is the one that is missing in the webinterface (under RAID management).


    Can I just remove the faulty one, add the functioning one and start to grow the RAID/add to the array or is there anything else I need to do?

    did you stop it first as per my post

    Weird, I just tried it again, same sequence! Now it shows up in OMV - still as clean, degraded. I suspect I need to decouple the defective HDD now somehow?


    doesn't look like this did the trick - it considers them as 'busy'?


    Code
    root@openmediavault:~# mdadm --assemble --force --verbose /dev/md127 /dev/sda /dev/sdb /dev/sdc /dev/sdd /dev/sde
    mdadm: looking for devices for /dev/md127
    mdadm: /dev/sda is busy - skipping
    mdadm: /dev/sdb is busy - skipping
    mdadm: /dev/sdc is busy - skipping
    mdadm: /dev/sdd is busy - skipping
    mdadm: /dev/sde is busy - skipping
    root@openmediavault:~#

    Hi guys, problem is the following - my NAS is a Dell T20 server running currently 5x 2TBs disks in RAID5. This has been set up a while back with OMV4, running on an USB stick. In the last week I noticed a couple of issues (mainly I couldn't log into the webinterface) so I just restarted the server. Noting that there seemed to be some consistency issues on the filesystem (it was booting default to initramfs which I was able to fix with fsck). Indepedently, I had a look into my webinterface once it was back up online and could see that there were some issues with one of the HDDs (red alarm signal in SMART - having some bad sectors) and the RAID was graded as 'clean, degraded' - files were still accessible.


    So I did get a new HDD and wanted to replace it over the weekend - unfortunately there hit a power outage on Thursday/Friday and the system went off. Rebooting the machine the USB thumb drive seemed unreadable so I did set up a new OMV installation (v5) on a different thumb drive. After successfully setting it up I replaced the drive that was claimed to have bad sectors with a new one - unfortunately I do not see the RAID now in the webinterface. I thought software RAID would be hot swappable, especially because 4 drives are still operating fine, looks like that is now a bit of an issue...I have now put the old (bad sectors) HDD back in and seem to have issues to get the RAID back into active mode:


    Code
    root@openmediavault:~# cat /proc/mdstat Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
    md127 : inactive sdd[3] sda[0] sde[5] sdc[4]
    7813542240 blocks super 1.2
    unused devices: <none>

    This is the defective drive:

    And these are the ones that operate correctly:


    Now I am feeling a bit hopeless - I am not sure how to interpret this?


    Though it looks like OMV can still see all HDDs and correctly considers them being in a RAID:


    Code
    root@openmediavault:~# blkid
    /dev/sdf1: UUID="fe602a13-21c8-49b7-a9b0-de6c397bd6a9" TYPE="ext4" PARTUUID="ad5bf966-01"
    /dev/sdf5: UUID="83f6ba28-0283-47b2-98a4-f832ad8486c1" TYPE="swap" PARTUUID="ad5bf966-05"
    /dev/sde: UUID="7b1be9be-d75a-f1ec-6370-02de39001c58" UUID_SUB="70f0181e-be31-b75e-e78f-498a7379f630" LABEL="Nas:RAID5" TYPE="linux_raid_member"
    /dev/sda: UUID="7b1be9be-d75a-f1ec-6370-02de39001c58" UUID_SUB="c762fde1-9e8f-0b91-cca4-ab0c6ae35729" LABEL="Nas:RAID5" TYPE="linux_raid_member"
    /dev/sdc: UUID="7b1be9be-d75a-f1ec-6370-02de39001c58" UUID_SUB="e392ac97-159d-f386-b562-983e0ed8929a" LABEL="Nas:RAID5" TYPE="linux_raid_member"
    /dev/sdd: UUID="7b1be9be-d75a-f1ec-6370-02de39001c58" UUID_SUB="9590adb7-f274-c2eb-b2f9-b5041dae9a1a" LABEL="Nas:RAID5" TYPE="linux_raid_member"
    /dev/sdb: UUID="7b1be9be-d75a-f1ec-6370-02de39001c58" UUID_SUB="82f55d04-1e52-1e01-6af8-d94b6c2aa6cf" LABEL="Nas:RAID5" TYPE="linux_raid_member"


    It says still active, but FAILED/not started - does anyone have an idea here how to circumvent this maybe?


    Code
    root@openmediavault:~# cat /sys/block/md127/md/array_state
    inactive


    Thanks in advance!!

    All,


    I am struggeling to get OMV installed onto a Dell T20. I did run through the installation (from stick to stick) but I come out afterwards, when I want to boot the USB thumbdrive to a Busybox shell.


    The first installation has been successful, the HDD were disconnected. I configured the system subsequently and upgraded Grub as well (through OMV package manager add in) but however, got out to the Busybox shell again. In the following installation attempts I kept the HDDs connected, but after the installation finishes, I am ending up in a Busybox shel which means for my understanding, that Grub has issues.


    The next attemp I will undertake is to install with HDDs disconnected and update/upgrade all packages first before reconnecting all drives...otherwise I would not know what to do.


    Did anyone of you encounter similar issues like that?


    Thx!!





    Sent from my iPad using Tapatalk

    Hi guys,


    sorry for the delay in getting back to you. To answer your queries;


    Are your other machines W10?
    Can you ping the ip of omv and get a reply from your windows machine?
    Have you tried from explorer/file manager, select network then in the location box type the ip address of omv?


    >> Yes, all machines are running W10. Yes, I can confirm that a ping from the other machines to the OMV box is successful. Furthermore I can see both machines in the DHCP clients sections of the main router. No issues with this one.
    I tried from explorer/file manager to access both IP and name of the box ('OPENMEIDAVAULT") but no luck - I always get the message that it's not possible to access \\192.168.0.219 with error code 0x80004005 (Unknown error). Within the OMV control panel I can see that Samba is activated and running (both dots are green).



    Do you have the same workgroup name on server (general settings page for SMB/CIFS) and clients?


    Also look here: https://forum.openmediavault.o…res-not-visible/?pageNo=1


    >> That did the trick!! Worked!!




    geaves wrote:

    Do you have the same workgroup name on server (general settings page for SMB/CIFS) and clients?


    Also look here: https://forum.openmediavault.o…res-not-visible/?pageNo=1

    That was going to be my next question :)


    Yes, done already.




    Very big thanks for collecting here all the different methods to be act on!


    In my case, the change of the FAKE start-stop-daemon did the trick. Now I will perform a backup of the stick and then afterwards run an apt-get install dpkg --reinstall in order to fix any issues that may have happened during the installation.


    Anyone know a bit more about this problem in detail? seems still a bit weird that a fake daemon is run and set up instead of just highlighting broken packages.

    Hi guys,


    sorry for the delay in getting back to you. To answer your queries;


    Are your other machines W10?
    Can you ping the ip of omv and get a reply from your windows machine?
    Have you tried from explorer/file manager, select network then in the location box type the ip address of omv?


    >> Yes, all machines are running W10. Yes, I can confirm that a ping from the other machines to the OMV box is successful. Furthermore I can see both machines in the DHCP clients sections of the main router. No issues with this one.
    I tried from explorer/file manager to access both IP and name of the box ('OPENMEIDAVAULT") but no luck - I always get the message that it's not possible to access \\192.168.0.219 with error code 0x80004005 (Unknown error). Within the OMV control panel I can see that Samba is activated and running (both dots are green).



    Do you have the same workgroup name on server (general settings page for SMB/CIFS) and clients?


    Also look here: https://forum.openmediavault.o…res-not-visible/?pageNo=1


    >> That did the trick!! Worked!!




    geaves wrote:

    Do you have the same workgroup name on server (general settings page for SMB/CIFS) and clients?


    Also look here: https://forum.openmediavault.o…res-not-visible/?pageNo=1

    That was going to be my next question :)
    [/quote]Yes, done already.

    So far, I have configured a user in order to access the share drives and have provided via ACLs the privs to that user.


    Furthermore what makes the cookie crumble for me is that I can not even see the OMV server/NAS within the network shares view. My rationale is, if it was a problem with access privileges I would at least be able to see the machine on the network but get error messages when it comes to connecting to the shares.


    Or am I far off the track?

    Hi team,


    I have upgraded to OMV 3.x on a Dell T20 microserver and installed OMV on a USB thumbdrive.


    So far, I can reach the admin console via the webinterface and make all necessary setting but even after activating samba multiple times, setting up shares and passing them on to the Samba plugin in OMV, I still can't access the shares from the other computers within my home network.


    In the dashboard section I can see that the plugin is active and running.


    I have assigned DHCP to the NAS/OMV but the IP is constantly leased on 192.168.0.219 (as I had issued with DNS resolving and apt-get update while I assigned a fixed IP).


    Does anyone have an idea what the problem could be or what else i could try? Every time when I try to access the samba share via network folder in windows I get an error message that the source is not reachable.


    Thanks for help and guidance on this, very much appreciated. Feel like I am getting out of ideas what to do.

    Du koenntest das remote share plugin auf OMV aufsetzen, mounten und dann per SSH aufschalten (geht auch durch das webinterface).



    Sent from my iPhone using Tapatalk

    No, I have IPv6 disabled and operate only IPv4 in my home network. Currently it seems like I can barely get a connection outside.
    THe main problem that I encounter is the DNS resolve issue - but I have configured my DSN (basically my router who does DNS) in the interfaces tab.

    Hi guys, I just changed the settings for IPv4 from static to dynamic, apparently now it works to resolve DNS. Any ideas why this appears to be different?


    Thanks!

    Report to the syncthing team that their repo seems slow. Disable the sync repo in omv-extras until then.


    I tried to disable it in the repositories page, but there seems to be a problem with deactivating it.


    Now I seem to encounter the problem that I get errors that hosts could not be resolved. I guess my prob could be rather DNS related?



    Sent from my iPhone using Tapatalk