Jump to content
XPEnology Community

md1032

Member
  • Posts

    15
  • Joined

  • Last visited

md1032's Achievements

Newbie

Newbie (1/7)

0

Reputation

  1. Just an update, i managed to make the jump to 6.1 for DS3615xs and the custom extra.lzma ramdisk with no issues! Now what's the latest update i can use with this configuration? Thank you again for your help!
  2. Thanx for your reply! What are the advantages of 918+? I have read at the forum that the specific synology can be used mostly for plex transcoding, is there anything else i am missing? Also, the SHR2 will be recognised immediately or do i have to do anything extra (i read at the FAQ that i need to change a line at a config)?
  3. So one more upgrade question. I have the following setup DS3615xs (INTEL Core i3-4130) DSM 5.2-5967 Update 9 1 volume of SHR-2 20TB (8x4TB WD Red) at the following hardware setup AMD A8 7600 Gigabyte GA-F2A88XM-D3H mATX - FM2 Fractal Node 804 I can use this guide to make the jump to 6.1 for DS3615xs? I don't care that much about the current DSM settings (but if i can keep them its great) and the data at the SHR2 are available elsewhere too (cloud & other backups). I will keep the 5.2 USB drive and i will create a new one for the 6.1, can i boot from the 6.1 USB with a test drive (or with no drive) to check that everything is booting OK and then plug again all the drives to do the proper migration of 5.2 -> 6.1? Thanx!
  4. Greetings, i have the following xpenology setup (my hw is Gigabyte GA-F2A88XM-D3H mATX - FM2+, A8 7600) Model name: DS3615xs DSM Version: DSM 5.2-5967 Update 9 I have installed the docker package (version 1.6.2-0036) from the package center, i am trying to install some images via the registry search bar and they download/install successfully but after that they are nowhere to be found at docker! What can/should i do to resolve this issue? Thanx!
  5. Yes! Now i am having a weird issue and i am not sure where to post, i have installed successfully the docker package and i am trying to download/install containers, they do with success (or at least that what the docker log say) but there are nowhere to be found at the docker!
  6. Thank you again for your information. For the record after i updated the usb drive and booted with it the DSM didn't ask me to migrate/update and i successfully updated my DMS with the DSM_DS3615xs_5967.pat file. After that i did an update via the control panel to Update-9 and after two reboots everything seems to be OK (with the first reboot it game the error "Abnormality detected on DISKSTATION. All volumes have been unmounted.").
  7. Thank you very much for this information. So the steps are (because i am a little rusty): Format the usb drive with Win32DiskImager the image of XPEnoboot_DS3615xs_5.2-5967.1.img/iso Boot the machine with the updated usb drive Update from the control panel with the DSM_DS3615xs_5967.pat from here https://archive.synology.com/download/DSM/release/5.2/5967/
  8. Greetings, i have the following xpenology setup (my hw is Gigabyte GA-F2A88XM-D3H mATX - FM2+, A8 7600) Model name: DS3615xs DSM Version: DSM 5.2-5565 USB version: XPEnoboot_DS3615xs_5.2-5565.2 (i need to double check that) I believe the latest version available is the DSM 5.2-5967 Update 9, what is the safest way to update to this version? Thanx!
  9. So i inserted a new one and the repair finished just fine! Now I can safely expand the allocate size of volume to max without losing data, right?
  10. Yes, it was a kinda "false alarm", i re-run the full scan of diagnostics and had disk failed error because of many bad sectors... so i will replace it with a new one (and its only 7 days old)!
  11. So the expanding finished, the volume is of course downgraded. I inserted the bad drive at my desktop and wd diagnostics found some bad sectors that repaired them...so what should i do next? Re-insert it to xpenology and repair the volume or replace it with a new one?
  12. I will hit the repair when the expanding is done (not its at 80%) and then i will take out the disk to check it at windows desktop with WD diagnostics. Thankfully the shared folder of the xpenology is visible at my desktop so i can do a minor backup of some important stuff i have there.
  13. The crashed one is from the new ones. The log wrote errors like that "SYSTEM: Write error at internal disk [4] sector 121006024." so i guess either the sata cable is bad (cause i used an old one) or the HDD has indeed bad sectors. Now the expanding is at 50% with no other errors...
  14. Greetings, i have 6 WD 3TB RED and i added 2 more to my system and when i was expanding the disk group it showed me that one of the new ones crashed My version is DSM 5.2-5565 What should i do? Can i stop the operation and check the crashed HDD to my desktop to check for bad sectors etc? Should i allow it to end and then do the replacement with a new one? If i leave it to expand the disk and one more crashes i will lose all my data (SHR2)? Thank you in advance for your help!
  15. Greetings, i am having the same issue with the topic starter My latest hardware installation of xpenology is and i am using a bootable usb with XPEnoboot_DS3615xs_5.2-5565.2. Because i am not really sure how to proceed with the update, 1) i need to create a new bootable usb with XPEnoboot_DS3615xs_5.2-5644.5 2) i need to choose install/update from boot manager or just let it boot? 3) update the software via the control panel through web download or manually choosing the DSM_DS3615xs_5644.pat file? I have taken a configuration backup. Also i guess that wont be any data loss from my SHR2 volume right? Thank you a lot for your time and support!
×
×
  • Create New...