Jump to content
XPEnology Community

billat29

Members
  • Posts

    350
  • Joined

  • Last visited

  • Days Won

    10

Everything posted by billat29

  1. Ah yes! Would you post the link when you find it, please?
  2. Somewhere on here, someone suggested: Remove USB Insert into your PC Boot run postupdate commands return USB to headless box I was building a system to try this but finger trouble got me into migrate mode which reset the BIOS which trashes everything. By the time I figured out what was happening and sorted it, I had lost all interest.
  3. run the command: date Is the date and time correct? If not, then that is your problem. Either your BIOS battery is dead OR DSM reset the BIOS when doing a recovery. If you run fullupgrade without the date correct, it seems to delete everything to make way for new files and then if it fails, you are stuck. Check BIOS settings, reset the date, download rploader,sh from the repository and run fullupgrade.
  4. Excellent! Well done! Would you mind posting an entry for your upgrade in here, please? https://xpenology.com/forum/topic/59827-dsm-71-42661
  5. What happened with DSM V6.x is that it had a check to see if there was a hidden directory ./xpenoboot. This directory was created by one of the versions of the xpenology loader for V5. If it found it, then it would disable all services. I don't know whether V7 has the same check, or if your system has the directory, but if the migration worked, then I would say that it is probably OK. If you ssh in and do cd / ls -la you should get a list of directories you can check
  6. OK if that was a DSM5.0 disk and no issues running V7 then the 3 disks <should> be OK.
  7. .. and if you are doing a migration from V5 then : https://xpenology.com/forum/topic/26723-network-down-after-dsm-login/?tab=comments#comment-137953
  8. Check that C1E is disabled in the BIOS. and that the onboard nic is enabled and WOL is enabled. Let me know what you find
  9. check that the time and date on the HP are correct
  10. Sorry. I have made myself confused.... You need both the USB (stick,card whatever) and the HDD. The loader goes on the USB and DSM is installed in a RAID array across all HDDs. We are not doing an upgrade. We are doing a migration. We are simulating pulling the drives out of a DS3612xs and putting them in a new DS3622xs. Once you have created the new 7.1 loader, we are hoping that when you boot from that, it looks at the three disks and says that you have taken the disks out of an old machine and offers to do a migration. We want it to give you the option to a manual install of DSM7.1 and then it should go away and do whatever it needs to do to end up with a running 7.1 system. It should preserve your data. So. I like your idea. Put the spare drive into the current system. Create a volume on it (this will also install DSM 5.0 on it). Pull everything out except the new drive, insert a fresh USB stick and build the loader. When it boots afterwards, it should allow you to perform a migration. If that looks good, shutdown; replace the extra disk with the three old disks and cross your fingers (or whatever works best for you) and boot. Good luck.
  11. This should be fun a. I hope you have a backup of your data. I guess you don't! I really, really would try to see if you can find a way to secure your data. b. I don't have SSD cache c. If you build a new system on HDD and introduce your old disks, DSM tends to want to reformat them. So we need to work out how to update your system safely using your existing data d. If you have another HDD that you can play with, then that's good as your can trial the upgrade before risking your data. e. What's connected to the USB 3.0 card? DSM 7.1 removes a lot of support for USB devices. f. You also need to check the packages you have installed in DSM 5.0 to see whether they are supported (or replaced) in DSM 7.1. g. I have no idea whether it is possible to take DSM 5.0 drives out of a real DS3612xs and put them into a real DS3622xs and install DSM 7.1 in one step. So we would need to trial that. h. What's the 640Gb disk for? It's a bit old and small.... Have I put you off yet? Depending the results of e. and f. You might consider just going to 6.2.3. If you have already or can make a full backup of all your data, I might be tempted to wipe it all clean and start a new, fresh installation. If not, then I would do the following: Remove all the old drives and set them aside. Keep them safe. leave the drive with your loader on it in the machine. Insert your "extra" blank disk and create a new 5.0-4493 U7 system. If you don't have a copy of the right DSM locally, you can find it on the Synology Download center. Create a volume and some folders. Upload a file or two. Set your loader disk aside. Keep it safe. Follow the DSM 7.1 tutorial to create a new 7.1 loader. Now. boot it and see if you can find it in Synology assistant. What options do you see? Does it give you the chance to install DSM 7.1 manually? If so do it and see what happened to your test system.
  12. Step 4.4. I think you are making life harder for yourself using WinSCP. Use the onboard vi editor or enter the command to install nano which for many is much easier to use.
  13. Can you, as a test, upload files via the web interface? If you can, then what protocol are you using to map your drives? I am wondering whether the N54L is using an old version of SMB which is now blocked by a recent update to your laptop.
  14. I can't say for sure. I can make the following observations: 1. The parameter now is no longer required. 2. I used the realmac option for serialgen this enabled WOL for me. 3. I didn't do the intermediate 7.0.1 step or clean 4. I didn't do any step after the 7.1 build. 5. I didn't apply any update. and.. can you post any follow up in the installation section? This doesn't really belong here.
  15. I did this. ./rploader.sh ext broadwellnk-7.1.0-42661 add https://github.com/jimmyGALLAND/redpill-ext/raw/master/acpid/rpext-index.json ./rploader.sh build broadwellnk-7.1.0-42661
  16. You need the acpi extension. Look through flyride's tutorial for how to do it. However, I didn't find it for DS3615xs and so I migrated to DS3622xs+
  17. I have a question about the reboot. My box is running headless and since I closed my home lab, it's a bit of pain to move it to a monitor and give it a network connection. Creating the loader and installing DSM is fine headless, but getting back to TCRP later needs a console to change the boot option. Can anyone think of a straightforward way (I can only think of complicated) to change the next boot to TCRP without a console?
  18. While I was testing upgrades, I got into this recovery loop. Looking at the logs. what seemed to be happening was that it was trying to download something to do the recovery and not finding it. I think that redpill by design blocks Synology and so this, I thought, could be the problem. In my case, as I was testing, I gave up and started again. What you might do is follow flyride's troubleshooting instructions in their tutorial to try and post what you find
  19. - Outcome of the update: SUCCESSFUL - DSM version prior update: DS3615xs+ 6.2.3-25426 U3 (Jun 1.03b loader) - Loader version and model: TCRP 0.4.6 DS3615xs - Using custom extra.lzma: NO - Installation type: Baremetal HP N54L. Stock BIOS. Integrated nic - Additional comments: Using "disable_mtrr_trim": null in user_config.json
  20. A typo. I think. Should it be vi user_config.json rather than vi nano user_config.json
  21. https://xpenology.com/forum/topic/59827-dsm-71-42661/
  22. My old N54L is still running. From other forum posts, there are a lot of people running them. All I have had to do to it (so far) is change the BIOS battery. Some people have had fan failures. If you want anything advanced, like transcoding,, then you need to seek a box with a later Intel processor but it is perfectly good for more basic tasks. Mine is still running 6.2.3 with the jun loader. I successfully installed 7.0.1 with the redpill loader but found I had some work to do to upgrade / replace some of the old packages for version 7. So it all went on hold. The latest DSM version is 7.1 and there are reports here of successful installation. So I would give it a try, post any issues in the appropriate forum rather than here. A couple of tutorials: https://xpenology.com/forum/topic/61634-dsm-7x-loaders-and-platforms/ Those who have reported success so far have used the DS3615xs platform and https://xpenology.com/forum/topic/60130-redpill-tinycore-loader-installation-guide-for-dsm-71-baremetal/ Good Luck!
  23. You can add this to user_config.json: { "extra_cmdline": { "pid": "0x4200", "vid": "0x13fe", "sn": "xxxxxxxxx", "mac1": "xxxxxxxx", "SataPortMap": "42", "DiskIdxMap": "0002", "disable_mtrr_trim": null } This worked on my N54L
  24. When I had this problem (network down), I could log in to the DSM desktop but all the packages stopped - including ssh. So it doesn't sound like the problem to me. But you DO need to delete the folder anyway or this problem will happen to you as soon as you get a system up.
×
×
  • Create New...