Posts by Sergio

    xfs_growfs /media/12f7f110-46e2-4b4f-a60f-f60bb8e3161e
    meta-data=/dev/sdh1              isize=256    agcount=4, agsize=61047597 blks
             =                       sectsz=512   attr=2
    data     =                       bsize=4096   blocks=244190385, imaxpct=25
             =                       sunit=0      swidth=0 blks
    naming   =version 2              bsize=4096   ascii-ci=0
    log      =internal               bsize=4096   blocks=119233, version=2
             =                       sectsz=512   sunit=0 blks, lazy-count=1
    realtime =none                   extsz=4096   blocks=0, rtextents=0

    And I can't understand anything about this. :D

    The new disk is SDH

    - expand the filesystem on new drive to use all of the space
    - reboot into OMV. no changes to snapraid needed because of OMV using uuids (it thinks the same drive is there)

    Aaron, I've done like this, but OMV still doesn't detect the new FS size. In disks, it correctly shows the disk as 1.82TB, but in filesystems it's showing data from the old disk aka 931.06GB.
    Is there something that can be done before deleting the fs and going the Fix method?

    <X:evil: Ahah... I wouldn't ever rely on you!

    I'll do the clone way and always keeping the old disk, but in case of a disk failure, I wouldn't had any options.
    It should be complete procedure instructions there in the OMV forum, for those things.

    And I guess disk replacement could be automated in the snapraid plugin. Mmmm...

    So for recovering a lost data drive, the procedure should be replacing the disk and then directly doing a Fix. The only requirement should be naming the device the same as the old. And it should even recover the AUFS stuff, right?
    What I don't understand is how one could remove the old drive (by only unchecking) and then creating the same name in the plugin gui.

    Men, you'r the guy. I'm currently using this procedure to recover an old W2003 server RAID that crashed, and never thought applying that in my house. I use partedmagic, so all tools are already in the same package. The only problem could me missing the target drive.

    Ahahah... Time zones rules. Hello Aaron.

    I removed the 1st parity drive, deleted the parity-2.snapraid on the 2nd parity drive and now I'm syncing.

    For your instructions... I have one doubt. If I go to the old drive I want to replace and uncheck the "data", what I'm supposed to do with the new drive? Also, that drive contains the shared folder for AUFS.
    It shouldn't be better to clone all the data in the new drive and then replace the uuid in the snapraid file? I suppose that for AUFS I should remove first the D1 share entry point and then share the one on the new drive. But I don't know what to do with the "storage" share.
    Can I place this on another drive?

    As for the snapraid manual... doesn't the plugin allow disk replacement? I'm forced to do cli commands

    The above procedure ended with a second parity drive with the parity file named something like parity-2.snapraid.
    What I noticed is that in the old parity drive there's a second parity file with a different name.

    There's no one in the forum that knows how to replace snapraid disks on Openmediavault?

    I currently have two data disk that are so old that need replacement and the parity drive it's almost full. So I bought two disks, one 4Tb for parity and one 2tb for data.
    What I want is to replace the parity with the new 4TB, then replace the first data drive with the new 2tb and then recycle the "old" 2tb parity drive for the second old data drive.
    All of this under a AUFS pool.

    Any suggestions on the correct way of doing that?

    I'm currently replacing the parity drive. I attached the 4TB drive and added to the array as a new parity+content, and then launched a sync. As it complained about a totally empty content file y executed the suggested command to force sync from cli. then I suppose that I'll remove the old parity disk from the Snapraid gui and launch sync again.

    Hello SubZero, I've been out today.
    I still want to make sure that the zfs scripts where updated with the reinstall, but other than that, seems that all is right and correctly running.
    Thank you so much for your help! May the magic kings bring you some nice presents today! :thumbsup:

    I uninstalled teh ZFS plugin and reinstalled again. It showed some errors, I could read something like "there's no zfs-mount" file present, but I could not copy-paste anything from the status window in this omv v2, as it's self refreshing every 10 seconds and it prevents scrolling or even select all and copy.

    The plugin seems to be at least partially installed and I managed to import my pool. Then I could restore my settings backup for emby from the ZFS pool.
    I doubt it's correctly functioning, as it has some latency while browsing the directories (halts for 5-10sec while issuing ls) and there are no zfs scripts in /etc/init.d

    Also, now I can access to omv gui with chrome, only shows the omv logo. Cleaning temp files/cache or issuing Ctrl-F5 does nothing. I'm forced to use Edge.
    Oh, god... messing with updates still gets crappy.

    phpVirtualbox is running. It shows my machines unaccessible.

    ZFS upgraded to v2, but as it showed so many insserv loop errors I thought the installation was reverted and deleted the scripts.
    Is there any way of uninstalling and clean install ZFS while recovering my pool?

    I did reboot.
    Now some packages appeared in update manager, ZFS is one of them. I'm updating (did not put the scripts back)
    I hope ZFS update goes well and it puts those or newer scripts in place.

    EDIT: Nah! It showed ZFS errors but I didn't have time to read it as the status window closed itself. :(

    Yeah. Not a cache problem but owncloud plugin.
    It got fixed with Aaron solution in this post

    Now to the new problem:

    That may be my machines missing as they where hosted at the ZFS array.

    I tried again and it succeed, but now, after the login screen I get this:


    Error #0:exception 'Exception' with message 'Failed to open file 'js/omv/form/field/CertificateComboBox.js'' in /usr/share/php/openmediavault/ trace:#0 /usr/share/php/openmediavault/ OMVHtmlPageAbstract->scanFiles('js/omv/form/fie...', Array)#1 /usr/share/php/openmediavault/ OMVHtmlPageAbstract->scanFiles('js/omv/module/a...', Array)#2 /usr/share/php/openmediavault/ OMVHtmlPageAbstract->scanDir('js/omv/module/a...', Array, true)#3 /usr/share/php/openmediavault/ OMVHtmlPageAbstract->scanDir('js/omv/module/a...', Array, true)#4 /usr/share/php/openmediavault/ OMVHtmlPageAbstract->scanDir('js/omv/module/a...', Array, true)#5 /usr/share/php/openmediavault/ OMVControlPanel->getJavascriptIncludes()#6 /var/www/openmediavault/index.php(36): OMVHtmlPageAbstract->render()#7 {main}

    I don't know if it failed. The OMV page has been failing all the morning: