OMV on a Board with UEFI?

Hessi · 13. November 2014

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

ryecoaaron · 13. November 2014

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.

Hessi · 13. November 2014

I will try it.
Who signed the boot keys? The NSA?
Who decrided, what is a "secure" OS?
That is my hardware! My decission!
Sorry, OT, I know...

KM0201 · 13. November 2014

Howto install OpenMediaVault on Debian 7.x (Wheezy)

Hessi · 14. November 2014

Okay, thanks a lot!
Everything has worked perfectly as you told.
One more thing is... my RAID-1 is gone!
Don't see the Filesystems of sde or sdf nor a RAID-Array.

ryecoaaron · 14. November 2014

What is the output of:

fdisk -l
blkid
cat /proc/mdstat

Hessi · 14. November 2014

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.

Hessi · 14. November 2014

Too sad, still gone.

fdisk -l

Code

...
Disk /dev/sde: 3000.6 GB, 3000592982016 bytes
255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000


   Device Boot      Start         End      Blocks   Id  System
/dev/sde1               1  4294967295  2147483647+  ee  GPT
Partition 1 does not start on physical sector boundary.


WARNING: GPT (GUID Partition Table) detected on '/dev/sdf'! The util fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sdf: 3000.6 GB, 3000592982016 bytes
255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000


   Device Boot      Start         End      Blocks   Id  System
/dev/sdf1               1  4294967295  2147483647+  ee  GPT
Partition 1 does not start on physical sector boundary.

Alles anzeigen

blkid:

Code

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

cat /proc/mdstat:

Code

Personalities : 
unused devices: <none>

ryecoaaron · 14. November 2014

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

Hessi · 14. November 2014

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.

Code

root@NAS:~# mdadm --assemble /dev/md127 /dev/sd[ef]1 --verbose --force
mdadm: looking for devices for /dev/md127
mdadm: cannot open device /dev/sd[ef]1: No such file or directory
mdadm: /dev/sd[ef]1 has no superblock - assembly aborted

ryecoaaron · 14. November 2014

You must not have wiped the drives before creating the array then. Try this:

mdadm --assemble /dev/md127 /dev/sd[ef] --verbose --force

Hessi · 14. November 2014

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.

Code

mdadm: looking for devices for /dev/md127
mdadm: Cannot assemble mbr metadata on /dev/sde
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.

ryecoaaron · 14. November 2014

If you don't need to save data, I recommend doing the following first:

Code

mdadm --zero-superblock /dev/sde
mdadm --zero-superblock /dev/sdf
dd if=/dev/zero of=/dev/sde bs=512 count=10000
dd if=/dev/zero of=/dev/sdf bs=512 count=10000

Hessi · 14. November 2014

Code

root@NAS:~# mdadm --zero-superblock /dev/sde
mdadm: Unrecognised md component device - /dev/sde

It's okay. I'll create a new RAID.
Perhaps it's an issue with the new SATA-Controller?

ryecoaaron · 14. November 2014

That message is fine. Keep going with the other commands.

Hessi · 14. November 2014

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:

Code

# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#


# by default, scan all partitions (/proc/partitions) for MD superblocks.
# alternatively, specify devices to scan, using wildcards if desired.
# Note, if no DEVICE line is present, then "DEVICE partitions" is assumed.
# To avoid the auto-assembly of RAID devices a pattern that CAN'T match is
# used if no RAID devices are configured.
DEVICE partitions


# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=yes


# automatically tag new arrays as belonging to the local system
HOMEHOST <system>


# definitions of existing MD arrays
ARRAY /dev/md0 metadata=1.2 name=NAS:TimeMachine UUID=ef684837:3028a273:9a9c4321:b54d3$


# instruct the monitoring daemon where to send mail alerts
MAILADDR mixxxxx@xxxxxx.de
MAILFROM root

Alles anzeigen

Shouldn't there be two UUIDs?

Sorry, that's all only my fault.

Edit:

Code

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

Code

root@NAS:~# mount -l
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,relatime,size=10240k,nr_inodes=495568,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=397796k,mode=755)
/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)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /run/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=1617440k)
/dev/sda1 on /boot/efi type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=cp437,iocharset=utf8,shortname=mixed,errors=remount-ro)
tmpfs on /tmp type tmpfs (rw,relatime)
/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]
/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]
/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]
rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime)

Alles anzeigen

Code

root@NAS:/dev/disk/by-uuid# blkid -o list -w /dev/null 
device                       fs_type     label        mount point                      UUID
---------------------------------------------------------------------------------------------------------------------------
/dev/sda3                    swap                     <swap>                           5a71893d-9098-4ccc-bbcf-8519e5d5a13a
/dev/sda1                    vfat                     /boot/efi                        8746-AD55
/dev/sda2                    ext4                     /                                55815ec0-944c-4049-ab74-61b0219851ed
/dev/sdb1                    ext4        Medien1      /media/a17632c2-23b3-4d60-a7ab-ca18b5b54cc7 a17632c2-23b3-4d60-a7ab-ca18b5b54cc7
/dev/sdc1                    ext4        Medien2      /media/ac210c2f-72b2-4a16-b7f0-3d9620067664 ac210c2f-72b2-4a16-b7f0-3d9620067664
/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:

Code

root@NAS:/# fdisk -l


WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sda: 40.0 GB, 40020664320 bytes
255 heads, 63 sectors/track, 4865 cylinders, total 78165360 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000


   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1    78165359    39082679+  ee  GPT


WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sdb: 3000.6 GB, 3000592982016 bytes
256 heads, 63 sectors/track, 363376 cylinders, total 5860533168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000


   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1  4294967295  2147483647+  ee  GPT
Partition 1 does not start on physical sector boundary.


WARNING: GPT (GUID Partition Table) detected on '/dev/sdc'! The util fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sdc: 3000.6 GB, 3000592982016 bytes
256 heads, 63 sectors/track, 363376 cylinders, total 5860533168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000


   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1               1  4294967295  2147483647+  ee  GPT
Partition 1 does not start on physical sector boundary.


WARNING: GPT (GUID Partition Table) detected on '/dev/sdd'! The util fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sdd: 3000.6 GB, 3000592982016 bytes
256 heads, 63 sectors/track, 363376 cylinders, total 5860533168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000


   Device Boot      Start         End      Blocks   Id  System
/dev/sdd1               1  4294967295  2147483647+  ee  GPT
Partition 1 does not start on physical sector boundary.


WARNING: GPT (GUID Partition Table) detected on '/dev/sde'! The util fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sde: 3000.6 GB, 3000592982016 bytes
255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000


Disk /dev/sde doesn't contain a valid partition table


WARNING: GPT (GUID Partition Table) detected on '/dev/sdf'! The util fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sdf: 3000.6 GB, 3000592982016 bytes
255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000


Disk /dev/sdf doesn't contain a valid partition table

Alles anzeigen

Code

root@NAS:/# cat /proc/partitions 
major minor  #blocks  name


   8        0   39082680 sda
   8        1     498688 sda1
   8        2   34472960 sda2
   8        3    4109312 sda3
   8       16 2930266584 sdb
   8       17 2930265543 sdb1
   8       32 2930266584 sdc
   8       33 2930265543 sdc1
   8       48 2930266584 sdd
   8       49 2930265543 sdd1
   8       64 2930266584 sde
   8       80 2930266584 sdf

Alles anzeigen

ryecoaaron · 14. November 2014

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

Hessi · 14. November 2014

Hmmm, okay, again... this take a while...
There is nothing to sweep:

Code

Command (m for help): p


Disk /dev/sde: 3000.6 GB, 3000592982016 bytes
255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x7a3ee645


   Device Boot      Start         End      Blocks   Id  System

Alles anzeigen

It's a matter of trust. I'd a bad feeling about that RAID.

ryecoaaron · 14. November 2014

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.

Hessi · 14. November 2014

Good hint. But... how can I stop the creation of the RAID?

Jetzt mitmachen!