OMV on a Board with UEFI?

    • OMV 1.0

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • OMV on a Board with UEFI?

      Hi Folks,

      I hate UEFI. It's a f*cking mess!
      Sorry, I have to say that first.

      I've tried to install OMV with a USB-Stick (that's worked with a Board with a normal BIOS).
      I have set

      Fast Boot off
      Boot Mode: Legacy&UEFI
      The system seems to boot from the stick and says:
      "Reboot an select proper boot device."

      There is a point "Secure Boot" to set off under "Windows 8 Options".
      But when I disable it, Boot Mode switched to "UEFI" only. So I can't select the Stick in the Boot Menu.

      Can you explain me how I will get OMV on this masterpiece of modern hardware engenieering, please?
      Slowly and for a stupid, please.

      TIA
      Mierscheid
      OMV 2.1.25, Asus P5K, C2D 4300, 4 GB RAM, 1x Intel SSDA2CT04, 5x Seagate ST3000DM001-1CH1
      Pictures of my NAS (with Nanoxia HDD-Cages)
    • Try installing Debian Wheezy instead. Debian doesn't have a signed secure boot key but I have installed it on uefi boards. Once you have wheezy installed, installing OMV is easy.
      omv 4.0.14 arrakis | 64 bit | 4.13 backports kernel | omvextrasorg 4.1.1
      omv-extras.org plugins source code and issue tracker - github.com/OpenMediaVault-Plugin-Developers

      Please don't PM for support... Too many PMs!
    • Wait a second. I've got a strange output while I set the powermenagement of the HDDs. "not a unique object...". It's gone after the seceond try, but I decided to restart the system.
      Now, at the startup, OMV is checking the quotas.
      I set up quotas only at the RAID-Array, therfore...

      This will take a while, please be patient. ;)
      OMV 2.1.25, Asus P5K, C2D 4300, 4 GB RAM, 1x Intel SSDA2CT04, 5x Seagate ST3000DM001-1CH1
      Pictures of my NAS (with Nanoxia HDD-Cages)
    • Too sad, still gone.

      fdisk -l

      Source Code

      1. ...
      2. Disk /dev/sde: 3000.6 GB, 3000592982016 bytes
      3. 255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectors
      4. Units = sectors of 1 * 512 = 512 bytes
      5. Sector size (logical/physical): 512 bytes / 4096 bytes
      6. I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      7. Disk identifier: 0x00000000
      8. Device Boot Start End Blocks Id System
      9. /dev/sde1 1 4294967295 2147483647+ ee GPT
      10. Partition 1 does not start on physical sector boundary.
      11. WARNING: GPT (GUID Partition Table) detected on '/dev/sdf'! The util fdisk doesn't support GPT. Use GNU Parted.
      12. Disk /dev/sdf: 3000.6 GB, 3000592982016 bytes
      13. 255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectors
      14. Units = sectors of 1 * 512 = 512 bytes
      15. Sector size (logical/physical): 512 bytes / 4096 bytes
      16. I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      17. Disk identifier: 0x00000000
      18. Device Boot Start End Blocks Id System
      19. /dev/sdf1 1 4294967295 2147483647+ ee GPT
      20. Partition 1 does not start on physical sector boundary.
      Display All


      blkid:

      Source Code

      1. /dev/sda3: UUID="5a71893d-9098-4ccc-bbcf-8519e5d5a13a" TYPE="swap"
      2. /dev/sda1: UUID="8746-AD55" TYPE="vfat"
      3. /dev/sda2: UUID="55815ec0-944c-4049-ab74-61b0219851ed" TYPE="ext4"
      4. /dev/sdb1: LABEL="Medien3" UUID="c15f9afc-6c05-40d3-bb05-840bac43c9f8" TYPE="ext4"
      5. /dev/sdc1: LABEL="Medien1" UUID="a17632c2-23b3-4d60-a7ab-ca18b5b54cc7" TYPE="ext4"
      6. /dev/sdd1: LABEL="Medien2" UUID="ac210c2f-72b2-4a16-b7f0-3d9620067664" TYPE="ext4"


      cat /proc/mdstat:

      Source Code

      1. Personalities :
      2. unused devices: <none>
      OMV 2.1.25, Asus P5K, C2D 4300, 4 GB RAM, 1x Intel SSDA2CT04, 5x Seagate ST3000DM001-1CH1
      Pictures of my NAS (with Nanoxia HDD-Cages)
    • How did you create your raid? OMV doesn't use partitions when creating an array. I would try:

      mdadm --assemble /dev/md127 /dev/sd[ef]1 --verbose --force
      omv 4.0.14 arrakis | 64 bit | 4.13 backports kernel | omvextrasorg 4.1.1
      omv-extras.org plugins source code and issue tracker - github.com/OpenMediaVault-Plugin-Developers

      Please don't PM for support... Too many PMs!
    • I've created it with OMV. I also reinstalled OMV yesterday and the RAID was still fine.
      I installed a new Board/CPU and also OMV.

      Source Code

      1. root@NAS:~# mdadm --assemble /dev/md127 /dev/sd[ef]1 --verbose --force
      2. mdadm: looking for devices for /dev/md127
      3. mdadm: cannot open device /dev/sd[ef]1: No such file or directory
      4. mdadm: /dev/sd[ef]1 has no superblock - assembly aborted
      OMV 2.1.25, Asus P5K, C2D 4300, 4 GB RAM, 1x Intel SSDA2CT04, 5x Seagate ST3000DM001-1CH1
      Pictures of my NAS (with Nanoxia HDD-Cages)
    • You must not have wiped the drives before creating the array then. Try this:

      mdadm --assemble /dev/md127 /dev/sd[ef] --verbose --force
      omv 4.0.14 arrakis | 64 bit | 4.13 backports kernel | omvextrasorg 4.1.1
      omv-extras.org plugins source code and issue tracker - github.com/OpenMediaVault-Plugin-Developers

      Please don't PM for support... Too many PMs!
    • The disks where brandnew as I'd created the RAID.
      I'd had to erase all partitions in OMV, because the drives came of a external case with 4k-translation.

      Source Code

      1. mdadm: looking for devices for /dev/md127
      2. mdadm: Cannot assemble mbr metadata on /dev/sde
      3. mdadm: /dev/sde has no superblock - assembly aborted


      But... it's okay to delete them again, because there are no important data on them. Only a backup from a fresh installed PC.

      Let me delete them and create the RAID again overnight.
      OMV 2.1.25, Asus P5K, C2D 4300, 4 GB RAM, 1x Intel SSDA2CT04, 5x Seagate ST3000DM001-1CH1
      Pictures of my NAS (with Nanoxia HDD-Cages)
    • If you don't need to save data, I recommend doing the following first:

      Source Code

      1. mdadm --zero-superblock /dev/sde
      2. mdadm --zero-superblock /dev/sdf
      3. dd if=/dev/zero of=/dev/sde bs=512 count=10000
      4. dd if=/dev/zero of=/dev/sdf bs=512 count=10000
      omv 4.0.14 arrakis | 64 bit | 4.13 backports kernel | omvextrasorg 4.1.1
      omv-extras.org plugins source code and issue tracker - github.com/OpenMediaVault-Plugin-Developers

      Please don't PM for support... Too many PMs!
    • I've created a new RAID, no matter. But now it's gone, too.

      It was my fault. I was stupid and lazy:
      I wasn't sure about what I have choosen at the postfix-config, but the system-messages by mail doesn't work.
      Therefore, I reinstalled postifix, instead of editing the config file. :(
      After that, OMV shows me a "403 forbidden" at the webend.
      I reinstalled OMV: apt-get install --reinstall openmediavault
      Backend is working now, but the RAID is lost again!

      Followed your instructions again with the same results.

      But... have a look at /etc/mdadm/mdadm.conf:

      Source Code

      1. # mdadm.conf
      2. #
      3. # Please refer to mdadm.conf(5) for information about this file.
      4. #
      5. # by default, scan all partitions (/proc/partitions) for MD superblocks.
      6. # alternatively, specify devices to scan, using wildcards if desired.
      7. # Note, if no DEVICE line is present, then "DEVICE partitions" is assumed.
      8. # To avoid the auto-assembly of RAID devices a pattern that CAN'T match is
      9. # used if no RAID devices are configured.
      10. DEVICE partitions
      11. # auto-create devices with Debian standard permissions
      12. CREATE owner=root group=disk mode=0660 auto=yes
      13. # automatically tag new arrays as belonging to the local system
      14. HOMEHOST <system>
      15. # definitions of existing MD arrays
      16. ARRAY /dev/md0 metadata=1.2 name=NAS:TimeMachine UUID=ef684837:3028a273:9a9c4321:b54d3$
      17. # instruct the monitoring daemon where to send mail alerts
      18. MAILADDR mixxxxx@xxxxxx.de
      19. MAILFROM root
      Display All


      Shouldn't there be two UUIDs?

      Sorry, that's all only my fault. :(


      Edit:

      Source Code

      1. root@NAS:/dev/disk/by-uuid# ls
      2. 55815ec0-944c-4049-ab74-61b0219851ed 8746-AD55 ac210c2f-72b2-4a16-b7f0-3d9620067664
      3. 5a71893d-9098-4ccc-bbcf-8519e5d5a13a a17632c2-23b3-4d60-a7ab-ca18b5b54cc7 c15f9afc-6c05-40d3-bb05-840bac43c9f8


      Source Code

      1. root@NAS:~# mount -l
      2. sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
      3. proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
      4. udev on /dev type devtmpfs (rw,relatime,size=10240k,nr_inodes=495568,mode=755)
      5. devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
      6. tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=397796k,mode=755)
      7. /dev/disk/by-uuid/55815ec0-944c-4049-ab74-61b0219851ed on / type ext4 (rw,noatime,nodiratime,errors=remount-ro,user_xattr,barrier=1,data=ordered,discard)
      8. tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
      9. tmpfs on /run/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=1617440k)
      10. /dev/sda1 on /boot/efi type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=cp437,iocharset=utf8,shortname=mixed,errors=remount-ro)
      11. tmpfs on /tmp type tmpfs (rw,relatime)
      12. /dev/sdc1 on /media/ac210c2f-72b2-4a16-b7f0-3d9620067664 type ext4 (rw,noexec,relatime,user_xattr,barrier=1,data=ordered,jqfmt=vfsv0,usrjquota=aquota.user,grpjquota=aquota.group,_netdev) [Medien2]
      13. /dev/sdb1 on /media/a17632c2-23b3-4d60-a7ab-ca18b5b54cc7 type ext4 (rw,noexec,relatime,user_xattr,barrier=1,data=ordered,jqfmt=vfsv0,usrjquota=aquota.user,grpjquota=aquota.group,_netdev) [Medien1]
      14. /dev/sdd1 on /media/c15f9afc-6c05-40d3-bb05-840bac43c9f8 type ext4 (rw,noexec,relatime,user_xattr,barrier=1,data=ordered,jqfmt=vfsv0,usrjquota=aquota.user,grpjquota=aquota.group,_netdev) [Medien3]
      15. rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime)
      Display All


      Brainfuck Source Code

      1. root@NAS:/dev/disk/by-uuid# blkid -o list -w /dev/null
      2. device fs_type label mount point UUID
      3. ---------------------------------------------------------------------------------------------------------------------------
      4. /dev/sda3 swap <swap> 5a71893d-9098-4ccc-bbcf-8519e5d5a13a
      5. /dev/sda1 vfat /boot/efi 8746-AD55
      6. /dev/sda2 ext4 / 55815ec0-944c-4049-ab74-61b0219851ed
      7. /dev/sdb1 ext4 Medien1 /media/a17632c2-23b3-4d60-a7ab-ca18b5b54cc7 a17632c2-23b3-4d60-a7ab-ca18b5b54cc7
      8. /dev/sdc1 ext4 Medien2 /media/ac210c2f-72b2-4a16-b7f0-3d9620067664 ac210c2f-72b2-4a16-b7f0-3d9620067664
      9. /dev/sdd1 ext4 Medien3 /media/c15f9afc-6c05-40d3-bb05-840bac43c9f8 c15f9afc-6c05-40d3-bb05-840bac43c9f8


      Where are the UUIDs for the RAID-HDDs?

      There _are_ /dev/sde and sdf:

      Source Code

      1. root@NAS:/# fdisk -l
      2. WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.
      3. Disk /dev/sda: 40.0 GB, 40020664320 bytes
      4. 255 heads, 63 sectors/track, 4865 cylinders, total 78165360 sectors
      5. Units = sectors of 1 * 512 = 512 bytes
      6. Sector size (logical/physical): 512 bytes / 512 bytes
      7. I/O size (minimum/optimal): 512 bytes / 512 bytes
      8. Disk identifier: 0x00000000
      9. Device Boot Start End Blocks Id System
      10. /dev/sda1 1 78165359 39082679+ ee GPT
      11. WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted.
      12. Disk /dev/sdb: 3000.6 GB, 3000592982016 bytes
      13. 256 heads, 63 sectors/track, 363376 cylinders, total 5860533168 sectors
      14. Units = sectors of 1 * 512 = 512 bytes
      15. Sector size (logical/physical): 512 bytes / 4096 bytes
      16. I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      17. Disk identifier: 0x00000000
      18. Device Boot Start End Blocks Id System
      19. /dev/sdb1 1 4294967295 2147483647+ ee GPT
      20. Partition 1 does not start on physical sector boundary.
      21. WARNING: GPT (GUID Partition Table) detected on '/dev/sdc'! The util fdisk doesn't support GPT. Use GNU Parted.
      22. Disk /dev/sdc: 3000.6 GB, 3000592982016 bytes
      23. 256 heads, 63 sectors/track, 363376 cylinders, total 5860533168 sectors
      24. Units = sectors of 1 * 512 = 512 bytes
      25. Sector size (logical/physical): 512 bytes / 4096 bytes
      26. I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      27. Disk identifier: 0x00000000
      28. Device Boot Start End Blocks Id System
      29. /dev/sdc1 1 4294967295 2147483647+ ee GPT
      30. Partition 1 does not start on physical sector boundary.
      31. WARNING: GPT (GUID Partition Table) detected on '/dev/sdd'! The util fdisk doesn't support GPT. Use GNU Parted.
      32. Disk /dev/sdd: 3000.6 GB, 3000592982016 bytes
      33. 256 heads, 63 sectors/track, 363376 cylinders, total 5860533168 sectors
      34. Units = sectors of 1 * 512 = 512 bytes
      35. Sector size (logical/physical): 512 bytes / 4096 bytes
      36. I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      37. Disk identifier: 0x00000000
      38. Device Boot Start End Blocks Id System
      39. /dev/sdd1 1 4294967295 2147483647+ ee GPT
      40. Partition 1 does not start on physical sector boundary.
      41. WARNING: GPT (GUID Partition Table) detected on '/dev/sde'! The util fdisk doesn't support GPT. Use GNU Parted.
      42. Disk /dev/sde: 3000.6 GB, 3000592982016 bytes
      43. 255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectors
      44. Units = sectors of 1 * 512 = 512 bytes
      45. Sector size (logical/physical): 512 bytes / 4096 bytes
      46. I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      47. Disk identifier: 0x00000000
      48. Disk /dev/sde doesn't contain a valid partition table
      49. WARNING: GPT (GUID Partition Table) detected on '/dev/sdf'! The util fdisk doesn't support GPT. Use GNU Parted.
      50. Disk /dev/sdf: 3000.6 GB, 3000592982016 bytes
      51. 255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectors
      52. Units = sectors of 1 * 512 = 512 bytes
      53. Sector size (logical/physical): 512 bytes / 4096 bytes
      54. I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      55. Disk identifier: 0x00000000
      56. Disk /dev/sdf doesn't contain a valid partition table
      Display All


      Source Code

      1. root@NAS:/# cat /proc/partitions
      2. major minor #blocks name
      3. 8 0 39082680 sda
      4. 8 1 498688 sda1
      5. 8 2 34472960 sda2
      6. 8 3 4109312 sda3
      7. 8 16 2930266584 sdb
      8. 8 17 2930265543 sdb1
      9. 8 32 2930266584 sdc
      10. 8 33 2930265543 sdc1
      11. 8 48 2930266584 sdd
      12. 8 49 2930265543 sdd1
      13. 8 64 2930266584 sde
      14. 8 80 2930266584 sdf
      Display All


      OMV 2.1.25, Asus P5K, C2D 4300, 4 GB RAM, 1x Intel SSDA2CT04, 5x Seagate ST3000DM001-1CH1
      Pictures of my NAS (with Nanoxia HDD-Cages)

      The post was edited 4 times, last by Mierscheid ().

    • It isn't detecting a filesystem on your raid array. Here is what I would do:

      Everything is done in the web interface.

      - Wipe both drives
      - Create raid array
      - Let it sync
      - Create filesystem on raid array (ext4 or xfs)
      - Mount that filesystem
      omv 4.0.14 arrakis | 64 bit | 4.13 backports kernel | omvextrasorg 4.1.1
      omv-extras.org plugins source code and issue tracker - github.com/OpenMediaVault-Plugin-Developers

      Please don't PM for support... Too many PMs!
    • Hmmm, okay, again... this take a while...
      There is nothing to sweep:

      Source Code

      1. Command (m for help): p
      2. Disk /dev/sde: 3000.6 GB, 3000592982016 bytes
      3. 255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectors
      4. Units = sectors of 1 * 512 = 512 bytes
      5. Sector size (logical/physical): 512 bytes / 4096 bytes
      6. I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      7. Disk identifier: 0x7a3ee645
      8. Device Boot Start End Blocks Id System


      It's a matter of trust. I'd a bad feeling about that RAID.
      OMV 2.1.25, Asus P5K, C2D 4300, 4 GB RAM, 1x Intel SSDA2CT04, 5x Seagate ST3000DM001-1CH1
      Pictures of my NAS (with Nanoxia HDD-Cages)
    • Is it raid 1? If yes, then I would not use raid and just setup an rsync job or rsnapshot (plugin available) to run 1,2,3.. times a day.
      omv 4.0.14 arrakis | 64 bit | 4.13 backports kernel | omvextrasorg 4.1.1
      omv-extras.org plugins source code and issue tracker - github.com/OpenMediaVault-Plugin-Developers

      Please don't PM for support... Too many PMs!