Beiträge von Luxo

    Is there any way to remove the reference to the seventh drive that it keeps looking for? That expansion failed after only a few seconds so it never did expand to that space.

    Code
    root@openmediavault:~# mount -t ext4 /dev/md127 /media/test
    mount: wrong fs type, bad option, bad superblock on /dev/md127,
           missing codepage or helper program, or other error
           (could this be the IDE device where you in fact use
           ide-scsi so that sr0 or sda or so is needed?)
           In some cases useful info is found in syslog - try
           dmesg | tail  or so

    root@openmediavault:~# mkdir -p /media/test
    root@openmediavault:~# mount /dev/md127 /media/test
    mount: you must specify the filesystem type
    root@openmediavault:~#

    Waited a long time after this and it still fails to mount.


    Is the rebuild finished when the RAID shows up in the GUI? After running the CLI commands it finishes by saying that 6 of 7 are completed. Then the RAID is listed in the GUI. It fails when I try to mount it and I have to reboot and start over. Is it possible to make the system forget the failed attempt to add drive 7?

    Code
    root@openmediavault:~# cat /proc/mdstat
    Personalities : [raid6] [raid5] [raid4]
    md127 : inactive sdf[0] sdg[5] sdd[4] sdc[3] sdb[2] sda[1]
          11720301072 blocks super 1.2
    
    
    unused devices: <none>



    Code
    root@openmediavault:~# blkid
    /dev/sda: UUID="161d27f1-6d6b-5b9b-925d-630ad00256e6" UUID_SUB="81f2c8c2-297e-be                                             0f-5775-9603ebcb88fa" LABEL="openmediavault:Pool" TYPE="linux_raid_member"
    /dev/sdb: UUID="161d27f1-6d6b-5b9b-925d-630ad00256e6" UUID_SUB="a94506be-8b62-af                                             4a-79db-5e8422057948" LABEL="openmediavault:Pool" TYPE="linux_raid_member"
    /dev/sdd: UUID="161d27f1-6d6b-5b9b-925d-630ad00256e6" UUID_SUB="e7e608d9-2085-5c                                             ac-8f60-8c75a2134be9" LABEL="openmediavault:Pool" TYPE="linux_raid_member"
    /dev/sdc: UUID="161d27f1-6d6b-5b9b-925d-630ad00256e6" UUID_SUB="03ffbb2d-5203-f3                                             4c-d217-bf5231ac331e" LABEL="openmediavault:Pool" TYPE="linux_raid_member"
    /dev/sde1: UUID="61341bc8-96ea-4048-b6b6-cd2e4786133d" TYPE="ext4"
    /dev/sde5: UUID="b8330aef-aede-45bd-b288-7ef0da62d7ce" TYPE="swap"
    /dev/sdf: UUID="161d27f1-6d6b-5b9b-925d-630ad00256e6" UUID_SUB="bc580f54-8994-47                                             ad-c653-9582a35a3927" LABEL="openmediavault:Pool" TYPE="linux_raid_member"
    /dev/sdg: UUID="161d27f1-6d6b-5b9b-925d-630ad00256e6" UUID_SUB="18ede836-ad14-2f                                             a1-caf3-e561c5403093" LABEL="openmediavault:Pool" TYPE="linux_raid_member"

    Best support on the net here!




    Since I have removed the seventh drive that I was trying to add and shape what should I do next? Adding that drive caused the entire failure.


    When should I mount the filesystem? The RAID is currently marked clean, degraded with the missing drive #7.

    Code
    Personalities : [raid6] [raid5] [raid4]
     md127 : inactive sdf[0] sdg[5] sdd[4] sdc[3] sdb[2] sda[1]
     11720301072 blocks super 1.2
    
    
     unused devices: <none>


    Code
    /dev/sda: UUID="161d27f1-6d6b-5b9b-925d-630ad00256e6" UUID_SUB="81f2c8c2-297e-be0f-5775-9603ebcb88fa" LABEL="openmediavault:Pool" TYPE="linux_raid_member"
    /dev/sdb: UUID="161d27f1-6d6b-5b9b-925d-630ad00256e6" UUID_SUB="a94506be-8b62-af4a-79db-5e8422057948" LABEL="openmediavault:Pool" TYPE="linux_raid_member"
    /dev/sdd: UUID="161d27f1-6d6b-5b9b-925d-630ad00256e6" UUID_SUB="e7e608d9-2085-5cac-8f60-8c75a2134be9" LABEL="openmediavault:Pool" TYPE="linux_raid_member"
    /dev/sdc: UUID="161d27f1-6d6b-5b9b-925d-630ad00256e6" UUID_SUB="03ffbb2d-5203-f34c-d217-bf5231ac331e" LABEL="openmediavault:Pool" TYPE="linux_raid_member"
    /dev/sde1: UUID="61341bc8-96ea-4048-b6b6-cd2e4786133d" TYPE="ext4"
    /dev/sde5: UUID="b8330aef-aede-45bd-b288-7ef0da62d7ce" TYPE="swap"
    /dev/sdf: UUID="161d27f1-6d6b-5b9b-925d-630ad00256e6" UUID_SUB="bc580f54-8994-47ad-c653-9582a35a3927" LABEL="openmediavault:Pool" TYPE="linux_raid_member"
    /dev/sdg: UUID="161d27f1-6d6b-5b9b-925d-630ad00256e6" UUID_SUB="18ede836-ad14-2fa1-caf3-e561c5403093" LABEL="openmediavault:Pool" TYPE="linux_raid_member"


    I added a new drive to my RAID 5. The grow process was successful after 12 hours and then the resize went well.
    Next I added another drive to repeat the same process. The drive was recognized and the grow function started but
    soon threw a communication error with no details. At this point the system was frozen and non-responsive from CLI or GUI.


    After a hard boot It tried to recover the journal (I don't know if FSCK was successful) and my RAID has now disappeared.




    I have disconnected the new drive that failed to grow and the system will boot but the pool with 6TB of data is missing.


    Expert advice is welcomed.


    Personalities : [raid6] [raid5] [raid4]
    md127 : inactive sdf[0] sdg[5] sdd[4] sdc[3] sdb[2] sda[1]
    11720301072 blocks super 1.2


    unused devices: <none>

    It can be difficult to get Asset UPnP configured to scan the music folder on the OMV NAS. The instructions given on the Asset forum to set the path have not worked for several people I have seen seeking help, including me.


    The path must include the UUID of the shared media folder in OMV.
    e.g.

    Code
    /media/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/Music


    xxx= the UUID you will find in your config.xml by searching for "media"

    Clonezilla was not able to create a bootable SSD from my thumbdrive. So a fresh install and reconfiguration is working great now.


    The issue with getting Asset UPnP to scan the music directory has also been solved. For those who are interested in this terrific plugin I have posted the details here Asset UPNP
    This has been tricky for myself and others with their music on NAS.

    Thank you for the quick reply!


    How do I import the original config.xml to the fresh install?


    I could use some command line assistance in saving the original file which I have on my thumbdrive and writing it to my new install on the SSD.


    Actually my new install on the SSD is running well after I manually configured it except for one thing. I am running a plugin, Asset UPnP. I had a great deal of difficulty getting it configured to scan my music folder on the original thumbdrive installation. In the Asset configuration I had to include the drive UUID in the path to the music folder and finally got it to scan. On the new install the same method is not working. I believe the UUID changed in the new install but even that new number is not working to satisfy the path.


    If I import my original config.xml will there be a UUID conflict?


    I am very close to making this work if I can get the path sorted in Asset UPnP then I am done.

    I have been using Asset now for a while and it is very good in conjunction with BubbleUPnP.
    The Internet radio functionality with the paid version is mostly useless, almost never loads a station. Otherwise it is the best I have tried. Much better than the MiniDNLA plugin currently available for OMV. 12% lower CPU load than MiniDLNA.

    I have been testing OMV on a USB stick with good success managing 14TB. Now I would like to permanently move my OS to an SSD from the thumbdrive.


    I have cloned with Clonezilla but the SSD does not finish booting.


    There does not seem to be a way of moving my config to a new install. What is the best practice here?

    Thanks for the help. Got it working. The only problem I had was Chrome won't load the config page. Had to use IExplorer from windows.


    Curious how Asset UPNP has worked out for you. Did you test any others?