Schmill
-
Posts
148 -
Joined
-
Last visited
Posts posted by Schmill
-
-
13 hours ago, XPEH said:
You don't need to do any of that as this wave of Crypto viruses are windows executable and will not run on Linux based NAS. If potentially infected Windows based computer doesn't have access to the share, it will not be able to encrypt the contents.
Are you sure that is the case?
I thought the whole worry of Synolocker was the fact that it infected and ran on the DSM directly, so would have access to everything that the NAS had access to.
-
Ok, I already have the usbshares hidden from the network, and permissions removed so that only the XPEnology box itself can write to the drives, but I was concerned that my box could get infected with CryptoLocker-like ransomware, and then it would also corrupt my backups (if they were still mounted), is that not the case?
I have tried the "mount" command (although not quite as you typed it) but get an error about the device not being in fstab:
mount /volumeUSB1 mount: can't find /volumeUSB1 in /etc/fstab
-
I have my server setup to perform weekly backups to an external USB drive; this all works fine.
With the recent CryptoLocker-like issues I figured it is probably not a great idea to leave my external USB backup mounted all the time, so in the "Backup & Replication" job settings I have set the "Remove destination external device when backup task has successfully finished", and that too works well for me.
However, I am then left in the situtation where in order to make the server 'see' the drive again I have to physically disconnect the usb and reconnect it, or (as I am commonly remote from the server) reboot the server so that it finds the usb drive again.
What I really want is to be able to do something (either manually or scripted) that will allow me to re-mount the device prior to the backup.
Does anyone know how to get Synology to un-eject an external USB device?
Thanks!
-
Rather than port forwarding to your DSM, it's safer to use VPN
.A VPN is something I have been wanting to setup for a while, but never seem to be able to get it to work.
Is there a guide available somewhere? - I've looked through the GUIDES section on here and can't find anything.
Did you check synology instructions?
The one place I didn't look! - Cheers!
Sent from my MotoG3 using Tapatalk
-
Rather than port forwarding to your DSM, it's safer to use VPN.
A VPN is something I have been wanting to setup for a while, but never seem to be able to get it to work.
Is there a guide available somewhere? - I've looked through the GUIDES section on here and can't find anything.
-
Wonderful! Many thanks, I feel more confident about giving this a go now
Cheers for your help, I'll post back how I get on.
Sent from my MotoG3 using Tapatalk
-
Cheers Benoire, can I ask did you use the ISO file or the IMG file?
Sent from my MotoG3 using Tapatalk
-
Hi,
I realise I could try this, but due to the possibly destructive nature of it I thought I would ask first whether anyone has done it already.
What I am looking to do is to be able to update the USB bootdisk whilst keeping it in the server.
Some generic instructions I have found for writing images to USb devices via command line seem to imply that all that is involved is along the lines of:
sudo umount /dev/sdb sudo dd if=/path/to/imagefile of=/dev/sdb
Is that all it will take?
If so should I use the XPEnoboot iso file, or the img file as the input to dd ?
Many thanks all!
-
5.2 5967 Update 1 here and the CPU throttle script still seems to be working its magic. I have 'upgraded' my way to here though, so perhaps it relied on something that was in earlier versions and now not present?
-
Where does it get stuck?
Have you done the checks to see if everything is running properly?
I'll add some diagnostics tips here later when I'm on the pc.
Sent from my GT-I9100 using Tapatalk
-
Hmm, ok the final script it says it is running "/etc/acpi/powerbtn.sh" consists of just two lines:
> cat /etc/acpi/powerbtn.sh #!/bin/sh syno_poweroff_task -r poweroff
What is the '-r' parameter to the syno_poweroff_task supposed to be doing?
Either it isn't supported, or it isn't documented:
> syno_poweroff_task -h DS shutdown progress. usage: syno_poweroff_task [OPTIONS] -h display this help -d debug mode
If I ignore that first script call and manually run the "poweroff" command at a root SSH prompt then the hardware does power-off, so I'm guessing that the system is actually hanging on the "syno_poweroff_task -r" call...
I tried running with the debug option, but it didn't seem to tell me much:
> syno_poweroff_task -d Killed by signal 15.
Thoughts anyone?
EDIT
Hmm - Ok it seems as if editing the powerbtn.sh script to comment out the two lines that are in it, and replace with a single line of:
#!/bin/sh syno_poweroff_feasible_check
Makes everything work perfectly.
Not sure if this will also fix it for the people running the 5644 bootloader, might be worth a try?
-
Just to throw another into the mix; I am running 5592 update 4 (with the 5592.2 bootloader), and the shutdown from the menu in DSM works fine.
Trying to use the pushbutton I get the same as reported above, the DSM software shutsdown (all terminals are disconnected etc.) but the final stage of the ACPI shutdown of actually turning off the hardware doesn't happen.
Running acpid in debug mode when I press the button I get the following output:
acpid -d -l Deprecated /proc/acpi/event was not found. Trying netlink and the input layer... input layer /dev/input/event0 (Power Button) opened successfully, fd 4 input layer /dev/input/event1 (Power Button) opened successfully, fd 5 inotify fd: 6 inotify wd: 1 netlink opened successfully acpid: starting up with netlink and the input layer parsing conf file /etc/acpi/events/powerbtn-conf acpid: 1 rule loaded acpid: waiting for events: event logging is on acpid: received input layer event "button/power PBTN 00000080 00000000" acpid: rule from /etc/acpi/events/powerbtn-conf matched acpid: executing action "/etc/acpi/powerbtn.sh" BEGIN HANDLER MESSAGES
Then I lose the SSH terminal.
Of note, I also have the WOL mod applied which works fine on its own, but I'm wondering whether it is possible that it might be interfering with the PushButton scripts at all on the way down?
I'll report back if I find anything, and I'll also keep my eyes open in case anyone else has any bright ideas
-
Okay, I finally cracked mounting synoboot for 5.2. Here's the updated instruction.
...
Just wanted to provide feedback on this thread that Kanedo's updated instructions did also work for me.
Thanks Kanedo!
-
Are you logged in as root, or an admin account?
It might make a difference.
-
Ok, so I can successfully hide it, and then see it listed as /dev/synoboot.
However I cannot mount it.
As a test I've now unplugged the USB stick from the server and now I see this:
> parted -l 2> /dev/null |grep "^Disk /dev/s" Disk /dev/sda: 3001GB Disk /dev/sdb: 3001GB Disk /dev/sdu: 2000GB
So that's expected, I've removed the stick after all. (/dev/sdu is my attached USB backup drive).
> ls -la /dev | grep syno crw-r--r-- 1 root root 201, 0 Dec 5 00:28 synobios brw-r--r-- 1 root root 1, 1 Dec 5 00:28 synoboot1 brw-r--r-- 1 root root 1, 2 Dec 5 00:28 synoboot2
So I have no 'synoboot' device now (I've removed the stick though), but I do have a synoboot1 and a synoboot2, I presume that these are images of the boot stick on each of my fitted drives (sda and sdb).
Trying to mount them with '-t vfat' doesn't work though:
DS001> cd /dev > mkdir -p /volumeBootStick > mount -t vfat synoboot1 /volumeBootStick/ mount: mounting synoboot1 on /volumeBootStick/ failed: Invalid argument > mount -t vfat synoboot2 /volumeBootStick mount: mounting synoboot2 on /volumeBootStick failed: Invalid argument
So try without '-t vfat':
> mount synoboot1 /volumeBootStick > mount | grep synoboot synoboot1 on /volumeBootStick type ext2 (0)
Seems to mount, so what's on it?
1> ls -la /volumeBootStick/ drwxr-xr-x 4 root root 4096 Dec 5 00:28 . drwxr-xr-x 31 root root 4096 Dec 6 18:46 .. drwxr-xr-x 3 root root 4096 Dec 5 00:28 boot drwx------ 2 root root 16384 Dec 5 00:28 lost+found -rw-r--r-- 1 root root 1024 Dec 5 00:28 rd.gz -rw-r--r-- 1 root root 1024 Dec 5 00:28 zImage
Doesn't look like the content I'm expecting on the boot stick though...
So I unmount it and mount synoboot2 instead...
> mount synoboot2 /volumeBootStick/ > ls -la /volumeBootStick/ drwxr-xr-x 3 root root 4096 Dec 5 00:28 . drwxr-xr-x 31 root root 4096 Dec 6 18:46 .. -rw-r--r-- 1 root root 1024 Dec 5 00:28 checksum.syno -rw-r--r-- 1 root root 1024 Dec 5 00:28 grub_cksum.syno drwx------ 2 root root 16384 Dec 5 00:28 lost+found -rw-r--r-- 1 root root 1024 Dec 5 00:28 rd.gz -rw-r--r-- 1 root root 65536 Dec 5 00:28 vender -rw-r--r-- 1 root root 1024 Dec 5 00:28 zImage
That doesn't look right either...
Checking the bootstick content in a Windows PC gives this:
Volume in drive F is 5_2__5992_2 Volume Serial Number is XXXX-XXXX Directory of F:\ 03/08/2015 15:45 24,124 libutil.c32 03/08/2015 15:45 26,336 menu.c32 12/09/2015 15:25 759 syslinux.cfg 03/08/2015 15:45 21,538,496 zImage 4 File(s) 21,589,715 bytes 0 Dir(s) 3,295,232 bytes freeSo it seems that the other synoboot# devices aren't copies of the bootstick?
To be sure I put it back in the server and rebooted.
> parted -l 2> /dev/null |grep "^Disk /dev/s" Disk /dev/sda: 3001GB Disk /dev/sdb: 3001GB Disk /dev/sdu: 2000GB Disk /dev/synoboot: 1059MB
Sure enough 'synoboot' is back.
Confirmed in the /dev directory:
> ls -la /dev | grep syno crw-r--r-- 1 root root 201, 0 Dec 5 00:28 synobios brw------- 1 root root 135, 240 Dec 6 19:27 synoboot brw-r--r-- 1 root root 1, 1 Dec 5 00:28 synoboot1 brw-r--r-- 1 root root 1, 2 Dec 5 00:28 synoboot2
So I try to mount it:
> mount synoboot /volumeBootStick/ mount: mounting synoboot on /volumeBootStick/ failed: No such device > mount -t vfat synoboot /volumeBootStick/ mount: mounting synoboot on /volumeBootStick/ failed: Invalid argument
I'm suspicious of the "No such device".
Has something been done to block the mounting of the synoboot device?
-
How did you get autoupdate?
I've downloaded the new spk (thanks Dodo!) but not yet install it, I am intrigued to know if it is possible to get Package Centre to autoupdate virtual box etc?
I think that DTech meant that he updated the package without uninstalling the previous version. Since version 5.0.4 this is working, Dodo-dk has done a great job, tha package gets updated and preserves all the settings and VMs.
Regarding the auto update I think you do not want the package center update automatically virtualbox shutting down the running VMs in an uncontrolled fashion.
Ah good point - many thanks for the explanation. I'll get this installed soon then [emoji3]
Sent from my GT-I9100 using Tapatalk
-
How did you get autoupdate?
I've downloaded the new spk (thanks Dodo!) but not yet install it, I am intrigued to know if it is possible to get Package Centre to autoupdate virtual box etc?
-
Cheers dodo - worked for me. Only issue I had was I was coming from a much older version. When I installed your pack I kept on getting an error when I tried to access the web page for virtualbox, but doing a 'Remove' from Package Centre then reinstalling seemed to sort it
Thanks for the update!
Sent from my GT-I9100 using Tapatalk
-
I'm currently running DSM 5.1-5022 Update 5 and will soon be updating to the latest 5.2
However I've found before that one thing that seems to get blanked during an update is the auto-block IP list.
I use this feature (Control Panel --> Security --> AutoBlock), and as such it has built quite a list of blocked IP addresses to date, and I don't really want to lose it.
The interface does allow you to IMPORT a list of IP addresses to add to the list, but I see no way to export the current list.
Does anyone know a way, or perhaps know where the list is stored on the file system?
Thanks!
-
So have you now fixed this yourself, or are you still stuck?
-
In hindsight that sounds like a plan...
In the meantime however anyone have any idea how I can mount the usb stick again?
I know once I can physically access the stick I could edit the vid and pid again and then when I boot I presume it will appear, but any ideas for the meantime?
-
As above, I found myself in a similar situation the bios is the place to look.
If memory serves me correctly you must set the USB boot disk to be the first boot device, and then disable all others. This will stop it trying to boot from your external drive
If you get stuck let me know and I'll check my bios settings and let you know the exact settings next time I am colocated with my server
-
Or you use the built in option that the devs put in. The following is an example of the syslinux.cfg on your usb drive. just edit the the VID and PID #'s with that of your usb drive.
UI menu.c32 PROMPT 0 TIMEOUT 50 DEFAULT xpenology MENU TITLE XPEnoboot 5.1-5055.1-19c83d5 LABEL xpenology MENU LABEL XPEnology DSM 5.1-5055 KERNEL /zImage APPEND root=/dev/md0 ihd_num=0 netif_num=4 syno_hw_version=DS3615xs sn=B3J4N01003 vid=0x0EA0 pid=0x2168 loglevel=0 vga=0x305 rmmod=ata_piix LABEL debug MENU LABEL XPEnology DSM 5.1-5055 Debug KERNEL /zImage APPEND root=/dev/md0 ihd_num=0 netif_num=4 syno_hw_version=DS3615xs sn=B3J4N01003 vid=0x0EA0 pid=0x2168 loglevel=0 vga=0x305 debug=1 console=ttyS1,115200 rmmod=ata_piix LABEL install MENU LABEL XPEnology DSM 5.1-5055 Install/Upgrade KERNEL /zImage APPEND root=/dev/md0 ihd_num=0 netif_num=4 syno_hw_version=DS3615xs sn=B3J4N01003 vid=0x0EA0 pid=0x2168 loglevel=0 vga=0x305 upgrade=5.1-5055 rmmod=ata_piixThanks Diverge, but I think you may have missed the point. Adding the VID and PID to the syslinux.cfg file is what this thread is about, but the query I'm having is the step that then lets you mount what is then known to the sytem as /dev/synoboot. Getting access to the USB stick itself is not easy for me, so it is handy to be able to mount it to make alterations to the files remotely, but at the moment I can't mount it.
-
Never mind - turns out you must run the parted command with root permissions.
If I do:
sudo parted -l 2> /dev/null |grep "^Disk /dev/s"
Then I get:
sudo parted -l 2> /dev/null |grep "^Disk /dev/s" Disk /dev/sda: 3001GB Disk /dev/sdb: 3001GB Disk /dev/synoboot: 1059MB Disk /dev/sdu: 2000GB
Unfortunately even then I cannot mount it.
DS001> mount -t vfat /dev/synoboot /volumeFooBar/ mount: mounting /dev/synoboot on /volumeFooBar/ failed: Invalid argument DS001> mount -t vfat /dev/synoboot /volumeFooBar mount: mounting /dev/synoboot on /volumeFooBar failed: Invalid argument
/dev/synoboot1 also gets the same failure - I did try
N54L - USB 3.0 Card recommendations?
in Hardware Modding
Posted
Hi all,
I have a USB3.0 PCI E card in my N54L, and I find the performance a bit flakey, (which isn't great as it feeds my external drives used for backups!); also it is no longer available.
I am looking to get a card for my parents N54L, and may look to replace mine at the same time, sooo... are there any cards that anyone would recommend (that are currently available), do I need to look for any particular chipset, or should I just be able to pickup any USB 3.0 PCI E (low profile) adaptor card from ebay and it should work?
Thanks!