Beiträge von itstheburns

Here are the base specs for the system:
Motherboard: ASUS P86-M
BIOS Version: 6702 x64
CPU: Intel Xeon E3122
RAM: 8GB ECC
SATA chipset: C204 or LSI (set via physical jumper)

A little history of the system: The ram and cpu were pulled from a decommissioned dell poweredge server that had some issues. I was able to get this asus board pretty cheap and its matx form factor made it easier to find a compatible compact rack chassis. The bios doesn't have an option to load a raid configuration utility without a physical jumper setting on the motherboard. I currently have it set to use the intel sata controller vs the onboard LSI controller. The intel controller is controlled by software in windows (obviously its not running). It does support raid 5, which i was mistaken. The LSI controller does not support RAID 5. I've had on board raid controllers fail so I don't like using them. The BIOS can be set (when using the Intel controller) to DISABLED, IDE, AHCI (current) or RAID.

As far as OMV seeing it as a raid controller, maybe, I don't know. I know, at this point, the RAID 5 configuration is working. It seems to be a software issue as to why its not starting correctly. After everything, I ran sudo mdadm --manage /dev/md127 --run and the array showed up in the web gui, I mounted it and all the data was there, as if nothing happened. I had reinstalled OMV so I had to recreate my shares and users. I attempted to add the AUTOSTART to mdadm but I'm not having any luck after reboots. I would prefer to not wipe the drives. I can switch the bios to RAID and it seems to boot the same in OMV. I dont have a lot of experience with linux so i'm not real familiar with the commands or what some of the processes are. I only get to learn when there's a problem like this. Other than that, it sits in a rack with only power and ethernet.

I have to keep running sudo mdadm --manage /dev/md127 --run every time the system reboots. It does start up after running the command but not sure what to do in order to automate it.

I did some more searching and ran this:

sudo mdadm --manage /dev/md127 --run

This fixed it. Seems like such a simple command had the system down. I was able to mount it and its showing up as normal. I just have to create my shares again. Thanks for your time.

No, I've never used the onboard raid controller. This onboard controller only has RAID 0, 1, 10. I had it setup using RAID 5 and xfs file system inside omv. Whether the SATA controller is set to raid or ahci, its the same results

Sorry, I didn't know that was the next step. Here is the output:

cat /proc/mdstat
Personalities :
md127 : inactive sdc[3](S) sde[2](S) sdb[1](S) sdd[0](S)
9552 blocks super external:imsm

unused devices: <none>

I'm following what to do exactly. I don't want to mess anything up by doing anything out of order. I'm not real good with this command line stuff.

Here are the results of your commands.

mdadm --stop /dev/md127
mdadm: stopped /dev/md127

mdadm --assemble --force --verbose /dev/md127 /dev/sd[bcde]
mdadm: looking for devices for /dev/md127
mdadm: /dev/sdb is identified as a member of /dev/md127, slot -1.
mdadm: /dev/sdc is identified as a member of /dev/md127, slot -1.
mdadm: /dev/sdd is identified as a member of /dev/md127, slot -1.
mdadm: /dev/sde is identified as a member of /dev/md127, slot -1.
mdadm: Marking array /dev/md127 as 'clean'
mdadm: added /dev/sdc to /dev/md127 as -1
mdadm: added /dev/sdd to /dev/md127 as -1
mdadm: added /dev/sde to /dev/md127 as -1
mdadm: added /dev/sdb to /dev/md127 as -1
mdadm: Container /dev/md127 has been assembled with 4 drives

update-initramfs -u
update-initramfs: Generating /boot/initrd.img-4.9.0-0.bpo.4-amd64

mount -a

Hey everyone. I'm not a linux wiz or know a lot of commands. I get the basics. I have OMV 3.0.94. I have 5 physical drives, 1 160gb boot drive and 4 3tb WD drives setup in RAID 5. I don't know when it happened but my raid array just stopped working. I couldn't tell you when since I dont access this system regularly. It is used as a backup of backup source. All drives are showing up in the bios, in the web gui and in other places when commands are used. I went ahead with this post (Degraded or missing raid array questions) to provide this info:

cat /proc/mdstat
Personalities :
md127 : inactive sdc[3](S) sde[2](S) sdd[1](S) sdb[0](S)
9552 blocks super external:imsm

unused devices: <none>

blkid
/dev/sda1: UUID="1c5113d5-72e5-4ae1-a712-7b52fe8ecf6a" TYPE="ext4" PARTUUID="2e328e8d-01"
/dev/sda5: UUID="81d88f38-9df7-4186-a564-e4d1f7cecc52" TYPE="swap" PARTUUID="2e328e8d-05"
/dev/sde: TYPE="isw_raid_member"
/dev/sdd: TYPE="isw_raid_member"
/dev/sdb: TYPE="isw_raid_member"
/dev/sdc: TYPE="isw_raid_member"

fdisk -l | grep "Disk "
Disk /dev/sda: 149.1 GiB, 160041885696 bytes, 312581808 sectors
Disk identifier: 0x2e328e8d
Disk /dev/sde: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors
Disk /dev/sdd: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors
Disk /dev/sdb: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors
Disk /dev/sdc: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors

cat /etc/mdadm/mdadm.conf

# 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/md127 metadata=imsm UUID=946a3419:9d26306e:22bbc12b:931fad1c
ARRAY metadata=imsm UUID=946a3419:9d26306e:22bbc12b:931fad1c
ARRAY /dev/md/Volume0 container=946a3419:9d26306e:22bbc12b:931fad1c member=0 UUID=035dc25d:c21e7104:fba7638d:77508a55

mdadm --detail --scan --verbose
ARRAY /dev/md127 level=container num-devices=4 metadata=imsm UUID=946a3419:9d26306e:22bbc12b:931fad1c
devices=/dev/sdb,/dev/sdc,/dev/sdd,/dev/sde
root@openmediavault:~#

I'm not really sure where to go from here since I really don't know what to search for. I've attempted to search to rebuild the raid array but I'm not sure. Any help or guidance would be appreciated. I would prefer to attempt to save the raid, if possible.

Since nothing else seems to work and I wasn't getting much help from the interwebs, I tried something to see if it would work and it has. I decided to reinstall OMV on a new USB drive to maintain the existing copy on the original USB drive. Doing so without a network connection I was able to remount the RAID6 partition. All files are intact. Thanks for your help.

mount -a returns:

mount: unknown filesystem type 'xfs'

then returns to prompt.

mount returns:

No worries.

xfs_check /dev/md0 returns

-bash: xfs_check: command not found

Nothing. It brings me back to the prompt.

I had to crop out the image since the file size was too large to insert as one file. Let me know if you need better or different pictures. Thanks!

When I try to enable SSH via WebGUI and I get this error:

Failed to execute command 'export LANG=C; systemctl stop avahi-daemon 2>&1': Failed to stop avahi-daemon.service: Unit avahi-daemon.service not loaded.
Error #4000:exception 'OMVException' with message 'Failed to execute command 'export LANG=C; systemctl stop avahi-daemon 2>&1': Failed to stop avahi-daemon.service: Unit avahi-daemon.service not loaded.' in /usr/share/php/openmediavault/systemctl.inc:64Stack trace:#0 /usr/share/php/openmediavault/systemctl.inc(128): OMVSystemCtl->exec('stop')#1 /usr/share/openmediavault/engined/module/zeroconf.inc(56): OMVSystemCtl->stop()#2 /usr/share/openmediavault/engined/rpc/config.inc(164): OMVModuleZeroconf->stopService()#3 [internal function]: OMVRpcServiceConfig->applyChanges(Array, Array)#4 /usr/share/php/openmediavault/rpcservice.inc(125): call_user_func_array(Array, Array)#5 /usr/share/php/openmediavault/rpcservice.inc(158): OMVRpcServiceAbstract->callMethod('applyChanges', Array, Array)#6 /usr/share/openmediavault/engined/rpc/config.inc(224): OMVRpcServiceAbstract->callMethodBg('applyChanges', Array, Array)#7 [internal function]: OMVRpcServiceConfig->applyChangesBg(Array, Array)#8 /usr/share/php/openmediavault/rpcservice.inc(125): call_user_func_array(Array, Array)#9 /usr/share/php/openmediavault/rpc.inc(79): OMVRpcServiceAbstract->callMethod('applyChangesBg', Array, Array)#10 /usr/sbin/omv-engined(494): OMVRpc::exec('Config', 'applyChangesBg', Array, Array, 1)#11 {main}

So I tried sudo service avahi-daemon start. I get this:

Failed to start avahi-daemon.service: Unit avahi-daemon.service failed to load: Invalid argument. See system logs and 'systemctl status avahi-daemon.socet' for details.

I can take high resolution pictures of the screen if that helps with the commands you gave me? Thanks!

Hello everyone. I am new to linux and OMV. I have been learning a little at a time in Linux but it has been slow. In my search for a solid diy NAS system I foud OMV. I have been running this NAS system problem free for about 8 months. Recently I had tried to access my SMB shares via windows and they could not be found. When I signed into OMV webGUI, i saw that it was not mounted. when trying to mount it via webGUI, this is the error that I got:

Error #6000:exception 'OMVException' with message 'Failed to mount 'f9334705-f9f9-4ba0-bc8c-67b06b276ec2': mount: unknown filesystem type 'xfs'' in /usr/share/openmediavault/engined/rpc/filesystemmgmt.inc:921
Stack trace:
#0 [internal function]: OMVRpcServiceFileSystemMgmt->mount(Array, Array)
#1 /usr/share/php/openmediavault/rpcservice.inc(125): call_user_func_array(Array, Array)
#2 /usr/share/php/openmediavault/rpc.inc(79): OMVRpcServiceAbstract->callMethod('mount', Array, Array)
#3 /usr/sbin/omv-engined(494): OMVRpc::exec('FileSystemMgmt', 'mount', Array, Array, 1)
#4 {main}

I've tried rebooting with no success. I don't know many commands and searching did not resolve anything useful to me. I do have physical access to the machine and can enter commands right at the terminal.

My system has 4 WD Red drives 3TB each in RAID6. In the RAID Management tab, it shows State: Clean /dev/md0 Capacity 5.46TiB.
OMV Version is 3.0.2 (Erasmus). I'm not 100% sure if this was automatically updated and I'm unsure of the previous version I used to install this.

Let me know what other information I can provide and how to go about retrieving it and I will get it posted as soon as I can. Thank you all so much in advance for any help you can provide.

Kevin