Jump to content
XPEnology Community

RobsterUK

Member
  • Posts

    26
  • Joined

  • Last visited

Everything posted by RobsterUK

  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 before installing and migrating data. I have checked /dev/dri - this is missing. cat /usr/syno/etc/codec/activation.conf - reports missing file. Is this because there is nothing installed on the system yet? I have not installed anything at all. Or do I need to replace the extra.lzma/extra2.lzma for loader 1.04b ds918+ DSM 6.2.3 v0.13.3 from this thread? https://xpenology.com/forum/topic/28321-driver-extension-jun-103b104b-for-dsm623-for-918-3615xs-3617xs/#comments Just want to ensure correct drivers are loaded before doing anything else, but not sure what other checks I can do, without installing Emby or Video Station.
  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 API v1 to connect and therefore is no longer working as they have turned it off. I may try the Syno forums to see if there's anyone else having issues.
  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 was done without any DSM updates applied. Some additional logs somewhere to indicate why it is failing would be handy too!
  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? I'm stumped.
  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 valid iso they can share? TIA
  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 my Nexus 5X using Tapatalk
  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.
  16. Not a specific XPENO issue, but having issues with the SHR, any advice offered would be appreciated. Running Bare Metal with 4 x 2TB disks in SHR. Have had issues leading up to 1 disk reporting that the 'System Partition Failed'. Resolved the other issues but not sure how to fix this. After reading https://forum.synology.com/enu/viewtopic.php?t=95925 & http://www.patnotebook.com/synology-ds1511-hard-disk-crash-not/ I wonder if running a GUI 'repair' will fix the issue. I've connect via putty and found out the following nas> cat /proc/mdstat Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] md2 : active raid5 sdd5[4] sdf5[6] sde5[5] sdc5[1] 5846049792 blocks super 1.2 level 5, 64k chunk, algorithm 2 [4/4] [uUUU] md1 : active raid1 sdc2[0] sdd2[1] sde2[2] sdf2[3] 2097088 blocks [12/4] [uUUU________] md0 : active raid1 sdc1[0] sdd1[1] sdf1[2] 2490176 blocks [12/3] [uUU_________] unused devices: Then looked at md0 nas> mdadm --detail /dev/md0 /dev/md0: Version : 0.90 Creation Time : Sat Jan 1 00:00:03 2000 Raid Level : raid1 Array Size : 2490176 (2.37 GiB 2.55 GB) Used Dev Size : 2490176 (2.37 GiB 2.55 GB) Raid Devices : 12 Total Devices : 3 Preferred Minor : 0 Persistence : Superblock is persistent Update Time : Thu Aug 11 12:14:31 2016 State : clean, degraded Active Devices : 3 Working Devices : 3 Failed Devices : 0 Spare Devices : 0 UUID : d58cf8b8:20aa78f7:3017a5a8:c86610be Events : 0.1107818 Number Major Minor RaidDevice State 0 8 33 0 active sync /dev/sdc1 1 8 49 1 active sync /dev/sdd1 2 8 81 2 active sync /dev/sdf1 3 0 0 3 removed 4 0 0 4 removed 5 0 0 5 removed 6 0 0 6 removed 7 0 0 7 removed 8 0 0 8 removed 9 0 0 9 removed 10 0 0 10 removed 11 0 0 11 removed * on a side note, I don't know why the disks start at sdc - sdf (not at sda - sdd) but the GUI also indicates they do not start at the logical beginning. Anyway, the System partition, md0, clearly has sde, missing. Would it be worth running the 'Repair' from the GUI. Or is there a command line alternative that would resolve the issue better? Or, should I scrub the drive then reinsert to allow SHR to rebuild the drive from being empty?
  17. Successfully updated to 5967 update 1. Created new boot disk. Booted & selected option Install/Upgrade. Used Syno assistant to connect to XPENO box. Manually installed .pat file selecting upgrade option. Rebooted, used DSM to install Update 1. Sorted
  18. Im sure that procedure will work. I was actually hoping after the first reply by abced that a new boot image would not be needed. But this method is tried and tested from previous versions & I don't want to risk dis-mounted disks or loose any data!! The lazy method would be without upgrading the boot disk. As my XPENO box is hidden under the stairs with loads of "junk" to move to gain access to it
  19. I think the safest way to go from 5592 to 5967 will be to create a new bootloader. Then boot and select Install/upgrade, select pre downloaded .pat file for 5967 and update. This should ensure all volumes mount and settings are intact. I will try to test this out this weekend and post back the result.
  20. Would the same be true to go from 5592 u2 to 5967?
  21. Yes! I'm busy with a brand new xpenology site. https://dev.myxpenology.com/ It also mirrors this forum, so if it got taken down somehow, we still have all the info =). Your site is looking great. All the builds & great guides too! Keep up the great work
  22. Have tried searching for this but cannot find any results. Does Xpenology have drivers for Broadcom BCM970015 (Crystal HD) PCIe card? Such as this http://www.amazon.com/BCM970015-Broadcom-Hardware-Decoder-Accelerator/dp/B0050QJUP0 I am in process of setting up Xpenology with Emby installed. My current Intel Core 2 Duo doesn't handle transcoding for all of my movies. If I can offload the transcoding to the Broadcom that may help. But I need the xpeno box to install the card first
  23. Search App Store for DS Download. As long as you have remote access setup for DSM web page then use the same details. Doesn't require any additional ports. You can use the BT search or even use the built in web browser (limited functionality) to add torrents to the queue. Works really well.
  24. htpcdude you're the man. Thanks for pointing that out, I don't think I would have ever thought of looking in there Changed that setting and, hey presto XPEnoboot will boot. Now happily running 5.2 5565 I will be looking to migrate my DS211 to XPEnology safe in the knowledge I can continue to update with XPEnoboot
  25. I am on bare metal using the following hardware Motherboard: Intel DG35EC CPU: Intel Core 2 Duo E7200 RAM: 4 GB DDR2 HDD: Maxtor 6V160E0 (160GB), SeaGate ST32000542AS (2TB) Chipset Info: 82G35 Graphics and Memory Controller, 82801HB I/O Controller Hub (ICH8), 82566DC Gigabit Ethernet Controller I am currently using Nanoboot 5.0.4.1 with DSM 4528. Everything works OK. I have tried to use Xpenoboot 5.2 5565.1 (& also previous versions of Xpenoboot) but each time I try to boot all I get is 'Boot Error' on screen. Doesn't even get as far as loading the boot options. I have verified the USB boot stick works on other hardware, so I can only presume this is some kind of driver/hardware issue. I have systematically gone through onboard devices on motherboard disabling one at a time and rebooting. But nothing I try will get this to boot. Has anyone any advice to offer? Obviously this issue is preventing me from updating any further. I don't want to get stuck using only Nanoboot on DSM 4528
×
×
  • Create New...