OMV Cannot detect my RAID controller

Solo0815 · 22. September 2014

as far as I can see, your Controller is detected, and the system sees your RAID1 as one HDD

Code

/dev/mapper/nvidia_fccijacb on /media/3ad3e032-ada2-46b4-8b3e-033f206ca1f5 type ext4 (rw,noexec,relatime,user_xattr,barrier=1,data=ordered,jqfmt=vfsv0,usrjquota=aquota.user,grpjquota=aquota.group,_netdev)

and it seems to be mounted:

Code

/dev/sda on /media/3ad3e032-ada2-46b4-8b3e-033f206ca1f5 type ext4 (rw,noexec,relatime,user_xattr,barrier=1,data=ordered,jqfmt=vfsv0,usrjquota=aquota.user,grpjquota=aquota.group,_netdev)

but for some reason there are 2 HDDs with the same UUID. Don't know, if this is normal for RAID1

Code

root@openmediavault:~# blkid
/dev/sda: LABEL="store" UUID="3ad3e032-ada2-46b4-8b3e-033f206ca1f5" TYPE="ext4" 
/dev/sdb: LABEL="store" UUID="3ad3e032-ada2-46b4-8b3e-033f206ca1f5" TYPE="ext4"

Please check with
cd /media/3ad3e032-ada2-46b4-8b3e-033f206ca1f5
ls -l
if there are your files on the mounted drive.

sidthakur · 22. September 2014

Solo0815 thx for responding.
The first set of logs was when the RAID device was getting detected. I'm copying the relevent logs here again - I upgraded to OMV 1.0 and rebooted. This is what the output of mount, df -h and blkid looks like now. For some reason /dev/sda has taken over the UUID assigned to the RAID.
----------------------------------------------------------------------------

Code

root@openmediavault:~# mount
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=95207,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=77340k,mode=755)
/dev/disk/by-uuid/0fdc71bd-41eb-47c8-92e4-9a458e50f384 on / type ext4 (rw,relatime,errors=remount-ro,user_xattr,acl,barrier=1,data=ordered)
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=456340k)
tmpfs on /tmp type tmpfs (rw,relatime)
/dev/sda on /media/3ad3e032-ada2-46b4-8b3e-033f206ca1f5 type ext4 (rw,noexec,relatime,user_xattr,barrier=1,data=ordered,jqfmt=vfsv0,usrjquota=aquota.user,grpjquota=aquota.group,_netdev)
rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime)
root@openmediavault:~# df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 59G 1.3G 54G 3% /
udev 10M 0 10M 0% /dev
tmpfs 76M 256K 76M 1% /run
/dev/disk/by-uuid/0fdc71bd-41eb-47c8-92e4-9a458e50f384 59G 1.3G 54G 3% /
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 446M 0 446M 0% /run/shm
tmpfs 378M 0 378M 0% /tmp
/dev/sda 917G 200M 917G 1% /media/3ad3e032-ada2-46b4-8b3e-033f206ca1f5
root@openmediavault:~# blkid
/dev/sda: LABEL="store" UUID="3ad3e032-ada2-46b4-8b3e-033f206ca1f5" TYPE="ext4" 
/dev/sdb: LABEL="store" UUID="3ad3e032-ada2-46b4-8b3e-033f206ca1f5" TYPE="ext4" 
/dev/sdc1: UUID="0fdc71bd-41eb-47c8-92e4-9a458e50f384" TYPE="ext4" 
/dev/sdc5: UUID="d5bc8fbc-646a-4ab9-ae44-1e2ad541c314" TYPE="swap"
-----------------------------------


The output of /boot/grub/grub.cfg is as follows


### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
 load_env
fi
set default="0"
if [ "${prev_saved_entry}" ]; then
 set saved_entry="${prev_saved_entry}"
 save_env saved_entry
 set prev_saved_entry=
 save_env prev_saved_entry
 set boot_once=true
fi


function savedefault {
 if [ -z "${boot_once}" ]; then
 saved_entry="${chosen}"
 save_env saved_entry
 fi
}


function load_video {
 insmod vbe
 insmod vga
 insmod video_bochs
 insmod video_cirrus
}


insmod part_msdos
insmod ext2
set root='(hd3,msdos1)'
search --no-floppy --fs-uuid --set=root 0fdc71bd-41eb-47c8-92e4-9a458e50f384
if loadfont /usr/share/grub/unicode.pf2 ; then
 set gfxmode=640x480
 load_video
 insmod gfxterm
 insmod part_msdos
 insmod ext2
 set root='(hd3,msdos1)'
 search --no-floppy --fs-uuid --set=root 0fdc71bd-41eb-47c8-92e4-9a458e50f384
 set locale_dir=($root)/boot/grub/locale
 set lang=en_US
 insmod gettext
fi
terminal_output gfxterm
set timeout=5
### END /etc/grub.d/00_header ###


### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
### END /etc/grub.d/05_debian_theme ###


### BEGIN /etc/grub.d/10_linux ###
menuentry 'Debian GNU/Linux, with Linux 3.2.0-4-486' --class debian --class gnu-linux --class gnu --class os {
 load_video
 insmod gzio
 insmod part_msdos
 insmod ext2
 set root='(hd3,msdos1)'
 search --no-floppy --fs-uuid --set=root 0fdc71bd-41eb-47c8-92e4-9a458e50f384
 echo 'Loading Linux 3.2.0-4-486 ...'
 linux /boot/vmlinuz-3.2.0-4-486 root=UUID=0fdc71bd-41eb-47c8-92e4-9a458e50f384 ro quiet dmraid=true
 echo 'Loading initial ramdisk ...'
 initrd /boot/initrd.img-3.2.0-4-486
}
menuentry 'Debian GNU/Linux, with Linux 3.2.0-4-486 (recovery mode)' --class debian --class gnu-linux --class gnu --class os {
 load_video
 insmod gzio
 insmod part_msdos
 insmod ext2
 set root='(hd3,msdos1)'
 search --no-floppy --fs-uuid --set=root 0fdc71bd-41eb-47c8-92e4-9a458e50f384
 echo 'Loading Linux 3.2.0-4-486 ...'
 linux /boot/vmlinuz-3.2.0-4-486 root=UUID=0fdc71bd-41eb-47c8-92e4-9a458e50f384 ro single 
 echo 'Loading initial ramdisk ...'
 initrd /boot/initrd.img-3.2.0-4-486
}
menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-486' --class debian --class gnu-linux --class gnu --class os {
 load_video
 insmod gzio
 insmod part_msdos
 insmod ext2
 set root='(hd3,msdos1)'
 search --no-floppy --fs-uuid --set=root 0fdc71bd-41eb-47c8-92e4-9a458e50f384
 echo 'Loading Linux 2.6.32-5-486 ...'
 linux /boot/vmlinuz-2.6.32-5-486 root=UUID=0fdc71bd-41eb-47c8-92e4-9a458e50f384 ro quiet dmraid=true
 echo 'Loading initial ramdisk ...'
 initrd /boot/initrd.img-2.6.32-5-486
}
menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-486 (recovery mode)' --class debian --class gnu-linux --class gnu --class os {
 load_video
 insmod gzio
 insmod part_msdos
 insmod ext2
 set root='(hd3,msdos1)'
 search --no-floppy --fs-uuid --set=root 0fdc71bd-41eb-47c8-92e4-9a458e50f384
 echo 'Loading Linux 2.6.32-5-486 ...'
 linux /boot/vmlinuz-2.6.32-5-486 root=UUID=0fdc71bd-41eb-47c8-92e4-9a458e50f384 ro single 
 echo 'Loading initial ramdisk ...'
 initrd /boot/initrd.img-2.6.32-5-486
}
### END /etc/grub.d/10_linux ###


### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###


### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###


### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###


### BEGIN /etc/grub.d/41_custom ###
if [ -f $prefix/custom.cfg ]; then
 source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###

Alles anzeigen

Solo0815 · 22. September 2014

and I quote myself:

Zitat

Please check with
cd /media/3ad3e032-ada2-46b4-8b3e-033f206ca1f5
ls -l
if your files are on the mounted drive.

sidthakur · 22. September 2014

Files are there - but these are on the disk /dev/sda1 not on /dev/mapper/nvidia.....

Solo0815 · 22. September 2014

Why should they be on /dev/mapper/nvidia...? /dev/sda is fine.
Please look in the GUI, if /dev/sda is mounted and has 1TB size

sidthakur · 23. September 2014

From the GUI I can see /dev/sda is mounted with size 931GB.
Further I see /dev/sdb is not mounted and shows up in the GUI as N/A.
I'll send a screen shot when I get home

sidthakur · 23. September 2014

Here is the screenshot. When I was on 0.5.x, OMV would recognize my RAID controller as a single device. I could not mount sda or sdb directly. I was under the impression that the RAID1 would show up as a single drive in the UI and not as two separate drives. I should mention that the only files there are
root@openmediavault:/media/3ad3e032-ada2-46b4-8b3e-033f206ca1f5# ls

aquota.group aquota.user lost+found

I have not added anything yet. But the size shows 916GB instead of 1TB. I guess journaled FS do take up a few 100 MB

sidthakur · 23. September 2014

I copied one 430M file over to my NAS as a test. The file did copy over, but the filesystem in the UI did not update. It still shows 916GB available and 200MB used. I was able to mount /dev/sdb as well. That was the intent behind my test. I wanted to see if the hardware RAID was really kicking in. Any thoughts?

sidthakur · 23. September 2014

Bump - any thoughts?

sidthakur · 24. September 2014

So I figured out the problem. During the upgrade from 0.5 to 1.0, my RAID controller basically lost its RAID information. So even when dmraid was set to true, there was no RAID for dmraid to detect. I reconnected my monitor and keyboard and rebooted the system to find that Mediashield had no record of my array. Rebuilt the array - booted up and viola - RAID is back - this is what I now see (attachment). But now I cannot mount the filesystem from the UI. When I SSH in, I do see the filesystem successfully mounted. Is this cause for concern?

I am now testing the system via an NFS upload. Hopefully it works - any thoughts on why I can't mount the FS from the UI?

WastlJ · 24. September 2014

Do you receive any error message?

sidthakur · 25. September 2014

When I try to mount the RAID array - the error message was something like cannot umount /media/3ad3e032-ada2-46b4-8b3e-033f206ca1f5.
It looks like the array is mounted, but the GUI cannot figure out that it is.

pyda · 28. September 2014

Hello, i have same problem whit my RAID HP P400. Partition 1.8TB, has be mounted in "/media" but cannot presented in WEB GUI.RAID 5 3x1TB, OMV 1.0.

Solo0815 · 28. September 2014

@sidthakur and pyda:
Do you mind, opening a detailed bug-report on Mantis with added "System Information > Report".
Thx

pyda · 28. September 2014

I found the same problem hire File Systems not mounting in OMV1.0 GUI , and follow this thread.

Jetzt mitmachen!