RobsterUK

Members
  • Content Count

    26
  • Joined

  • Last visited

Community Reputation

0 Neutral

About RobsterUK

  • Rank
    Junior Member
  1. I have copied the extra/extra2 v0.13.3 into the boot image. Had to use synology assistant to re-intialize the system, another reboot everything looks good. admin@NAS1:/$ cd /dev/dri admin@NAS1:/dev/dri$ ls card0 renderD128
  2. Thanks IG-88 for the reply & confirming correct procedure. Will give that a try tomorrow morning and report back. Sent from my Nexus 5X using Tapatalk
  3. Have been running DSM 5.2-5967 on old hardware for about 5 years. Just built new box to replace. Going to rsync all 5TB of data from old to new. Just want to make sure new is setup correctly prior to data migration. Hardware is Gigabyte B365m DS3H Intel i3 8100 8GB RAM 3 x 4TB Seagate Wolf drives Generated a serial from google search, inserted real MAC and added VID & PID to grub.cfg Have used Jun 1.04b with DSM_DS918+_25426.pat - Install went fine - so running 6.2.3 - 25426 Update 2 Want to ensure Emby will do hw transcoding befo
  4. Hi, I got a legacy motherboard - Intel DG35EC which is not UEFI BIOS. I currently have 4 x 2TB HDD. One of them has died. So, as I have to make a purchase, I'm thinking of replacing two with 3TB drives. Anyone know if the motherboard will have any restrictions of a HDD that size? All I can find is forums talking of MBR with BIOS and GPT for UEFI - all windows based systems.
  5. Have just found this on their forum. https://www.dropboxforum.com/t5/Syncing-and-uploads/Unable-to-connect-to-Dropbox-account-on-Synology-CloudSync/m-p/246683 Although related to Cloud Sync, they're getting a similar error. Synology will need to re-create using the APi v2. May be in a future update, or may even be on DSM 6. But I'm in no rush to move to DSM 6 yet, so will leave it as it is for now.
  6. Thanks for pointing me in the right direction. Managed to gain this from the logs nas entry.cgi_SYNO.FileStation.VFS.Connection[1].create[26403]: error_handler.cpp:752 dropbox response error code=400 Nov 23 10:52:49 nas entry.cgi_SYNO.FileStation.VFS.Connection[1].create[26403]: dropbox.cpp:101 Failed to process curl https://api.dropbox.com/1/account/info, err:{"code":27,"curl_code":0,"msg":"{\"error\": \"v1_retired\"}","response_code":400} Nov 23 10:52:49 Along with this link to say APi v1 is depreciated I may be way off, but it sounds like the File Station uses Dropbox's A
  7. Thanks for the reply. I only mentioned the DSM account as in the file station settings>Mount/Connections>Server and Cloud Service - you can specify what DSM users can add connections to remote services. When I first created my XPENO box during 2015 I created a serial and MAC form the generator tools available at the time. So not using a genuine one, but not the default one either. Yes google connection requires google account credentials, which the dropbox one does too. I used to be able to access the dropbox service this way & i'm fairly certain that it wa
  8. Running DSM 5.2-5967 Update 6. Trying to get File Station connected to Dropbox. Go through connection wizard and sign into Dropbox. 'Allow' the API request. Click to Agree the redirection. Then get prompted with 'Operation Failed'. I have added a connection to Google Drive using the same DSM account, so there is not a permission issue there. The API status in Dropbox shows an entry for Synology File Station. I have file station logging enabled, but nothing helpful is reported in the log center. Are there any other logs I can look into this issue?
  9. Can anyone confirm if its safe to go from DSM 5.2-5967 Update 2 to Update 4 via webgui? Currently using 5.2-5967 Update 1 boot loader. Obviously its safe to go from Update 3 to 4. I always tread cautiously before updating a working system.
  10. RobsterUK

    DSM 6.1.x Loader

    Thanks for the replies. As the Hyper-V Network driver is not yet supported. I've converted the vhdx to a vmdk & going through setting it up in VM Player. Hopefully this will work OK.
  11. RobsterUK

    DSM 6.1.x Loader

    I've read through the last few pages of this thread, at least since the new V1.0 loader has been released. I can't see that anyone has created an .iso yet. I want to test this with Hyper-V & that will only boot from an iso. I've tried to create an iso by using ImgBurn to open the .img file then create an iso. The VM would not boot. From the 5.2 iso that was working OK. Copied the VID & PID and SN from the isolinux.cfg file. Mounted the img with OSFMount and edited the grub.cfg with correct values. Created a new iso with ImgBurn. Still will not boot. Has anyone got a v
  12. This Then issue sorted Sent from my Nexus 5X using Tapatalk
  13. I have an Intel DG35EC mobo with an Intel Core 2 Duo E7200 @ 2.53 Ghz, 2x2GB 667mhz Kingston ram, 4x2 TB Seagate drives from on board sata controller, running off a 320 watt PSU. It's been running solidly for 18 months with 24/7 operation. Running Emby media server (which will perform on-the-fly transcoding), photostation, ds download, ds audio, couch potato, Sabnzbd, sickbeard. One thing I did have to do was to set BIOS, Boot, USB Mass Storage Emulation Type and changed the setting from "Auto" to "All Fixed Disc". Prior to that the box wouldn't boot. Hope this is useful Sent from
  14. Adding the drives in the right order was probably one of the most important things to have got right. Still, at least you can see them in the new install. Another option may have been to use the synology assistant when you had all the drives on the new mobo, but before you added the new DSM install. Boot XPENO to install/upgrade boot option & Syno assistant could well have detected the previous install and allowed you to reinstall over the top. Same way as running the upgrade. But if your making good progress then go with it! Good luck
  15. Yea OK, think I'll give it a try. After reading the threads on those links I want to err on the side of caution. Asking in here is a good way to get somebody else's opinion.