jensmander

Hi. HP StorageWorks? Das ist ein SAN-System, kein normales 2HE Servergehäuse... Poste doch zunächst einmal, was Du überhaupt haben willst. 1.) Anzahl HDDs und Kapazität (2TB, 4TB, 6TB, usw.)? 2.) Typ HDD? S-ATA oder SAS? 2,5" oder 3,5"? 3.) Welches RAID-Level ist gewünscht? 0, 1, 10, 5, 6, etc.? 4.) Wie sieht es mit der Infrastruktur aus? Ist ein "normales" 08/15 Gbit LAN vorhanden? Soll mehr als 1Gbit Datendurchsatz erreicht werden (bspw. über LACP/Trunking), muss sowohl die Switch als auch die Client-Seite entsprechend ausgestattet und konfiguriert werden. 5.) Budget?

Did you check your BIOS for any activated security options (User, Master, etc.)? It would be interesting to place both drives in slot 1&2, enable the raid mode and boot a live linux. Within the live os you could try "hdparm -I /dev/sd*" (where * is a, b or c - boot stick and hdd1&2) from a console. The output should display informations like this: Commands/features: Enabled Supported: * SMART feature set Security Mode feature set * Power Management feature set * Write cache Look-ahead * Host Protected Area feature set [...] Security: Master password revision code = 65534 supported not enabled not locked not frozen not expired: security count supported: enhanced erase [...]" You should get a clue if any security features are enabled or not on the drives.

Hi. Yes. I have two Gen8, each filled with 4x4TB in AHCI mode. One with 4x WD Red Pro, the other with 4x Seagate ST4000VN003. Which BIOS version does your Gen8 have? And did you try smaller models in port 1&2? Did you save your BIOS settings as user defaults?

1.02b worked on three different bare-metal systems for me. Previously installed version: DSM 6.1.2-15132 @ 1.02a - HP MicroServer Gen8 with Xeon - Intel Z77 with Core i7 - AMD A78 FCH with A6 All systems started in "recovery mode" (DHCP). After a quick repair all systems run fine with their original configuration incl. SSD cache on the AMD system.

A connection over a serial port is just easier but not the only way to fix this. As mentioned in my 1st post it's possible to boot from a live linux, mount the system partitions and copy the files. Just in case you don't have a serial port/cable/etc. on consumer hardware (the HP MicroServer Gen8 has a virtual serial port to which you can connect with putty via the iLo address).

I discovered that creating a bond fails when your MAC adresses differs (real MACs vs MACs in grub.cfg). Had this problem on HP ProCurves and a TP-Link switch. After I corrected the MACs in my grub.cfg everything worked.

Before applying any brand new updates always search the forum for issues with this version. Many (brave) users post their experience with new versions of DSM and it's updates. The reason for your problem is described here: If you have important files on your NAS I recommend to backup these files first. You can boot from a live linux, mount the data partitions and backup your stuff. After that you can retry your "old" V1.02a flash drive and copy the files on your system partition(s) from /lib/modules/update to /lib/modules You can do this either with a serial connection or with a live linux. Both ways are described in the above linked topic.

The test system runs (again) on 6.1.2-15132 but I don't recommend to upgrade any live system.

P.S.: I didn't want to say that it's safe to install this update! I was lucky to get the system up again but I won't install it on my other bare-metal systems. So be aware of this update!

Today (2017-06-15) DSM 6.1.2-15132 has been released. I tried an update on a bare-metal Intel system (Loader 1.02a, DS3615XS) with NO luck! To get the system up and running again you have to boot from a live linux system, mount the system partitions and copy all files from /lib/modules/update to /lib/modules After that unmount the partitions, shut down the system and plug in your XPEnology boot stick/card. Polanskiman wrote an excellent tutorial on how to gain access to this partitions:

Sorry, your're right. It should be 1.02a - not 1.02a2. Link: https://mega.nz/#F!BtFQ2DgC!JgomNP3X8V9EuwxL4TXbng!5kcjyJ7R

Hi. Before any upgrade please take a full backup of your important data. There is no "Do it so and it will work!" guide. I can describe how I updated my bare-metal systems from 6.0.X to 6.1.1 (including a Gen8 MS) - Backup your data - Disable any SSD cache - Shut down your server - Unplug your boot stick or micro-sd from the server and open it's grub.cfg - Write down the important modifications and entries like serial no., macs, sataportmap, etc. - You can either write the new synoboot.img to your old boot device or use a new one - Download the 1.02a2 image for DS3615XS from here: https://mega.nz/#F!BtFQ2DgC!JgomNP3X8V9EuwxL4TXbng!Fwki3A4B - Use a tool like OSFMount to mount the synoboot.img (15MB partition) and uncheck the "read-only" option, open it's the grub.cfg - Check the VID & PID of your new device or (if you intend to use your old boot medium) use the old values - Fill in the entries mentioned above (vid, pid, serial, etc.) - Save the image and unmount it - Write the image to your desired boot medium with Win32Diskimager, plug it into to your server and let it boot - Log in to DSM and go to the control panel -> Updates & Recovery - Download the official PAT file from Synology: https://global.download.synology.com/download/DSM/release/6.1.1/15101/DSM_DS3615xs_15101.pat - Select "Manual update" and upload the previously downloaded PAT - Confirm the update and let the server reboot (this can take a little bit more time as usual) - If anything went smooth you should be able to re-login into DSM - Apply actual Update 4 and after another reboot everything should be finished

Welches Dateisystem? Neben der 2.4GB Systempartition, die auf jeder HDD erstellt wird, wird bei BTRFS im Gegensatz zu EXT4 mehr Speicher belegt.

Tried it with a PE version of Macrium Reflect and it worked flawless. But - as sbv3000 mentioned - all HDDs were of the same size and modell. Cheers

@IG-88 Das ist nicht ganz korrekt. Der 1.02a2 ist sowohl für die DS3615 als auch für die DS3617, es gibt 2 Versionen. Man sollte bei der DS3615 bleiben. Dass man sich die NAS schrottet, ist nicht garantiert, natürlich möglich. Deswegen der Hinweis auf die Vielzahl an Hardwarekombos, wo es gut oder schief gehen kann (und niemand definitiv sagt: "Klappt bei Dir auf jeden Fall!"). Das war aber schon immer so bei XPEnology Mit o.g. Methode habe ich bereits 12 bare-metal Systeme erfolgreich aktualisieren können. Schönes Wochenende!