Yes that seems to work. Thank you.
Posts by clickwir
-
-
Pretty simple, I installed OMV 6.0.12-1 in a VM today. Don't want or need IPv6 on any of them right now, so it's pretty standard practice to disable IPv6 in grub (/etc/default/grub and add 'ipv6.disable=1' to the linux default line). But on reboot I noticed a console message about something failing to start.
Turns out it's the webserver. Can't get to the web admin interface when IPv6 is disabled. I re-enabled, rebooted and it was fine. Disabled, rebooted and couldn't access it. I would like to be able to disable IPv6 and still use the system.
This was in syslog, not sure if it's an important part.
Feb 13 15:30:11 nas monit[434]: 'nas' Monit 5.27.2 started
Feb 13 15:30:11 nas monit[434]: 'nginx' process is not running
Feb 13 15:30:11 nas monit[434]: 'nginx' trying to restart
Feb 13 15:30:11 nas monit[434]: 'nginx' start: '/bin/systemctl start nginx'
Feb 13 15:30:11 nas systemd[1]: Starting A high performance web server and a reverse proxy server...
Feb 13 15:30:11 nas nginx[733]: nginx: [emerg] socket() [::]:80 failed (97: Address family not supported by protocol
)
Feb 13 15:30:11 nas nginx[733]: nginx: configuration file /etc/nginx/nginx.conf test failed
Feb 13 15:30:11 nas systemd[1]: nginx.service: Control process exited, code=exited, status=1/FAILURE
Feb 13 15:30:11 nas systemd[1]: nginx.service: Failed with result 'exit-code'.
Feb 13 15:30:11 nas systemd[1]: Failed to start A high performance web server and a reverse proxy server.
-
Code
Display MoreReading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: openmediavault 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/2,348 kB of archives. After this operation, 0 B of additional disk space will be used. Preconfiguring packages ... (Reading database ... 51054 files and directories currently installed.) Preparing to unpack .../openmediavault_6.0.5-3_all.deb ... Unpacking openmediavault (6.0.5-3) over (6.0.5-2) ... Setting up openmediavault (6.0.5-3) ... Creating configuration database ... Migrating configuration database ... Setting up Salt environment ... [ERROR ] Command '/usr/bin/patch' failed with return code: 1 [ERROR ] stdout: patching file /tmp/__salt.tmp.b27_94h1 (read from /lib/python3/dist-packages/salt/fileserver/roots.py) Reversed (or previously applied) patch detected! Skipping patch. 1 out of 1 hunk ignored -- saving rejects to file /tmp/__salt.tmp.1b0lz0ad [ERROR ] retcode: 1 Processing system modifications ... Processing triggers for rsyslog (8.2102.0-2) ... Processing triggers for openmediavault (6.0.5-3) ... Restarting engine daemon ... Updating workbench configuration files ...Just did a run of the mill 'apt update && apt dist-upgrade' and saw this error. I don't understand what it means, if there's actually a problem and if I need to do anything.
Other than that ERROR, the update seemed to go ok. Can login WebUI, NFS seems fine.
-
Mine doesn't show BTRFS or 'normal' information there, never has. Maybe because they are QEMU Disks?
I've gotten used to OMV not showing this entry correctly; it's been like this for several years.
-
Tried again, from a different system with Firefox same error.
Tried from mobile, same error.
I have never accessed OMV from either of those systems.
Restarted the Proxy after clearing cache, watched for cache_hits and they were all cache_miss.
It's coming from somewhere, I don't know where.
-
Reasonable to one may be unreasonable to another. Since it's basically always using CPU time, it doesn't allow the CPU to clock down and use less power as often.
It's not nothing, that's my point. The old screen used nothing, now it's using something.
Granted, it's not --much--, but it's more than zero.
Again, I like it, just think it should stop at some point.
-
6.0.5-2 (Shaitan)
Linux 5.14.0-0.bpo.2-amd64
Just upgraded today.
Normally I use Firefox, tried in Private window and got the same error.
Tried in Chromium Incognito, also same error.
-
First, I know my setup is a bit out of the norm. OMV is a VM on Proxmox and I'm doing single disk passthrough, not HBA. So OMV sees QEMU disks.
On this I have BTRFS, then OMV is sharing it out to things like NFS. Fairly simple, but not normal.
Doing to <Storage>, <File Systems>, I see 1 entry. Which is correct, that's my BTRFS RAID. I'm used to it not showing up correctly and OMV not knowing how to handle it.
However, if I click on the row with the filesystem and click <Edit>, I get a crash.
Again, I know it's out of the ordinary so this might be a non-issue. But I thought it best to bring it up and maybe a more graceful situation can be thought out. -
Just updated to OMV 6 RC1, everything went easy. After poking around for a bit, I logged out and went about my business. At some point I noticed Firefox using 8% CPU, even with very few tabs open and doing nearly nothing. Turns out it's the animation on the login screen for OMV.
It's beautiful and I like it, but can we have it stop after a few zooms? Or an option to disable it?
I prefer to always keep a tab open of OMV sitting at the login screen, but I don't want to have it using up CPU time like that.
-
Don't be worried about the thermals or longevity, they are put in those cases and meant to run for many years. It's fine.
Spin down if you want, but you aren't extending the life of the drive.
Next, usually USB obscures the SMART system. Generally SMART via USB does not work.
-
That status page isn't the best, granted.
However, many people have tried to get failures with raid56 and have not. It just works.
I've been using single drive, RAID1 and RAID10 for many years and it's never has any issues.
-
btrfs has lots of great features and is far more future proof than ext4.
It does not need maintenance, but it doesn't hurt to have some scrubs scheduled.
-
That would make sense why it didn't work or reflect the change.
Any plans to have more support for SAS?
-
Keep in mind those are specific stress tests. They are looking for limits.
I've used the car analogy many times. Car A has a top speed of 250mph. Car B, 240. Car C 180.
The vast majority of the time and and vast majority of people will never hit those limits. They will never see a performance difference because they aren't running simulated workloads back to back and graphing the results.
It's not an exact comparison; it's easier to hit limitations on computer hardware than a super fast car. But it helps to bring the thoughts out.
I've been using btrfs for years under many different hardware and software setups. It's never been a concern of speed for me. Btrfs has always performed great, usually if I'm hitting some limit it's not because of btrfs.
That said, btrfs has many more modern features that really should make it the default filesystem used for most systems.
-
FWIW, how I would do it would be like this: copy data off to another location. Create new ext4 (btrfs is what I would use) file system. Copy data back.
You could probably even use the same path names after as well so you wouldn't have to update all the things pointing to it.
-
Some years ago, btrfs devs suggested NOT to convert from ext4 anymore. Somewhere around that time I used it and it worked fine. But since seeing them say that, I haven't used it since.
To proceed here: copy data off, create btrfs file system, copy data back.
-
Have OMV 5.3.2 installed as a VM in Proxmox. 4 SAS drives are passed through (with scsiblock=1).
Running 'sdparm -g WCE /dev/sdb' shows that Write Cache is disabled.
Go into the WebUI and enable Write Cache for the same drive (save and apply), sdparm still shows it disabled.So I used 'sdparm -s WCE --save /dev/sdb', then check what sdparm shows and yes it reports that it is enabled. WebUI shows it's disabled.
Should OMV work with SAS drives and Write Cache through the WebUI? -
So poking around in there I see 3 things referencing the filesystem in question.
Not sure what I should do with them though.
Code: config.xml
Display More<mntent> <uuid>cc425a4c-2faa-4294-8f9a-e1cef0d26c51</uuid> <fsname>/dev/disk/by-id/scsi-0QEMU_QEMU_HARDDISK_drive-scsi4</fsname> <dir>/srv/dev-disk-by-id-scsi-0QEMU_QEMU_HARDDISK_drive-scsi4</dir> <type>btrfs</type> <opts>defaults,nofail</opts> <freq>0</freq> <passno>2</passno> <hidden>0</hidden> </mntent> <mntent> <uuid>fd489af3-e460-488f-99df-a1696fe712a3</uuid> <fsname>/srv/dev-disk-by-id-scsi-0QEMU_QEMU_HARDDISK_drive-scsi4/Data</fsname> <dir>/export/Data</dir> <type>none</type> <opts>bind,nofail</opts> <freq>0</freq> <passno>0</passno> <hidden>0</hidden> </mntent> <mntent> <uuid>8ce35c05-b4d3-4a54-9b0c-8cf24878feb4</uuid> <fsname>/srv/dev-disk-by-id-scsi-0QEMU_QEMU_HARDDISK_drive-scsi4/utilities</fsname> <dir>/export/utilities</dir> <type>none</type> <opts>bind,nofail</opts> <freq>0</freq> <passno>0</passno> <hidden>0</hidden> </mntent> -
The error message indicates that there are more than one moint points for this device which is WRONG. You need to modify the database manually to fix that.
Where is the db? Sorry, not done that before.
-
I like the thought of having a auto backup in case one drive is faulty. If for what reason a file is deleted by accident it still is available in the waste bin.
RAID is not backup.
Backup is not RAID.
Trash/Waste/Recycle bin, is not backup.
This short video covers some of the high points.
External Content www.youtube.comContent embedded from external sources will not be displayed without your consent.Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.To your original question, some motherboard (fake) RAID solutions can still pass through the drives connected without adding an abstraction layer. This can get confusing because it could be doing a RAID1, but you would expect to only see one drive. It may in fact be doing a RAID1 but not hiding the other drive from you. This could cause you to be able to use both drives for different things. This would be bad.
The suggestion is to remove the motherboards RAID settings, make sure it's not doing anything. Delete the RAID set it created, if it actually created one. Then use OMV to RAID the drives together.
Remember, RAID1 is protecting uptime and availability. Backups protect data. That's a BIG difference and understanding that is important.