Balrog
-
Content Count
118 -
Joined
-
Last visited
-
Days Won
1
-
data deduplication
Balrog replied to Aigor's topic in General Post-Installation Questions/Discussions (non-hardware specific)
I have played around with deduplication and btrfs in the past. Even with good results. But as dedup & encryption is not compatible and also one never does run a defragmentation or the deduplication will be destroyed I deleted my tests. Deduplication is a very interesting feature for me but only if it's supported neat. -
I have some news about other log entries which are anyoing and useless: The open-vm-tools package logs every 30 seconds this: root@ds:~# tail -f /var/log/vmware-vmsvc.log [Oct 09 19:50:17.681] [ warning] [vmsvc] HostinfoOSData: Error: no distro file found [Oct 09 19:50:17.681] [ warning] [guestinfo] Failed to get OS info. [Oct 09 19:50:17.683] [ warning] [vmsvc] HostinfoOSData: Error: no distro file found Solution: root@ds:~# cat /proc/version > /etc/release If this file exists the open-vm-tools are happy and do not throw any error anymore. __________________
-
Hello! I just expand a vmdk in a virtual Xpenology (a simple basic volume). The instructions are working very good besides two little differences: 1. After "mdadm --grow /dev/md2 --size=max" I have to use "lvextend -l +100%FREE /dev/vg1/volume_1" to grow the volume itself. 2. "btrfs filesystem resize max ..." does not work for me. I have to use "Storage Manager - Volume - Action - Expand" instead in DSM itself. But after all, the expanding works very well. Thanks very much for the information!
-
You can't create a snapshot of a a powered on virtual machine if you have a passthrough controller attached to this virtual machine. Then you must first shutdown the vm and then you are able to create a snapshot.
-
So I have now build your setup by myself. Everything went well and only one step was missing I used some info from this article to get the missing pieces: https://www.stavros.io/posts/how-to-configure-wireguard/ After adding these two lines into the server configuration file I am able to access my LAN and also the DSM via my smartphone over wireguard! I think the procedure itself will be running fine even on a raspberry pi as there is also docker available. Thank you very much again for this fine idea. Edit: I was building
-
So I just got the time to read through all information: Thank you very much for this!! Btw: We have a similar backup routine for backup "real" linux equipment (I use also Veeam Linux Free). For now I have the only issue that Veeam currently is not supporting LUKS2-encryption (only LUKS1). But this is much off topic and only a matter of time.
-
Nice to read that you solved the issue.
-
The first thing coming to my mind during reading your text is: "check speed and duplex settings!". Sometimes there is a mismatch between the NIC and the connected network switch regarding these settings which results exactly into the issues you are describing. The default setting in DSM is "auto" but maybe it helps if you to set speed/duplex fix to "1000mbit/full duplex". You can find the setting in the NIC settings of DSM. Before testing this I would suggest that you configure the second NIC as a fallback with a own fixed IP if the change doesn't work and you lost completely your connection
- 5 replies
-
- 1
-
-
- microserver
- update
- (and 4 more)
-
Thank you very much! Your instructions are working very well! I applied it in the same way as yours (only for supressing SMART errors on /dev/sda and /dev/sdb) and /var/log/messages is a lot quieter now!! EDIT: After enabling your fix for suppressing the SMART-Error messages I recognize a new error message which comes every minute: Every minute an error will be logged in /var/log/messages: 2020-05-19T06:17:38+02:00 diskstation ovs-appctl: ovs|00001|daemon_unix|WARN|/var/run/openvswitch/ovs-vswitchd.pid: open: No such file or directory But
-
Yes that's exactly the issue: your cpu does not have the needed instructions for the newest DSM. But in my case the 3615xs-image is working stable and without issues for a long time. So either upgrade your cpu/motherboard or stay at 3615/3617.
-
"Port URI" is set to "telnet://:8601" at my installation and it's working since years. But you use the wrong network card type: should be "E1000e" and not "E1000".
-
Ah well, that makes sense too. I broken hard disk is also a good reason for breaking a RAID.
-
Hi! I just read this thread and the first thing which comes to my mind was: "Maybe the new WD red hard disks are "new ones" with SMR.". WD40EFAX is SMR (shingled recording) with many problems on a RAID rebuild when used in a mixed environment with to good old and fast WD40EFRX (which uses CMR). If it is the case that you have a mixed environment and getting performance problems you can say "thank you" to western digital. Just google about this.
-
Yes. The Dell H200 HBA will be driven by the mpt2sas-driver. Here are some information aboute it: lspci -v | more [....] 0000:03:00.0 Class 0107: Device 1000:0072 (rev 03) Subsystem: Device 1028:1f1c Flags: bus master, fast devsel, latency 64, IRQ 18 I/O ports at 4000 [size=256] Memory at fd4f0000 (64-bit, non-prefetchable) [size=64K] Memory at fd480000 (64-bit, non-prefetchable) [size=256K] Capabilities: [50] Power Management version 3 Capabilities: [68] Express Endpoint, MSI 00 Capabilities: [d0] Vital Product D
-
I just have a look on my 2 VMs: - the first VM has a Dell H200 HBA flashed to IT-Mode and is configured as passthrough (under ESXi 6.7 and also 7.0 on a HPE Microserver Gen 8): SMART works very well! All values are shown in DSM and I run successfully a short SMART-Test on the disks. - on the second VM I have passthroughed the original "Cougar Point 6 port SATA AHCI Controller" of the HPE Microserver Gen8: SMART is working also very well without any issues. Both VMs are running as "DS3615xs". I hope this helps a little bit to localize a