Beiträge von Mikky

  • Problem creating ZFS striped mirror (4 HDD) OMV 6

    I cannot expand the pool by adding another mirrored pair to it. It will only show one dev although two are checked (see second pool/second pool line).

    I believe my procedure is correct:

    install OMV6

    Install updates

    Install OMV extras

    uncheck backports/apt clean

    Install proxmox and reboot

    Remove non-proxmox kernels

    Install ZFS plugin

    Create mirror (2 dev)

    Expand pool with another 2 dev mirror. Only one dev listed after checkmarks.

  • Problem creating ZFS striped mirror (4 HDD) OMV 6

    I have 2 small NAS’s that were both running OMV 5 ZFS (w/pve kernel). One NAS was a backup using a 2 HDD mirror, the other was a 4 HDD striped mirror. Both were created in the GUI and worked perfectly.


    After using the upgrade command to test OMV 6 for a few weeks for the 2 HDD mirror, it was wiped and a fresh install of OMV 6 was performed with ZFS (w/pve kernel); no issues to date. The mirror was created in the GUI.


    The second NAS was wiped and fresh OMV 6 install was performed exactly as the above. No errors were seen during any of the processes (Kernel plugin, non-proxmox removal, ZFS, Management updates, etc.)


    Issue:


    I can create the first mirror in the GUI by selecting 2 of the 4 Hdds, without a problem. When I check off on 2 HDDs they both are displayed and I click save; mirror created! The issue begins when expanding the mirror: I can see the 2 remaining drives and check off on them but the Devices line only displays one drive. Clicking save produces an error message stating I need to select more than one drive. I verify and yes both HDDs are in fact checked but only one is displayed. I have reinstalled OMV 6 twice, after wiping the HDDs as well as I have tried only attaching 2 HDDs at a time with no success. ZFS was also uninstalled and reinstalled, again no success.


    I am at a loss as to what I am doing incorrectly. I am at work, when I am at home in 4 hours I can take screenshots if requested. Any advice would be greatly appreciated. Thank you.


    Screen grabs (second pool and second pool line displays the above issue)

  • Raid 10 failure to mount, root in emergency mode

    Although GParted displayed no partitions on any drive other than the USB boot, you put me right into the BIOS! The boot priority list had all HDDs prioritized over the USB boot. My bad, I should have verified after installing the new HDDs. I have corrected that error and I am going to attempt RAID 10 one final time. The bug was me?!

  • Raid 10 failure to mount, root in emergency mode

    I'm sorry, yes all HDDs connected through SATA. To repeat:


    After the RAID10 finished syncing everything looked normal. Then I created a file system and when I attempted the mount the error I posted above was noted (GUI). I turned on the console and noticed the root was in emergency mode and it was not when I began the syncing. I rebooted and it stayed in emergency mode until I broke the array down, then upon reboot it everything was normal. Again, I reproduced this two times (RAID10) with complete fresh installs of OMV and all the updates. I did NOT reinstall OMV when I broke the second array down and mirrored just 2 drives, mounted it and I was good to go (still am, reboots and all). This is why I am thinking a bug.


    ps - is somehow the part of the boot image getting onto the HDDs during the RAID10 syncing?

  • Raid 10 failure to mount, root in emergency mode

    I am going to look into UrBackup, I am licensed for Acronis for the next year so I can play around with UrBackup in the meantime.


    I was not aware that I could download a clean W10 and still maintain the same license - thank you for that!


    I actually enjoy the learning curve. I was going to go with SnapRaid and Mergerfs but finding my way around the root environment is like Helen Keller learning to code. I figured raid 10 would passify my needs as I begin my journey into OMV/Linux.


    As I write this all three computers in the household are all connected to OMV. OMV running like a champ, although in mirror mode. I am wondering if there may be a bug in the software with raid 10? .... oh well:


    Thanks for all your help! I will begin reading the guide tonight!

  • Raid 10 failure to mount, root in emergency mode

    Yes, the computer is homebuilt and had no issues as it was a Windows 7 machine before this. Wife is a teacher and with the hybrid system I had to build her a Windows 10 machine. It's imperative that machine stays running so I keep spare parts on hand for an emergency. Thus the reason to keep images of the drive. My 14 yr old boy figured out how to upgrade from Win 7 to Win 10 for free and has large cache of games. If that machine goes down it would be a nightmare since Win 7 is no longer supported. Simpler to keep an image of his disk also.


    My novice opinion was to gain the capacity of 2 drives in raid 0 with the mirroring security of raid 1. USB backup from there.


    Thanks for the link, it's all bookmarked and I will begin reading it all soon enough.

  • Raid 10 failure to mount, root in emergency mode

    RAID SETUP: In reality I have been wanting to try a server build for a while, hobby, and Linux has peaked my interest for some time as I am becoming more disgruntled with our "big tech". A move to Ubuntu in a dual boot is coming soon. BTW, I was a DOS user back in the 1980's before windows. I am COMP TIA A+ certified, for whatever that is worth - lower than whale sh*t technician?.


    I have OMV installed to a 32gb USB flash drive. All HDDs are 2 TB WD's and all are 64mb cache CMR although 2 are designated NAS and 2 are not. Intel i5 and 8gb RAM. I have the flash memory plug in and have altered the fstab per the instructions - was never a problem in stripe or mirror mode.


    I did not reinstall OMV after wiping the drives and mirroring 2 of them, the root is fine. The emergency mode seemed to coincide with the issue of RAID10 as noted above.


    Thanks for assisiting geaves.

  • Raid 10 failure to mount, root in emergency mode

    Hello and let me introduce myself as saying I am as newbie as they come. A few weeks back I decided to try my luck with turning an old computer into a server. After researching for some time (youtube and net) I decided on OMV. My goal was to be able to transfer disk images of our families computers (Acronis) and place them on the network drive and use a USB backup from there. Originally I ran a mirror but a recent purchase of 2 more HDDs gave me the opportunity for RAID 10. I recently completed a fresh install of OMV 5.x and with all drives wiped and proceeded to create the array. Once competed the console shown it was running in 'emergency mode' and the OMV GUI would not mount the array and produced an error dialog. I wiped all drives and began another fresh install of OMV 5.x and attempted once again to create the array. The same result was noted. I have gone back to the mirror (using the new drives, old drives prior) with no problems. Curiosity is getting the best of me: Is it my lack of knowledge or something else? I am posting the error dialog given and if anyone would like to give an opinion including "you suck, go back to MS" I am ok with that :P. Thanks to all who post here as you were a big help when I encountered the Realtek r8168 LAN issue.


    Raid 10 error dialog:


    Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; omv-salt deploy run --no-color fstab 2>&1' with exit code '1': debian: ---------- ID: create_filesystem_mountpoint_0eda26a6-c63e-423e-8673-e43f1efb70a3 Function: file.accumulated Result: True Comment: Accumulator create_filesystem_mountpoint_0eda26a6-c63e-423e-8673-e43f1efb70a3 for file /etc/fstab was charged by text Started: 04:58:18.000968 Duration: 0.672 ms Changes: ---------- ID: mount_filesystem_mountpoint_0eda26a6-c63e-423e-8673-e43f1efb70a3 Function: mount.mounted Name: /srv/dev-disk-by-uuid-dd0964ea-69aa-4796-952e-09db61e0f5a3 Result: False Comment: mount: /srv/dev-disk-by-uuid-dd0964ea-69aa-4796-952e-09db61e0f5a3: mount(2) system call failed: Structure needs cleaning. Started: 04:58:18.002188 Duration: 126.166 ms Changes: ---------- ID: append_fstab_entries Function: file.blockreplace Name: /etc/fstab Result: True Comment: No changes needed to be made Started: 04:58:18.130535 Duration: 11.563 ms Changes: Summary for debian ------------ Succeeded: 2 Failed: 1 ------------ Total states run: 3 Total run time: 138.401 ms



    Error #0: OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; omv-salt deploy run --no-color fstab 2>&1' with exit code '1': debian: ---------- ID: create_filesystem_mountpoint_0eda26a6-c63e-423e-8673-e43f1efb70a3 Function: file.accumulated Result: True Comment: Accumulator create_filesystem_mountpoint_0eda26a6-c63e-423e-8673-e43f1efb70a3 for file /etc/fstab was charged by text Started: 04:58:18.000968 Duration: 0.672 ms Changes: ---------- ID: mount_filesystem_mountpoint_0eda26a6-c63e-423e-8673-e43f1efb70a3 Function: mount.mounted Name: /srv/dev-disk-by-uuid-dd0964ea-69aa-4796-952e-09db61e0f5a3 Result: False Comment: mount: /srv/dev-disk-by-uuid-dd0964ea-69aa-4796-952e-09db61e0f5a3: mount(2) system call failed: Structure needs cleaning. Started: 04:58:18.002188 Duration: 126.166 ms Changes: ---------- ID: append_fstab_entries Function: file.blockreplace Name: /etc/fstab Result: True Comment: No changes needed to be made Started: 04:58:18.130535 Duration: 11.563 ms Changes: Summary for debian ------------ Succeeded: 2 Failed: 1 ------------ Total states run: 3 Total run time: 138.401 ms in /usr/share/php/openmediavault/system/process.inc:182 Stack trace: #0 /usr/share/php/openmediavault/engine/module/serviceabstract.inc(62): OMV\System\Process->execute() #1 /usr/share/openmediavault/engined/rpc/config.inc(167): OMV\Engine\Module\ServiceAbstract->deploy() #2 [internal function]: Engined\Rpc\Config->applyChanges(Array, Array) #3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array) #4 /usr/share/php/openmediavault/rpc/serviceabstract.inc(149): OMV\Rpc\ServiceAbstract->callMethod('applyChanges', Array, Array) #5 /usr/share/php/openmediavault/rpc/serviceabstract.inc(588): OMV\Rpc\ServiceAbstract->OMV\Rpc\{closure}('/tmp/bgstatuspc...', '/tmp/bgoutputWm...') #6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(159): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure)) #7 /usr/share/openmediavault/engined/rpc/config.inc(189): OMV\Rpc\ServiceAbstract->callMethodBg('applyChanges', Array, Array) #8 [internal function]: Engined\Rpc\Config->applyChangesBg(Array, Array) #9 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)