Posts by TheLostSwede

Well, I just updated the driver, still can't add the card in the UI, nor make any changes through omv-firstaid...
Same error message.

The reason I upgraded the firmware is because Aquantia has had some issues with past firmwares and although things have worked, I've had issues with fairly high latency on these cards compared to normal Gigabit. Admittedly it doesn't really affect transfer between the NAS and my PC, but at the same time, I have a habit of keeping my firmwares up to date, regardless of the product. In many cases, it prevents security issues. Besides, I hadn't updated this card for the better part of two years, so I figured it was high time. And no, nothing went wrong during the firmware upgrade, as both cards are working and can communicate with each other.

The card clearly still works, the issue is with the error message I get when trying to make any changes through OMV.

So who am I supposed to contact if not OMV about the issue? Especially as having installed the latest drivers from Aquantia, solved nothing.
I thought the point of this forum, was to report issues and not having to use some third party service.

I really loath how hard it is to do, what should be simple things, like updating drivers, in Linux. Every time, I spend hours and hours doing simple tasks.
Beyond this issue, everything else, is mostly working, well, except every time there's an update for Docker, something breaks...

Sorry, I'm too attached to these cards, as I went through a whole heap of trouble getting them at the time.

And I hope you understand that although I'm venting frustration here, it's not aimed at you, since you actually try really hard to help people on the forums. I just find the way a lot of things are done the Linux world very frustrating.

Quote from ryecoaaron

File an issue on github. Until then, you can manually edit /etc/network/interfaces

You know, these are things "normal" people simply don't do.
I'm not a software developer. I just expect this stuff to work...

Well, I'm at a total loss, but I can't change any settings, which is annoying, as I wanted to change the MTU size, but as it's not possible to save any changes, or even add the specific interface in the UI...

Nothing change, the UI kind of hangs and tells me I need to save the settings, but it can't be saved, so I have to revert the settings.
OMV-firstaid comes out with the same "Failed to execute command" error.
enp1s0 is the Aquantia card.

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: enp7s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 1c:1b:0d:99:bf:cb brd ff:ff:ff:ff:ff:ff
3: enp0s31f6: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 1c:1b:0d:99:bf:cd brd ff:ff:ff:ff:ff:ff
4: enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 00:17:b6:00:18:29 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.250/24 brd 192.168.1.255 scope global enp1s0
       valid_lft forever preferred_lft forever
5: wlp8s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:28:f8:3b:d7:a6 brd ff:ff:ff:ff:ff:ff
6: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
    link/ether 02:42:6f:85:e2:65 brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
       valid_lft forever preferred_lft forever

I updated the firmware on my Aquantia card today and after that, I can't configure the card in OMV.
OMV-firstaid doesn't work either and I get the same error message there.
Everything seems to be working fine still, so not sure what's going on.
The card is not in the list of network interfaces in the OMV UI though.
Any suggestions as to what have gone wrong and how to possibly solve it?

Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; monit monitor collectd 2>&1' with exit code '1': Cannot create socket to [localhost]:2812 -- Connection refused


Error #0:
OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; monit monitor collectd 2>&1' with exit code '1': Cannot create socket to [localhost]:2812 -- Connection refused in /usr/share/php/openmediavault/system/process.inc:182
Stack trace:
#0 /usr/share/php/openmediavault/system/monit.inc(115): OMV\System\Process->execute()
#1 /usr/share/php/openmediavault/system/monit.inc(82): OMV\System\Monit->action('monitor', false)
#2 /usr/share/openmediavault/engined/module/collectd.inc(81): OMV\System\Monit->monitor()
#3 /usr/share/openmediavault/engined/rpc/config.inc(194): OMVModuleCollectd->startService()
#4 [internal function]: OMVRpcServiceConfig->applyChanges(Array, Array)
#5 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(149): OMV\Rpc\ServiceAbstract->callMethod('applyChanges', Array, Array)
#7 /usr/share/php/openmediavault/rpc/serviceabstract.inc(565): OMV\Rpc\ServiceAbstract->OMV\Rpc\{closure}('/tmp/bgstatus1H...', '/tmp/bgoutputhm...')
#8 /usr/share/php/openmediavault/rpc/serviceabstract.inc(159): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))
#9 /usr/share/openmediavault/engined/rpc/config.inc(213): OMV\Rpc\ServiceAbstract->callMethodBg('applyChanges', Array, Array)
#10 [internal function]: OMVRpcServiceConfig->applyChangesBg(Array, Array)
#11 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#12 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('applyChangesBg', Array, Array)
#13 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Config', 'applyChangesBg', Array, Array, 1)
#14 {main}

Quote from ColdShoulderMedia

Ya, I checked that in the specs previously.
That is the fastest ram which I can afford, do you really think it will be a bottleneck? I will get a second stick in the future if I need it, and then I'll gain some dual channel benefit, right?

Well, Ryzen 2000 might not be as sensitive to fast RAM as the Ryzen 3000 series CPUs, as AMD did a lot of changes to how the CPUs work. Bottle neck, well, maybe not, but you're not going to get the most out of that CPU with slow RAM. Again, it depends on how much it really matters to what your'e going to use your NAS for.

Just make sure the board+CPU combo supports ECC.
Even though AMD Ryzen supports ECC, it doesn't mean the motherboard makers have implemented support in the UEFI for it.
It wold seem you're ok with that combo though.
AMD Ryzen™ 2nd Generation/ Ryzen™ 1st Generation Processors
4 x DIMM, Max. 64GB, DDR4 3200(O.C.)/2666/2400/2133 MHz ECC and non-ECC, Un-buffered Memory

You're also going to want to sticks of RAM for optimal performance and ideally a bit faster RAM as well.

Except none of that works.
I wouldn't be here asking for help if that worked.

Quote from gderf

There is nothing in SnapRAID that can prevent access to your data. If you can't access the data on your remaining data drives, then something else went wrong. You should also remove the failed drive from your UnionFS pool. Don't run ANY SnapRaid commands until you are positioned to recover the lost drive or are able to reconfigure it properly per the manual and FAQ.

Again, the manual as is as helpful as not at all.
The drive has already been removed, both from SnapRAID, UnionFS and the disk management interface on the NAS and physically removed, packaged up and sent off for RMA. It's the only way I'm going to get a replacement drive.
I just don't know how to remove it from the config file, which is what I need help with at this moment.

Quote from gderf

You don't have an adequate understanding of SnapRAID. Please read the FAQ and manual.
Not all that can be or needs to be accomplished in SnapRAID can be handled in the GUI. You are going to have to use the command line and editor.

Which is why I'm asking for help here. The manual is pure nonsense to me at this point, so reading it, isn't helping as I can't find the answers I need.

Quote from jollyrogr

TheLostSwede,
If availability is an issue, perhaps regular RAID would better suit you, although in either case if you're not prepared with replacement drives you might be in over your head. Businesses and networks that employ RAID systems don't wait to RMA a drive. In fact, they won't bother with a refurbished drive period. When a drive fails, a new one goes in and they move on.

As was stated earlier, you can change your array from 3 drives to 2 and re-sync, but you'll need to read the manual and will have to use the command line.

My recommendation would be to get a new drive ASAP and get your array repaired. Then RMA the bad drive and when its replacement comes, keep it for a spare for use in times like these.

No, regular RAID is too much of a risk if a drive fails, as I only have a four bay NAS. Not everyone has the cash to have spare drives sitting on a shelf, unfortunately and this is why I picked something else, that was supposed to give close to the same redundancy, but clearly it doesn't work as promoted.

Well, how? This is the problem, I can't figure out how and the so called manual doesn't provide instructions. I can get around in Linux, but I'm far from an expert at it and these kind of things makes me just want to throw it all out. It really gets to me that Linux is so convoluted when it comes to things that should be fairly logical to do and it's not the first time I've run into issues that apparently no-one else is having or simply aren't documented at all.

Again, I don't have the cash to get another drive. I've already RMA:ed the bad drive, but it's going to take a week or two to get that back.

So again, to my question, how do I shrink the SnapRAID to three disks so I can access my data?

Quote from jollyrogr

I think what you did is fundamentally incorrect. You should have copied the data to a new drive and then replaced the failing drive with the new drive in the snapraid array. Then you could run a check and sync and be good to go.
Since you did what you did, now you have a whole bunch of data out of place in your array. Assuming you haven't synced, (it seems snapraid is protecting you from doing so) you can still replace the failed drive and copy the data back and check/fix the array or simply replace the drive and fix the array in which case it will rebuild that drive using the parity but that will probably be slower.

Or follow the instructions at the link gderf posted to decrease your array by 1 disk. You will not have parity protection until the resync is complete.

And if you don't have a new drive? I need to RMA my drive. I only have these two drives to copy the data to, as the fourth drive is the parity drive.

I need access to my data while I RMA my drive, otherwise running any kind of silly crap like this is pointless. It's supposed to protect my data, no? Not make it inaccessible.

Quote from gderf

Instructions not missing. Here are the steps from the FAQ.

• Change in the configuration file the related "disk" option to point to an empty directory
• Remove from the configuration file any "content" option pointing to such disk

And how do I do that from the OMV GUI? The config file is all greyed out...

Quote from gderf

Not correct. See:
https://www.snapraid.it/faq#remdatadisk

If only that worked. See first post.
The instructions on how to change the config file is also missing, which is kind of a critical part.
Just deleting the drive details doesn't work...

I haven't lost any data, as I copied it over from the failing primary drive to the secondary (empty) drive, in the SnapRAID, but apparently SnapRAID doesn't want to play along with that, even though that seems to be what their instructions tells you to do in case of a drive failure.
As such, all the data is there, but because I can't remove the failed drive somehow, I can't sync and make SnapRAID understand that the data is there.
There are also zero instruction on how to remove a drive from SnapRAID, only how to replace one.
I have more than enough empty space on the other two drives for the data, but apparently that's a no go...

So, it turns out one of my drives are failing and I need to send it for RMA.

My problem is that after having removed the drive from the system, having first copied all the data to a different drive in the SnapRAID, 1. SnapRAID is refusing to behave 2. even though I deleted the drive in the OMV GUI, SnapRAID says the drive is missing and I can't sync which leads to 3. my data is inaccessible, despite being on the drives.

I removed the hard drive both in the SnapRAID UI and unders Disks. So what am I supposed to do now to make it all work again, as there are no explanations on how to actually remove a drive in the SnapRAID manual, it just tells you how to replace one. Does this mean my NAS is out of commission until my replacement drive arrives? If so, then SnapRAID is mostly pointless, as it caused more headache than it's supposed to solve.

root@OMV:/srv# snapraid sync -E
Self test...
Loading state from /srv/dev-disk-by-id-ata-TOSHIBA_HDWQ140_Z79ZK0SYFPBE-part1/snapraid.content...
Decoding error in '/srv/dev-disk-by-id-ata-TOSHIBA_HDWQ140_Z79ZK0SYFPBE-part1/snapraid.content' at offset 90
The file CRC is correct!
Disk 'sda' with uuid 'a5751f9a-7dbe-4afe-abc3-11bc406d4c66' not present in the configuration file!
If you have removed it from the configuration file, please restore it
root@OMV:/srv#

This helps me how?

Ok, I'm once again having some really odd issues.
SnapRAID is telling me to fix some issue by running snapraid -e fix, which comes up with an input/output error.
I try to delete the file in question, as it's only one file, which locks the drive and puts it a read-only file system mode.
WTAF is going on here?

Using the commands here OMV is suddenly read only unlocks the drive again, but I can't fix the problem, as it goes in a loop like this.

Quote from ryecoaaron

4.19 backports kernel?

Yes

Well, one of the drives has a SMART flag for some bad sectors, which is odd, as the drives are all fairly new.
No other issues with the hardware.
I keep getting hit with various issues that prevents me from writing data to the drives though.
It seems after the Kernel update, I got hit by the user permission issue again, reset user permissions and it mostly works.
Also had issues with Dockers not being given write access to the drives, but restarting the docker seems to have solved that.

Kernel update today, rebooted and system goes into read only mode.
I still need some help in solving this, as I have no idea what's going on.
Even running the command I found in the other thread doesn't seem to solve the problem now.
Desperately need to know what's going on and how to solve it.

My OVM box has been running rock solid for months now, but this is the second time I'm having issues with shared folders after installing some updates.
I can no longer write to my shared folder and Windows is telling me I don't have the correct user privileges. Yet this has worked fine until today, except a small hitch a month or two ago.
I've tried resetting the permissions at no avail.
I can't upload files to the shared folders using FTP as root either (yes, root login is enabled).
The weird thing is, I can delete files in the same folder from Windows, no problem at all.
Any suggestions on how to solve this issues?

On top of this, I can't assign a new share to the directory on its own and I get the following error message.
If I'm reading that correctly, the file system is read only, but that shouldn't be the case and how would I get it back to a normal file system?
I should mention I use UFS and SnapRaid.

Edit: Never mind, solved it by running the commands here - OMV is suddenly read only

Edit 2: Had a power surge later on in the same day which caused the NAS to reboot (first time I've had a power surge in forever, might need to get a UPS). The file system reverted back to read only after the reboot. Any ideas what's going on? Running the commands in the link above and rebooting seemingly solved the issue, until I ran the SnapRaid Scrub which put the NAS into read only mode again.

Edit 3: Another power surge and it's clear it's not the rebooting that's the issue, it seems to be related to SnapRaid somehow. Every time I run a check with SnapRaid, it puts the file system into read only. Any ideas?