Decebalus

Members
  • Content Count

    29
  • Joined

  • Last visited

Community Reputation

5 Neutral

About Decebalus

  • Rank
    Junior Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.3-25423 - Loader version and model: JUN'S LOADER v1.03b - DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - HP Microserver Gen 8 - Additional comments: Using built in NIC - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.3-25423 - Loader version and model: JUN'S LOADER v1.03b - DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - ASUS P5Q - Additional comments: Using built in NIC - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.3-25423 - Loader version and model: JUN'S LOADER v1.03b - DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - ASUS P8H61-M-LE-R2 - Additional comments: Using built in NIC - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.3-25423 - Loader version and model: JUN'S LOADER v1.03b - DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - ASUS P5N7A-VM - Additional comments: PCI-E NIC; onboard NIC does not work
  2. It sounds like you have the right steps. To answer your question, yes, you should see the HP microserver with the factory broadcom NIC on the network if you have used the proper extra.lzma v0.5 modified by IG88. That file, plus the rd.gz and zImage files from the 24922 DSM 6.2.2 for 3615xs should be copied to the 2nd partition of 30MB on Jun's 1.03b bootloader for 3615xs. I recommend to redo the steps carefully since it's possible you missed a step in the execution. Always use an extra empty HDD. If you have used the HDD previously, I recommend to erase it, just to be safe there are no DSM leftovers on it.
  3. Duh! I did not unmount the USB stick before loading the .pat file. That's why I was getting the error. So after replacing the extra.lzma file, just unplug and plug back in the USB stick, then proceed with update. Hope this helps others.
  4. I am sure I am doing something wrong. I have mounted the USB stick and replaced the extra.lzma file, however, when I am trying to load the 6.2.3 pat file from control panel, I am getting an unknown error. Now, 2 things I think it is worth mentioning: 1. 6.2.3 does not show up under Update/Restore in control panel - hence trying to install it manually. Is it expected for 6.2.3 not to show up as an available update? 2. I have not replaced zImage and rd.gz files on the stick with the ones from June's loader. Those files are from 6.2.2. Do those need to be replaced as well? Thanks in advance.
  5. Quick update: I have been running 6.2.3 non-stop since yesterday and, so far, it has been rock solid. In fact, with 6.2.2 and the custom extra.lzma used previously, one of the HDDs connected to one of the two extra Marvell SATA ports was dropping from the pool randomly. Not happening any longer with 6.2.3 and June's 1.03b unmodified loader.
  6. That's perfect. Is there a link or a thread that contains those details? What commands to use in terminal? Any help is definitely appreciated.
  7. Since I have installed from scratch 6.2.3 using June's loader 1.03b for 3615xs on one of my old machines, I was wondering what would be the best approach to upgrade to 6.2.3 for those of us who have custom extra.lzma. Would it make sense to boot up with the current USB stick containing custom extra.lzma and after booting up, taking out the stick, reimage it with original June's 1.03b loader (and modifying grub.cfg accordingly, of course), plugging it back in the USB port, install manually 6.2.3 from Control Panel and reboot? Sorry, it may be a stupid question but I have never went through a similar process before. Any suggestions are definitely appreciated and I hope this will help others in similar situation. Thanks in advance!
  8. I am wondering what made them decide to revert back to older driver support. Just asking, not complaining . I pray we will be so lucky with DSM 7.0 - I know, it's a very long shot but still...
  9. I can also can confirm that djvas335 is right! I have installed 6.2.3 using June's loader version 1.03b unmodified (original extra.lzma, rd.gz and zimage) and installing DSM_DS3615xs_25423.pat. That is on a very old hardware using Asus P5Q motherboard. Everything seems to be working fine. I will report later if I encounter any issues. djvas335, thank you so much for mentioning this!
  10. IG-88, I just wanted to say that you are GOD when it comes to trying to keep compatibility with older hardware and I cannot express enough my gratitude and appreciation for all the work you have been doing and the time invested in this! I am sure I am not the only one appreciating all your work, time and dedication. Hats off in front of you and thanks a million, my friend! YOU ROCK!
  11. I apologize up front if this has been clarified/mentioned by someone else, however, I can confirm that it is possible to upgrade from 6.1.7 directly to 6.2.2 using IG-88's extra.lzma without losing the data, by choosing "Reinstall DSM" option and selecting 6.2.2 pat file mentioned by IG-88 in his first post. It goes w/o saying that you will have to reinstall all packages, users, configuration but you are saving a ton of time by not having to restore the data. As I stated previously in one of my replies in this post, I was not able to go through a migration process successfully from 6.1.7 to 6.2.2 but choosing the option to reinstall the DSM worked flawlessly. I have used that approach successfully on my last 2 NAS' that had 6.1.7 (one of them is so old that it has a Q9500 CPU) and are now running happy on 6.2.2. Hope that helps.
  12. Hi IG-88, Sorry to bother you - just have a quick question: do you expect this SATA controller to be compatible with 6.2.2? https://www.amazon.ca/dp/B081DM6Y9L/ref=pe_3034960_236394800_TE_dp_1 I can't tell if it has a port multiplier or not (even though each SATA port is placed separately on the board). Thanks in advance for your help, as always.