Posts by Sui_Generis

Yup, having the exact same problem.

Have tried both bare metal on a Dell PowerEdge T110 ii & PERC H200 (flashed to IT mode) and in VMWare 16 with the same results.

No additional plugins installed, just updates run.

Hey OMV Guru's, quick question for your all.

So, I'm planning on having a few external USB drives (HDD's) to backup my central stuff on my OMV server, one external drive per one internal drive, so the external is an exact replica of the internal.

My question is this.

If I go down this route, is OMV/USB Backup using /dev/ identifiers or UUID's? Since I will be using multiple drives what I don't want to happen is two or more external drives (only one drive will be connected at any one time) to end up with the same /dev/sdx identifier and thus overwrite whatever is on disk B because it thinks it's disk A.

Any update to this?

5.8 is on Buster and collectd themselves put out 5.9 in June, but we're still on 5.7?

Morning all,

I'm having some headaches with trying to get scans to work using Clam via the OMV-Extras plugin, would keep giving me a permission denied error.

Trying to fix this, I uninstalled and reinstalled Clam (didn't fix the original problem at all), but I forgot to remove the scheduled scan I was trying to run.

Now when I try to create the task again it tells me that the configuration object already exists.

How can I get rid of said objects manually?

As always I appreciate any light you can shed!

Dem

Quote from kfczingerbox

@Sui_Generis okay so the nas is connected to a router/modem and it has a spare gigabit Ethernet card, as does my main pc, i was thinking that it would be faster to connect them with the ethernet cable then to transfer files over Samba so i want to do this this https://techwiser.com/how-to-connect-pc-to-pc-lan-cable/

Ahh, I think I understand what you're getting at.

You want to use the direct connection because I'm guessing your router is 10/100, and the direct connection would give you full gigabit speeds for file transfers?

You can join two machines directly using something called a crossover cable. However, you would still need a Samba share set up, like @flmaxey said, as a 'file translator'.

You would also need to manually assign all the IP information for both machines, given you would be connecting them directly and there would be no DHCP server to assign that.

I have to say though, I've never done a direct cable connection between two machines, let alone when they were already connected to another network. In theory it should work, but I'm I'm not certain I'm afraid.

Perhaps someone with more knowledge than myself will be able to step in.

Sui

I'm a little confused by the question.

You want to transfer files to your NAS from your main PC...directly?

I'm assuming you have a network set up, with a router in place, otherwise there wouldn't be much point to having a NAS.

So why not just set up a Samba share?

Seeing as no one seems to be willing to step forward with the "Complete Idiots Guide to Setting Up OpenVPN On OpenMediaVault", I've had to go ahead & write my own.

I hope this helps anyone who, like myself, is a Linux novice and a OMV noob.

• Install OpenVPN on your OMV system, either directly or via SSH
  apt-get install openvpn
• Download the configuration files for your particular VPN (in my case PIA) using wget, they should be available from your providers website
  Please note that the following URL is for the secure PIA OpenVPN files, if you are not using PIA these will be of no use to you, but I'm leaving the URL in as an example.
  wget https://www.privateinternetaccess.com/openvpn/openvpn-strong.zip
• In my case, I had to install unzip to extract the contents of the .zip archive
  apt-get install unzip
  I then made a directory to extract the files to
  mkdir ~/<directory_name>
  and extracted with
  unzip <filename>.zip -d ~/<directory_name>
  Your mileage may vary here, as you might have downloaded your OpenVPN configuration files archived in a different way.
• Change directory to where you just extracted the files to
  cd ~/<directory_name>
• Copy the .crt and .pem files, as well as the .ovpn file of your choice to /etc/openvpn
  cp <filename>.crt <filename>.pem <filename>.ovpn /etc/openvpn
• Make a file to store your VPN login information in
  nano /etc/openvpn .secrets
  and enter your username and password into it in order
  <username>
  <password>
  save and exit nano
• Open the .ovpn file you copied using nano and change the line
  auth-user-pass
  to
  auth-user-pass .secrets
• Rename the .ovpn file to .conf
  mv <filename>.ovpn <filename>.conf
• You can test your OpenVPN connection at this point by running
  openvpn --config <your_config>.conf
• If you want your OpenVPN connection to run at startup, add the following systemd entry
  systemctl enable openvpn@<name_of_your_conf_file>.service
• Reload systemd
  systemctl daemon-reload
  and start OpenVPN service
  service openvpn start

Reboot your system, and your OpenVPN connection should automatically start.

This is my very first tutorial on anything Linux wise, so I hope the format and instructions are clear enough, and I really hope it helps someone out.

Sui

Good evening all,

My OMV 4.x box has been purring away quite happily for the last few months, even has it's first storage drive and is actually doing something at last!

I would like to connect it to my Private Internet Access VPN to use it as a centralised Transmission hub, but I've no idea where to start.

Does anyone have a complete idiots guide to doing such a thing?

Thanks in advance.

Sui

Evening all,

I've finally added the first drive to my NAS build, after it just running the OS drive for the last month or two (was having some stability issues caused by an iffy PSU) and have found an interesting quirk/problem...of sorts.

The first drive added to the system is a Western Digital 4TB Red - WD40ERFX on a Syba SI-PEX40064 SATA3 card which uses the Marvell 88SE9215 chipset (I'm using an old 775 board, no SATA3 and only 4 ports onboard).

I copied over 2.10TB of stuff to the drive without issue using FreeFileSync from my HTPC.

However! When I checked the SMART logs (just for the sake of checking), I found I had an error...at the exact time of checking the log.

I checked again a day or two after, got another error, again at the exact time of checking the log, see the below extract from the SMART Info;

Error 2 [1] occurred at disk power-on lifetime: 38 hours (1 days + 14 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
04 -- 51 00 0b 00 00 00 00 00 00 00 00 Error: ABRT

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
b0 00 d5 00 01 00 00 00 c2 4f e1 00 08 1d+14:55:27.743 SMART READ LOG
b0 00 d5 00 01 00 00 00 c2 4f e1 00 08 1d+14:55:27.742 SMART READ LOG
2f 00 00 00 01 00 00 00 00 01 04 40 08 1d+14:55:27.711 READ LOG EXT
b0 00 d6 00 01 00 00 00 c2 4f e0 00 08 1d+14:55:27.710 SMART WRITE LOG
b0 00 d6 00 01 00 00 00 c2 4f e0 00 08 1d+14:55:27.709 SMART WRITE LOG

Error 1 [0] occurred at disk power-on lifetime: 12 hours (0 days + 12 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
04 -- 51 00 0b 00 00 00 00 00 00 00 00 Error: ABRT

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
b0 00 d5 00 01 00 00 00 c2 4f e1 00 08 12:33:09.171 SMART READ LOG
b0 00 d5 00 01 00 00 00 c2 4f e0 00 08 12:33:09.171 SMART READ LOG
b0 00 d5 00 01 00 00 00 c2 4f e1 00 08 12:33:09.171 SMART READ LOG
b0 00 d6 00 01 00 00 00 c2 4f e0 00 08 12:33:09.170 SMART WRITE LOG
b0 00 d5 00 01 00 00 00 c2 4f e1 00 08 12:33:09.170 SMART READ LOG

So, it looks like accessing the SMART info, is actually causing a SMART error. O.o

Now, while I have no doubt that my drive is working absolutely fine, what's causing this SMART logging issue when I read the log it's self? Is there any way of stopping it? And moreover is it any sign of potential instability?

Thanks in advance.

Good morning all,

Having brought a Dell PowerEdge T310 a few weeks ago that failed to meet my requirements miserably (well, the Perc 6/i card specifically), I decided to go back to basics as I am going to be a very basic NAS user!

I dug out an old 775 board I had kicking around (Bad Axe 2 anyone?) because it has 8 SATA ports, unfortunately 4 of those rely on a Marvell RAID chipset that I just could NOT get to work on any flavour of Linux.

So I turned off those 4 ports in the BIOS & brought a cheap SATA III card (Syba SI-PEX40064) running on the Marvell 88SE9215 chipset (yes I know, it's cheap & nasty, but it works...)

Now, this is NOT a RAID card, in any way shape or form, it's purely pass-through.

I currently have the boot drive (64GB SSD) running off it as well as an old 150GB Raptor X (complete with translucent top window so you can see all the gubbins whizzing around! Ahh memories...) for testing.

OS drive is, as you would expect, /dev/sda

However, any other drive I configure seems to insist on being software RAID through MDADM, mounting the Raptor X as /dev/md126

Is there any way around this? I really don't want anything to do with RAID in any way, software or otherwise.

::EDIT::

Ok, you can ignore ALL of the above. After powering the system off, connecting a third drive (os + two test disks) and booting up again, the two test disks are now detecting normally as /dev/sdb and /dev/sdc

Well, that was weird.

Sui

Thanks for your input guys.

I've brought the server into work so I have access to more drives to load it with to test and have done a fresh install of OMV3 to see if that makes any difference.

Alas...

I've attached a screenshot of the S.M.A.R.T. page from the web interface as well as terminal outputs from both MegaRAIDsas-status and smartctl on one of the drives attached to the RAID controller.

I've put two 80gb drives on the RAID controller, as individual "RAID0" arrays. The controller doesn't see the drives at all unless they are configured as RAID in one way shape or form.

Ignore the red warning on the Toshiba drive, that is connected to the native SATA interface and was just something I picked up off our pile of drives to test & wipe to do the test installation of OMV3.

Sui

::EDIT::

This may be a facepalm moment. Having actually read through the output from smartctl, I see now that it mentions "SMART Status not supported: ATA return descriptor not supported by controller firmware", have a horrible feeling here that it is literally that, live status not supported.

A very good evening to you all!

I've just started putting my NAS together using a Dell PowerEdge T310 with a PERC 6/i RAID card (after I brought it I found that the PERC 6/i is limited to 2tb drives, but that's ok, I'm working around it), but I've run into a little issue.

I can't get the web interface smart monitoring to register the (test) drive on the RAID controller.

Disk is configured as a Raid 0 array on it's own (going to use 4 single virtual disks, no actual RAID in either hardware or software), the web interface says the status of the drive is "unknown". Attempting to make a scheduled test and run it gives me an error of "unable to open device" and tells me to manually add device parameters for "megaraid".

SHH'ing into the box and running smartctl with the "-a -d megaraid,0 /dev/sda" parameter gives me full S.M.A.R.T. information for the connected drive.

But how do I get this to be implemented through the web interface?

I should probably also add I've gone ahead & added the "hwraid" repo in and installed all Megaraid related tools.

Thank you for any help you may be able to provide in advance.

Sui