Decebalus

Members
  • Content Count

    34
  • Joined

  • Last visited

Community Reputation

6 Neutral

About Decebalus

  • Rank
    Junior Member

Recent Profile Visitors

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

  1. Yup! You got it. Trust me, been there, done that Another option is to unplug and plug back the USB stick but it’s faster and more elegant to umount through terminal. Plus it’s safer since unplugging the USB could result in data corruption on the stick. When the partition is mounted by your terminal instance the DSM update can’t write to it, hence the error and the need to unmount it.
  2. That makes no sense. Mine got updated in less than 4 min and was available on the network immediately after that. It does have a xenon CPU but even with a GT CPU it should be under 10 min.
  3. You got it. Plus you have to unmount synoboot2 after you have copied the file with umount. After that you start the manual update from Control Panel. Do not reboot before updating.
  4. It's right in the Jun's loader 1.03b bootloader. Get it from there (from the 2nd partition of 30MB).
  5. Yes, it works. As others have stated, for HP Microserver Gen8, if you have DSM 6.2.2 you need to use the custom extra.lzma. In order to update to DSM 6.2.3 you need to replace the custom extra.lzma with the original one from Jun's v 1.03b. I went through this process with 4 Xpenology servers without any issues. Just make sure you replace the extra.lzma on the USB stick through ssh / terminal before updating to DSM 6.2.3 through Control Panel. You will have to update manually i.e. select the 6.2.3 pat file. For new installation you just need to use Jun's 1.03b original boot loader (w/o any changes) and 6.2.3 pat file. Hope that helps.
  6. - 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
  7. 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.
  8. 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.
  9. 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.
  10. 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.
  11. 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.
  12. 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!
  13. 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...