MarsManden

Could this be your problem?

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.4 15217 Update 3 - Loader version and model: Jun's Loader v1.02b - DS3615xs - Installation type: 1 * Baremetal on HP N54L, 2 * ESXi 6.5 on HP Microserver Gen8 - Additional comments: Requires reboot

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.4 15217 Update 2 - Loader version and model: Jun's Loader v1.02b - DS3615xs - Installation type: Baremetal (HP Microserver Gen7 (HP N54L)) and virtual on VMware ESXi v6.5 running on HP Microserver Gen8 - Additional comments: Updated through "Control Panel, Update & Restore" - Requires reboot - Info shows Update 3, DSM Date 2017/12/14

HP Microserver Gen7 N54L, bare metal 1.02b Juns loader DS3615xs DSM 6.1.4-15217 Update 2 - OK No reboot required Manual reboot - OK ESXi v6.5.0 on HP Microserver Gen8 1.02b Juns loader DS3615xs DSM 6.1.4-15217 Update 2 - OK No reboot required Manual reboot - OK

Loader: Juns v1.02b, Internal USB stick DSM: 6.1.3U7 Hardware: HP Microserver Gen7, 2GB RAM, BIOS Mod O41100113.ROM, 5*4TB WD Red

Hi You should follow this subforum for new updates: https://xpenology.com/forum/forum/78-critical-updates/ But so far it seems okay, according to this thread:

Updated one virtual DSM 6.1.3-15152 U6 to U7 on ESXi from GUI. ESXi v6.0.0 running on HP Microserver Gen8. Rebooted fine - no issues noted so far.

VM on ESXi 6.0 DS3615xs Jun's Mod v1.02b Updated from DSM 6.1.3-15152 update 5 til update 6 using control panel System rebooted without errors - all seems OK.

Which BIOS are you using? Native? If native then upgrade the BIOS - see this guide. http://www.nathanielperez.us/blog/hp-proliant-n40l-bios-modification-guide I know it's for a N40L, but the steps are equal for a N54L - and I've checked the BIOS file in the pakage, it's identical to the BIOS-file I've used on my N54Ls. Note that you have to flash twice according to the guide. Once with the original O41 BIOS and next with the MOD version of the O41 bios. The MOD bios activates a LOT of new settings in BIOS, so be careful! When you're running the new BIOS, do these settings to activate AHCI on all 5 SATA ports. And remember to disable C1E also! To enable AHCI on all ports, go to Southbridge Config, SATA 4/5 and disable sata 4/5 IDE mode. From the main screen go to ‘Chipset > Southbridge Configuration > SB SATA Configuration’ and make sure your settings are the same as below: OnChip SATA Channel = Enabled OnChip IDE Type = IDE SATA IDE Combined Mode = Disabled SATA EPS on all PORT = Enabled SATA Power on all PORT = Enabled Return to the main screen then go to ‘Advanced > IDE Configuration’ and again, make sure your settings are the same as below. Embedded SATA Link Rate = 3.0Gbps MAX are the settings for sata Then you should have no problems - I'm running two N54L servers with this BIOS and settings, both with five disks.

Upgraded 3 Xpenologys. 2 DSM v5.2 (5565) XPEnoboot (XPEnoboot_DS3615xs_5.2-5565.2) running on ESXi v6.0 on HP Microserver Gen 8 with Intel Core i3-3240 - Juns loader v1.02b DS3615xs. Just changed serial, MAC and timeout in grub.cfg 1 DSM v5.2 (5565) XPEnoboot (XPEnoboot_DS3615xs_5.2-5565.2) running bare-metal on HP Microserver N54L - Juns loader v1.02b DS3615xs. Just changed serial, MAC, VID, PID and timeout in grub.cfg. All upgraded from webpage (ip-adr-on-nas:5000). All went smooth. A few pakages needed upgrade after upgrading DSM to v6.1.3, but after that all is running. A note to others - ran into the problem, that upgrade stopped at 56% on my bare-metal server and returned to install page with error 13. Tried rewriting the USB stick several times, but same problem. Then tried another USB stick - problem solved.

I've used this command to remove scsi-hpvsa from my HP Gen8: esxcli software vib remove -n scsi-hpvsa -f Notice that I don't have the driver prefixed with 'Hewlett-Packard:'. Don't know if that's the reason why you get the error when trying to remove scsi-hpvsa.

Use this guide - just replace 5565 with 5592. It really is fairly simple. http://xpenology.me/how-to-update-to-dsm-5-2-5565/

Don't upgrade to 5.2-5644 - not safe yet. Stay on 5.2-5592 for now.

I'll second that - option 1.

Hi - as far as I know, no. If you want to access data on an existing disk, you have to attach it to the USB-port. DSM wants to initialize the disks attached to the SATA ports, which means it wants to create 2 small partitions in the beginning of the disk to hold the DSM system. The rest of the disk is used as your data volume. If you allow it to initialize the disk, DSM will delete all existing partitions on the disk, and thereby delete your data on it.