Jump to content
XPEnology Community

DSfuchs

Member
  • Posts

    259
  • Joined

  • Last visited

  • Days Won

    4

Everything posted by DSfuchs

  1. It's all 0% related. If you want to destroy the hardware, please continue.
  2. One is primarily for Windows, Terminal for Linux. I only know errors with the DoM, and general final-smoking by the power supply.
  3. You have to find USB hardware for which there is also a programming tool from the manufacturer, to set 0xf400/0xf400 IDs. I did this. Cloning works e.g. with this tool: USB Image Tool 1.81 Copyright (c) 2006-2020 Alexander Beug In the terminal I copy/backup partitions/drives with ddrescue, which becomes available on synology via the synocli-disk package. It works like: ddrescue "source" "target" e.g. Partition: ddrescue /dev/sdq1 --force /dev/sdr1 e.g. Device: ddrescue synobootstick.img --force /dev/sdr
  4. No, it can only be started from hardware reporting 0xf400/0xf400, translated from the online database i.e. Synology/Diskstation: https://the-sz.com/products/usbid/index.php?v=0Xf400&p=0xf400&n= If the DoM can be read, then I would overwrite the four files as described above, out of the tar from here: https://global.synologydownload.com/download/DSM/release/6.2.4/25556/DSM_DS412%2B_25556.pat If no 0xf400/0xf400 hardware works => PM
  5. Hello, I'm not looking for a backup. It just doesn't work, even with a build. I have the impression that chatGPT always answers me first. Please check the basic features provided by friend.
  6. Hello again, I have a significant problem when I adjust the configuration file for DS918+ from your menu manualy. The changes are not effective and overwritten with every boot. So I don't have any hard drives, just a DoM. It's about the values that you have to set, for example to manage an external USB drive internally: esataportcfg="0x0" internalportcfg="0xfffff" usbportcfg="0x0" I hope there would be help for me. Regards
  7. Does the file only differ in the device name, which actually doesn't matter if it's a better device? I haven't compared it yet.
  8. I don't need to send anything from a DS918+, you already have that.
  9. That should be all, only hardware that reports 0xf400/0xf400 is missing.
  10. It may still be necessary to change the values to "DS218"
  11. The 1st partition can be completely taken over by the DS918+.
  12. It seems to be, that the original Flash is working on it's 1st partition further on. Than it is posssible that the boot process finds the 2nd on your memory. To recover the 2nd partition, take the Sone.9 file from the DS918+ and the other files out of the downloaded pat. If you need detailed information about the image of the DS218+, I can look at mine, since I have one now.
  13. Should you not be familiar with migrating RAID arrays: After the model change under DSM6 on the replacement drive, I recommend removing it and performing the migration and in a 2nd step the OS upgrade as described/intended by the manufacturer. To do this, you must first start with only one hard disk leftmost, install the DSM6-pat of the new model, make the changes regarding the drives and then restart with all the drives to complete the array. Then only the system partition needs to be synchronized. Now Upgrade to DSM7 by the gui.
  14. We will not have DSM8 running on a Synology Cedarview model. So the necessary changes for the DS713+ actually only have to be made "once".
  15. I also got Xpenology running fine on a DS710+ as a DS3615+. To this is to be said: - the 4GB RAM module is very expensive - 1c/1t performance is very limited - an additional hardware trick was necessary, another USB device had to be plugged into one of the rear sockets at the same time. For me it was a keyboard transmitter. Dealing with the DS218+ with 2c/2t is a waste of time. You definitely get 4c/4t hardware like DS716+II for 75 mice.
  16. Seems interesting, but it isn't. I stopped reading after a few lines. We're not talking about a different operating system. He also confirms that the hardware is locked with 0xf400/oxf400. Of course, it can be any storage hardware that reports like this. I even say it only works from the front USB socket.
  17. The boot process must be initiated from hardware with VID/PID 0xf400/0xf400.
  18. dd if=/dev/synoboot of=/volume1/myShare/DS412+synoboot-6.2.4u6.img
×
×
  • Create New...