omv-extras 5.2.5 fixes the systemrescuecd ssh issue. sshd was running but systemrescuecd 6.0.4 added a firewall. I added nofirewall to the boot arguments and it works as expected. Just click install systemrescuecd again.
Thanks for updating systemrescuedcd. Probably you should not update that component, it's just a rescue CD 
Regarding the mergefolders issue, I had the feeling this wasn't enough.
If I will play with it in the future I will let you know.
Whilst I was setting up my new OMV system, I wanted to give a try to openmediavault-mergerfsfolder, instead of using the "old" openmediavault-unionfilesystems.
Well, it's been a nightmare: it crippled my OMV installation twice before I realised it.
Disclaimer: I don't have many details and I don't want to replicate the issue because I already wasted a lot of time, but I thought was still worth reporting the issue.
OMV: 5.3.3-1
openmediavault-mergerfsfolder: 5.0.1
I installed OMV along with many plugins: backup, usbbackup, flashmemory, snapraid, resetperms, diskstats, wakealarm and mergerfsfolder.
I didn't configure most of them and didn't make any weird change to the system.
I configured mergerfsfolder to merge two main folders from different drives. Yes, I used /srv/dev-by-disk-by-label-XXX .
It seemed to work fine, I could see the new filestystem, browse it via WinSCP, mount it in SMB and do all sort of things.
Until I rebooted the system.
I thought was my fault. Before rebooting I also updated from 5.3.2-1 to 5.3.3-1, so I thought this could have caused the issue.
I had to start all over again, because I hadn't made a backup yet ( 
),
This time I configured everything but mergerfsfolder, and made a backup first. Rebooted, everything went fine, so the backup was healthy.
I configured mergerfsfolder and as before I could use correctly the merged FS.
Rebooted and bang! The same issue.
I managed to remount the root fs via the command above, install systemrescuecd and boot to it. By the way, it does not start ssh automatically (nothing was listening on port 22 but the system was connected correctly as I could ping it)
I restored the backup, removed mergerfsfolder and installed unionfilesystems.
I configured unionfilesystems, rebooted and everything has been working great since then.
Sorry for the rant, I hope this will help.
As said and shown, postfix is already configured to handle such situations. The question now is why it does not work.
Hey, just wanted to let you know the issue does not occur any more.
Cron jobs are now received with the sender Cron Daemon, so I think it is working correctly now.
After reporting the issue here, I managed to replicate the issue in my following test installs, but it's been a while I haven't seen the issue.
This is drawback of omv vs synology or qnap... Why i so hard to have a file manager on omv ??? This method (mc over ssh conection or another method ... ) request that on every pc you try to connect to omv to have or install putty or winscp....
Too bad
Sent from my GM1913 using Tapatalk
Use Krusader in Docker as suggested by @KM0201. I've quickly tested and works quite well. You have the complete GUI as it uses VNC.
It's the most complete I've tested so far.
(I don't want to use SSH over the internet)
Thanks, will try your suggestions!
I think I've found a good File Manager:
https://filerun.com/
It can be installed via Docker, obviously.
Do you have other options?
Hi all,
Coming from a Synology NAS, there is one thing I still haven't found a replacement for: their web based File Manager called "File Station".
I am going to use NextCloud for general usage and sharing, but it's not so focused on file management tasks like "File Station" or a real file manager is.
As an example, Nextcloud by default doesn't extract archives, and even with the plugin enabled its support is somewhat flaky.
Do you have any suggestions or tackle the issue in a different way? I got used to a such powerful tool In a web browser!
Seems that Votdev has fixed the issue with this commit
https://github.com/openmediavault/openmediavault/pull/616
Yeah
Display Moremin receivefile size = 16384
write cache size = 524288
getwd cache = yes
socket options = TCP_NODELAY IPTOS_LOWDELAY SO_RCVBUF=65536 SO_SNDBUF=65536
log level = 1
read raw = yes
write raw = yes
max xmit = 65535
dead time = 15
I am jumping in this conversation because I would like to know where did you get these extra options and if they are actually useful. So far I've only enforced SMB2 and above.
EDIT: I don't have technical experience with these parameters, but after few readings seems like that most of them are unnecessary or debatable. What is the performance without them?
The issue must be fixed upstream (Debian or smartmontools). The OMV project can't do anything here. SImply create a filter rule in your email client that redirects those emails into trash in the meanwhile.
I already updated smartmontols to the actual latest version for another issue - wasn't detecting the NVMe drive for SMART reads, so it has something to do with Debian.
Personally, I don't think you need smart for nvme especially if you leave some unpartitioned space on the drive. Most nvme drives are rated to write their entire capacity at least once a day for at least a few years. You should never hit this unless you are doing something crazy with it. If you just check the life left every six months after about 3 years, you would be probably know when it is going to need to be replaced.
Thanks for this advice, I will leave some unpartitioned space on the drive, disable SMART reading and rely on the hdsentinel tool to send me scheduled emails.
Hi,
OMV5 (5.3.2-1) is logging a "useless" NVMe property that leads to scary SMART alert emails that make me worry for no reason.
Here is what I am talking about.
This message was generated by the smartd daemon running on:
host name: [blip]
DNS domain: [blop]
The following warning/error was logged by the smartd daemon:
Device: /dev/disk/by-id/nvme-SPCC_M.2_PCIe_SSD_SerialNumberRemoved, number of Error Log entries increased from 40 to 42
Device info:
SPCC M.2 PCIe SSD, S/N:SerialNumberRemoved, FW:ECFM13.1, NSID:1, 256 GB
For details see host's SYSLOG.This drive is new, and I've checked its health with other tools, and obviously it's doing great.
The report is referring to Error Information Log Entries. A quick search reveals it is not due to the drive health.
Some interesting discussion here from bugs.debian.org.
I am no expert of this tool but does somebody know what could be done, like tellling the utility to ignore this value (maybe it's not NVMe aware)?
Honestly I want SMART enabled for this drive, but only for real warnings.
Hi,
I just installed OMV5 on my shiny new build and I have spotted this error coming up frequently in logs:
systemd[1]: /lib/systemd/system/nmbd.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/samba/nmbd.pid → /run/samba/nmbd.pid; please update the unit file accordingly.It's so frequent that appears in every log page.
- Samba is not (yet) enabled
- The installation is pretty clean, I haven't messed with any system file (yet)
- I am running OMV 5.3.2-1
I believe it's just a warning but it's very annoying. I have found some reference here, but should this be fixed?
Debian not OMV but 7.1-1 is in backports but not pinned. It will be installed if you install proxmox kernel as well since 7.1 is in the proxmox repo. You can install from buster-backports with: apt-get install -t buster-backports smartmontools=7.1-1~bpo10+1
Thanks for the advice, will try tonight.
Since OMV got the 5.4 kernel officially, I thought there was no need for proxmox kernel. Do you still recommend it? I see proxmox it's 5.3 though
it works in the shell with this command
smartctl -x /dev/nvme0
This specific SMART issue is because smartmontools is not updated in OMV5. The bug has been solved by smartmontools team, but the updated version is not showing up. Found it out just a while ago.
NVMe SMART status reading failure (wrong drive name)
Hi,
I am sorry to reply to an old thread, but the issue still exists in OMV5, I am currently running 5.3.2.1 and have the exact same issue as OP:
smartmontools version is 6.6.-1. The issue has been fixed by the smartmontools team, but OMV does not pick up the updated package.
This is a newly installed system.
That's a great idea! Please make it for OMV 5 too!
The U-NAS NSC-400 looks good but in Germany I can't find a seller.
@thedarkness
Is the height of the Fractal Design Node 304 21cm with or w/o feet?
It's 21cm with feets. Without I don't think it will reach 20.
Display MoreI have a U-NAS NSC-400
It has 4 x 3.5"/2.5" front bays and space for up to 2 Internal 2.5" disks
It is 19cm wide, 18cm high and about 25 deep
It is a good case and silent enough (on high CPU load the fans do ramp up and it is pretty audible but when in idle i cannot hear it unless I am about 10cm from it)
Availability is a problem, though...
Did you pay 150$ for it?
Although looks well made, I think it's a bit expensive 
By the way, I'm in the process of assembling my new NAS with the Node 304. When the fans are set at minimum via the controller, I can't hear a thing. It's so silent that the first time I booted the system I thought I was missing some fans (Obviously withouth HDD at the moment).
I'm in love with it.
Display MoreThanks.
I had already looked at the Fractal Design Node 304.
Unfortunately it is 25cm wide, but alternatively I could put it on its side and put rubber feet below.
Are the feet removable so that the height can be reduced to 20cm?
With 21cm width I found also the Coolermaster Silencio S400. What do you think about this?
(Actually I prefer 20cm maximum width to have 1cm space in between.)
Well the Cooler Master looks a bit overkill.
Yes, you could remove the rubber feets, they are sticked with simple glue.
I had a space problem like yours: shelfs were only 20cm away and the Node 304 didn't fit. I looked for other cases, but no alternative.
I solved the issue by changing furniture unit in my living room 
I've been testing OwnPhotos.
It's promising, but rough.
Requires a lot of resources, uses 4 GB of RAM during my testing, becoming the heaviest container/app I've ever tried.
SSD is a must to store its DB and thumbnails.
Has a AI to recognize people but obviously needs a lot of training.
I didn't know about PiGallery2, I really like the UI from the screenshots! Will try it out.
