yaqushi

Members
  • Content Count

    27
  • Joined

  • Last visited

Community Reputation

1 Neutral

About yaqushi

  • Rank
    Junior Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi there, assuming one would have an original Synology USB flash module where the DSM is hosted, can that be transferred to another PC and then booted? (It could simply be connected to any mainboard USB 2.0 socket) Every synology box has a usb flash like this hosting the DSM:
  2. Short question. Background: I did an update with Nanoboot 5.0.2.2 yesterday directly from Trantors beta 5, very easy. Web-GUI said its migrateable and I chose Migration (keep files and most of the settings). I assume clean installation (keep your files) would have led to a swipe of the hard drives. Uploaded original pat file and it works without additional adjustments. Maybe that helps some people. Question: In the pic you'll see that the little one as a reminder of an update did not disappear. Upon checking, it says, latest version installed. Why doesnt the red 1 disappear?
  3. Unfortunately most Synology solutions are underpowered in CPU for plex transcoding. The 3612 might do the job (price tag of 3k), but even that is borderline. If they would only offer smth with more power in the consumer field.
  4. It takes a lot less work to actually read the thread I did read the whole thread, no one posted anything on trying this as a fresh install. Everyone is trying to upgrade from 4452 version. But ya, I guess it was worth it to post a comment to read the thread. Cause we don't ask questions here, we are only reading...
  5. so completely new installation with gnoboot 10.5 and 4482 does work? Its a bit of work to backup the data and fill the nas afterwards, but can be done if the above is a workaround...
  6. That cant be right, if more than one volume present on separate drives and you delete volume 1 and pull respective drives out, system still starts, cause it is on EVERY drive independent from volumeX.
  7. funny, also i dont get hibernation to work in DSM 5. Other here claim it works. Would be nice to find out why hibenration doesnt work, rather than downgrading
  8. so just to clarify: you guys dont use the script (sync; /usr/syno/bin/synousbdisk -umount sdq; >/tmp/usbtab) at all to eject the system usb stick, it just works for you in DSM5?
  9. Does the Hibernation work for you guys? I cannot get this to work, everything else is fine in DSM5beta I tried the script sync; /usr/syno/bin/synousbdisk -umount sdq; >/tmp/usbtab but after reboot i ejects the usb, and only 20sec it mounts it again automatically. No idea whats wrong here.
  10. glaub nicht dass das so funktioniert wie im zweiten post beschrieben. USB oder SSD am USB (ist voellig egel was am USB angesteckt wird, kann auch ne microsd-karte mit usb adapter sein; man kann irgendein speichermedium benuzten solange es in der boot reihenfolge als erstes angewaehlt werden kann) enthaelt nur die start img datei, das 'system' installiert sich automatisch (nach laden der pat datei) auf JEDER festplatte die dem NAS hinzugefuegt wird. Die SSD ist voelliger overkill. USB wird nur beim hochfahren benutzt, wenn system laeuft kann man den getrost unmounten. Alle Einstellungen si
  11. Question for the hibernation in this release - I dont get it to work. Following the guides here, i do the following: 1. create new script S99ZZZ_USB_eject.sh: sync; /usr/syno/bin/synousbdisk -umount sdu1; >/tmp/usbtab (checked if sdu1 really is my USB drive) 2. copy it in the /usr/syno/etc/rc.d directory 3. give it the execute permission When i reboot the system and look in the log file, it says right after startup that USB1 was ejected. So far so good, apparently only if the USB1 drive is ejected, the sytem can hibernate. But, only 20sec later log shows: USB1 was mo
  12. Plex is a separate user, so why do you have a plex folder under "home" - that is supposedly your admin account right? See screenshot above. Under users you should have admin, guest , and plex.
  13. look two posts above, forget for ssh or any start-stop-status. post again when two posts above does not work. its pretty simple and everything to be done using the DSM GUI only.
  14. Hi guys, short question, did anyone came across this "error" already: I am running 3x3TB, 1x2TB, adn 1x80GB, when using SSH/fdisk -l, the following is the output: DiskStation> fdisk -l fdisk: device has more than 2^32 sectors, can't use all of them Disk /dev/sda: 2199.0 GB, 2199023255040 bytes 255 heads, 63 sectors/track, 267349 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sda1 1 267350 2147483647+ ee EFI GPT fdisk: device has more than 2^32 sectors, can't use a
  15. Sorry guys, still trying to figure out what script S99ZZZ.sh above is doing. Why "put the attached file (S99ZZZ_Shutdown.rar) to /usr/syno/etc/rc.d/ and give the file execuable permission"??? Anyone?