You know what? Forget it. I guess OMV is not ready for prime time when used with an RPi. It might just be worth looking into a build tailored for the Rpi with so many users out there all looking to do the same thing. Then again, if it is getting to you, maybe you should step away. The universe will continue without you or OMV. Personally I am done with both.
Beiträge von BobMendon
-
-
Output of cat /proc/mdstat
root@raspberrypi:/boot# cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4]
md0 : active (auto-read-only) raid5 sda[0] sdd[3] sdc[2] sdb[1]
5860150272 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/4] [UUUU]
resync=PENDING
bitmap: 1/15 pages [4KB], 65536KB chunk
unused devices: <none>
root@raspberrypi:/boot# -
I recommend against using raid on an RPi since it has to use USB drives. The RPi boots too fast for some usb controllers to initialize. So, if you insist on ignoring my recommendation, look up add a bootdelay to cmdline.txt.
My friend, you don't need to be so patronizing and condescending. I have read your rant and it was duly noted along with the attending observation by another user about "if it doesn't work then why put it in there".
I added the boot delay btw. I also just ran, mdadm --assemble --scan --verbose and it came back in a clean, resyncing (PENDING) status. What does that mean and how do I get it out of PENDING status?
You really need to work on your social skills!
Array details output:
Version : 1.2
Creation Time : Mon Dec 26 19:23:55 2016
Raid Level : raid5
Array Size : 5860150272 (5588.67 GiB 6000.79 GB)
Used Dev Size : 1953383424 (1862.89 GiB 2000.26 GB)
Raid Devices : 4
Total Devices : 4
Persistence : Superblock is persistent
Intent Bitmap : Internal
Update Time : Fri Dec 30 01:49:59 2016
State : clean, resyncing (PENDING)
Active Devices : 4
Working Devices : 4
Failed Devices : 0
Spare Devices : 0
Layout : left-symmetric
Chunk Size : 512K
Name : raspberrypi:Five0 (local to host raspberrypi)
UUID : 4a311105:49e628d7:36317d3e:1cf3b6a1
Events : 24034
Number Major Minor RaidDevice State
0 8 0 0 active sync /dev/sda
1 8 16 1 active sync /dev/sdb
2 8 32 2 active sync /dev/sdc
3 8 48 3 active sync /dev/sdd -
root@raspberrypi:~# cat /etc/mdadm/mdadm.conf
# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about thisfile.
#
# by default, scan all partitions (/proc/partitions) for MDsuperblocks.
# alternatively, specify devices to scan, using wildcards ifdesired.
# Note, if no DEVICE line is present, then "DEVICEpartitions" is assumed.
# To avoid the auto-assembly of RAID devices a pattern thatCAN'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 localsystem
HOMEHOST <system>
# definitions of existing MD arrays
ARRAY /dev/md0 metadata=1.2 name=raspberrypi:Five0UUID=4a311105:49e628d7:36317d3e:1cf3b6a1
# instruct the monitoring daemon where to send mail alerts
MAILADDR bwheeler@mendoncomp.com
MAILFROM rootroot@raspberrypi:~#
root@raspberrypi:~# DeviceBootStartEndSectorsSize Id Type
root@raspberrypi:~# clear
root@raspberrypi:~# cat /etc/mdadm/mdadm.conf
-bash: Device: command not found
# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about thisfile.
#
# by default, scan all partitions (/proc/partitions) for MDsuperblocks.
root@raspberrypi:~# /dev/mmcblk0p1819212287911468856McW95 FAT32 (LBA)
# instruct the monitoring daemon where to send mail alerts
MAILADDR bwheeler@mendoncomp.com
-bash: syntax error near unexpected token `('MAILFROMrootroot@raspberrypi:~#
root@raspberrypi:~# /dev/mmcblk0p2122880702873569058563.3G 83 Linux
-bash: /dev/mmcblk0p2: Permission denied
root@raspberrypi:~# /dev/mmcblk0p37028736 60751871 53723136 25.6G 83 Linux
-bash: /dev/mmcblk0p3: Permission denied
root@raspberrypi:~#
root@raspberrypi:~# Disk /dev/sda: 1.8 TiB, 2000398934016bytes, 3907029168 sectors
-bash: Disk: command not found
root@raspberrypi:~# Units: sectors of 1 * 512 = 512 bytes
-bash: Units:: command not found
root@raspberrypi:~# Sector size (logical/physical): 512bytes / 512 bytes
-bash: syntax error near unexpected token `('
root@raspberrypi:~# I/O size (minimum/optimal): 512 bytes /512 bytes
-bash: syntax error near unexpected token `('
root@raspberrypi:~# Disk /dev/sdc: 1.8 TiB, 2000398934016bytes, 3907029168 sectors
-bash: Disk: command not found
root@raspberrypi:~# Units: sectors of 1 * 512 = 512 bytes
-bash: Units:: command not found
root@raspberrypi:~# Sector size (logical/physical): 512bytes / 512 bytes
-bash: syntax error near unexpected token `('
root@raspberrypi:~# I/O size (minimum/optimal): 512 bytes /512 bytes
-bash: syntax error near unexpected token `('
root@raspberrypi:~# Disk /dev/sdd: 1.8 TiB, 2000398934016bytes, 3907029168 sectors
-bash: Disk: command not found
root@raspberrypi:~# Units: sectors of 1 * 512 = 512 bytes
-bash: Units:: command not found
root@raspberrypi:~# Sector size (logical/physical): 512bytes / 512 bytes
-bash: syntax error near unexpected token `('
root@raspberrypi:~# I/O size (minimum/optimal): 512 bytes /512 bytes
-bash: syntax error near unexpected token `('
root@raspberrypi:~# Disk /dev/sdb: 1.8 TiB, 2000398934016bytes, 3907029168 sectors
-bash: Disk: command not found
root@raspberrypi:~# Units: sectors of 1 * 512 = 512 bytes
-bash: Units:: command not found
root@raspberrypi:~# Sector size (logical/physical): 512bytes / 512 bytes
-bash: syntax error near unexpected token `('
root@raspberrypi:~# I/O size (minimum/optimal): 512 bytes /512 bytes
-bash: syntax error near unexpected token `('
root@raspberrypi:~# root@raspberrypi:~# clear
-bash: root@raspberrypi:~#: command not found
root@raspberrypi:~# root@raspberrypi:~# cat/etc/mdadm/mdadm.conf
-bash: root@raspberrypi:~#: command not found
root@raspberrypi:~# # mdadm.conf
root@raspberrypi:~# #
root@raspberrypi:~# # Please refer to mdadm.conf(5) forinformation about this file.
root@raspberrypi:~# #
root@raspberrypi:~#
root@raspberrypi:~# # by default, scan all partitions(/proc/partitions) for MD superblocks.
root@raspberrypi:~# # alternatively, specify devices toscan, using wildcards if desired.
root@raspberrypi:~# # Note, if no DEVICE line is present,then "DEVICE partitions" is assumed.
root@raspberrypi:~# # To avoid the auto-assembly of RAIDdevices a pattern that CAN'T match is
root@raspberrypi:~# # used if no RAID devices areconfigured.
root@raspberrypi:~# DEVICE partitions
-bash: DEVICE: command not found
root@raspberrypi:~#
root@raspberrypi:~# # auto-create devices with Debianstandard permissions
root@raspberrypi:~# CREATE owner=root group=disk mode=0660auto=yes
-bash: CREATE: command not found
root@raspberrypi:~#
root@raspberrypi:~# # automatically tag new arrays asbelonging to the local system
root@raspberrypi:~# HOMEHOST <system>
-bash: syntax error near unexpected token `newline'
root@raspberrypi:~#
root@raspberrypi:~# # definitions of existing MD arrays
root@raspberrypi:~# ARRAY /dev/md0 metadata=1.2name=raspberrypi:Five0 UUID=4a311105:49e628d7:36317d3e:1cf3b6a1
-bash: ARRAY: command not found
root@raspberrypi:~#
root@raspberrypi:~# # instruct the monitoring daemon whereto send mail alerts
root@raspberrypi:~# MAILADDR bwheeler@mendoncomp.com
-bash: MAILADDR: command not found
root@raspberrypi:~# MAILFROM rootroot@raspberrypi:~#
-bash: MAILFROM: command not found
root@raspberrypi:~#
mdadm --detail --scan –verbose gave no results. -
So, I waited patiently for about 4 days for my raid 5 to build and then after it syncs, I go to initialize and it starts out ok and then it flags a error with no explanation and seems to go into a state where it is just spinning it's wheels. This is where I screwed up and rebooted the system because nothing could get it out of it's loop and the unspecified error message kept popping back up. All the drives were clean and wiped for extra measure before building the array. From what I can see, the base array is still there but in an uninitialized mode and it won't appear when I attempt to create the array under RAID Management.
Here are relevant files:
root@raspberrypi:~# cat /proc/mdstat
Personalities :
unused devices: <none>root@raspberrypi:~# blkid
/dev/mmcblk0p1: SEC_TYPE="msdos"LABEL="boot" UUID="7D5C-A285" TYPE="vfat"PARTUUID="000b5098-01"
/dev/mmcblk0p2: LABEL="omv"UUID="5d18be51-3217-4679-9c72-a54e0fc53d6b" TYPE="ext4"PARTUUID="000b5098-02"
/dev/mmcblk0p3:UUID="fa36508a-b3c4-4499-b30a-711dd5994225" TYPE="ext4"PARTUUID="000b5098-03"
/dev/sda:UUID="4a311105-49e6-28d7-3631-7d3e1cf3b6a1"UUID_SUB="d6a9ebd0-abc6-dc48-d836-5867f1ebc97b"LABEL="raspberrypi:Five0" TYPE="linux_raid_member"
/dev/sdc:UUID="4a311105-49e6-28d7-3631-7d3e1cf3b6a1"UUID_SUB="0c8f8a2f-c23f-f31d-fcbe-8c20a1e75963"LABEL="raspberrypi:Five0" TYPE="linux_raid_member"
/dev/sdd:UUID="4a311105-49e6-28d7-3631-7d3e1cf3b6a1"UUID_SUB="e9587db2-c8c3-54b8-df01-65a618da7df7" LABEL="raspberrypi:Five0"TYPE="linux_raid_member"
/dev/sdb:UUID="4a311105-49e6-28d7-3631-7d3e1cf3b6a1"UUID_SUB="71101f28-98aa-5a6b-6ddd-52249acca4e6"LABEL="raspberrypi:Five0" TYPE="linux_raid_member"
/dev/mmcblk0: PTUUID="000b5098"PTTYPE="dos"
root@raspberrypi:~# root@raspberrypi:~# blkid
-bash: root@raspberrypi:~#: command not found
root@raspberrypi:~# /dev/mmcblk0p1:SEC_TYPE="msdos" LABEL="boot" UUID="7D5C-A285"TYPE="vfat" PARTUUID="000b5098-01"
-bash: /dev/mmcblk0p1:: No such file or directory
root@raspberrypi:~# /dev/mmcblk0p2: LABEL="omv"UUID="5d18be51-3217-4679-9c72-a54e0fc53d6b" TYPE="ext4"PARTUUID="000b5098-02"
-bash: /dev/mmcblk0p2:: No such file or directory
root@raspberrypi:~# /dev/mmcblk0p3:UUID="fa36508a-b3c4-4499-b30a-711dd5994225" TYPE="ext4"PARTUUID="000b5098-03"
-bash: /dev/mmcblk0p3:: No such file or directory
root@raspberrypi:~# /dev/sda:UUID="4a311105-49e6-28d7-3631-7d3e1cf3b6a1"UUID_SUB="d6a9ebd0-abc6-dc48-d836-5867f1ebc97b"LABEL="raspberrypi:Five0" TYPE="linux_raid_member"
-bash: /dev/sda:: No such file or directory
root@raspberrypi:~# /dev/sdc:UUID="4a311105-49e6-28d7-3631-7d3e1cf3b6a1"UUID_SUB="0c8f8a2f-c23f-f31d-fcbe-8c20a1e75963"LABEL="raspberrypi:Five0" TYPE="linux_raid_member"
-bash: /dev/sdc:: No such file or directory
root@raspberrypi:~# /dev/sdd:UUID="4a311105-49e6-28d7-3631-7d3e1cf3b6a1"UUID_SUB="e9587db2-c8c3-54b8-df01-65a618da7df7"LABEL="raspberrypi:Five0" TYPE="linux_raid_member"
-bash: /dev/sdd:: No such file or directory
root@raspberrypi:~# /dev/sdb: UUID="4a311105-49e6-28d7-3631-7d3e1cf3b6a1"UUID_SUB="71101f28-98aa-5a6b-6ddd-52249acca4e6"LABEL="raspberrypi:Five0" TYPE="linux_raid_member"
-bash: /dev/sdb:: No such file or directory
root@raspberrypi:~# /dev/mmcblk0:PTUUID="000b5098" PTTYPE="dos"
-bash: /dev/mmcblk0:: No such file or directory
root@raspberrypi:~#root@raspberrypi:~# fdisk -l
Disk /dev/ram0: 4 MiB, 4194304 bytes, 8192 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 /dev/ram1: 4 MiB, 4194304 bytes, 8192 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 /dev/ram2: 4 MiB, 4194304 bytes, 8192 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 /dev/ram3: 4 MiB, 4194304 bytes, 8192 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 /dev/ram4: 4 MiB, 4194304 bytes, 8192 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 /dev/ram5: 4 MiB, 4194304 bytes, 8192 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 /dev/ram6: 4 MiB, 4194304 bytes, 8192 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 /dev/ram7: 4 MiB, 4194304 bytes, 8192 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 /dev/ram8: 4 MiB, 4194304 bytes, 8192 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 /dev/ram9: 4 MiB, 4194304 bytes, 8192 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 /dev/ram10: 4 MiB, 4194304 bytes, 8192 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 /dev/ram11: 4 MiB, 4194304 bytes, 8192 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 /dev/ram12: 4 MiB, 4194304 bytes, 8192 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 /dev/ram13: 4 MiB, 4194304 bytes, 8192 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 /dev/ram14: 4 MiB, 4194304 bytes, 8192 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 /dev/ram15: 4 MiB, 4194304 bytes, 8192 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 /dev/mmcblk0: 29 GiB, 31104958464 bytes, 60751872sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x000b5098
DeviceBootStartEndSectorsSize Id Type
/dev/mmcblk0p1819212287911468856Mc W95 FAT32 (LBA)
/dev/mmcblk0p2122880702873569058563.3G 83 Linux
/dev/mmcblk0p37028736 60751871 53723136 25.6G 83 Linux
Disk /dev/sda: 1.8 TiB, 2000398934016 bytes, 3907029168sectors
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 /dev/sdc: 1.8 TiB, 2000398934016 bytes, 3907029168sectors
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 /dev/sdd: 1.8 TiB, 2000398934016 bytes, 3907029168 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 /dev/sdb: 1.8 TiB, 2000398934016 bytes, 3907029168sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
root@raspberrypi:~#Drives used, 4x Seagate Barracuda 3.5 Inch 2Tb 7200 Rpm 64Mb6Gb/S Internal Sata Drive OEM
-
Does that mean that if my raspberry pi fails, I can pull the memory card, pop it into another raspberry pi and it will pick up where it left off?
-
This may sound like a noob question and rightly so, but how does one backup the software raid5 configuration info? Would one normally just rely on a snapshot of the system drive?
Thanks...
-
That doesn't sound unreasonable for building the array. Mine is building raid 5 on four 2TB drives and has been running about three days and is just at 84%. It should finish sometime today.
-
After reading the pined posts, am I correct in thinking that the OwnCloud and the Virtual Box plugins are no longer supported. If that is the case, why aren't they pulled from the extras repository? Can these two items be installed via CLI?
-
I get this message when trying to create a VM, "Error #64:exception 'Exception' with message 'Could not connect to host (http://127.0.0.1:18083/)' in /usr/share/phpvirtualbox/lib/vboxconnector.php:220Stack trace:#0 /usr/share/openmediavault/engined/rpc/virtualbox.inc(176): vboxconnector->connect()#1 [internal function]: OMVRpcServiceVirtualBox->getMachines(Array, Array)#2 /usr/share/php/openmediavault/rpcservice.inc(125): call_user_func_array(Array, Array)#3 /usr/share/php/openmediavault/rpc.inc(79): OMVRpcServiceAbstract->callMethod('getMachines', Array, Array)#4 /usr/sbin/omv-engined(500): OMVRpc::exec('VirtualBox', 'getMachines', Array, Array, 1)#5 {main}"
What additional information do you need for help with this?
Computer: Zbox CA320 nano, 240 GB SSD, 8 GB memory A6 processor running 1.0ghz. 2.2.13 Stoneburner.
