J3d1UK

I have iLO and a built in virtual serial port already which was set up ready to go - Sadly nobody replied to my thread - But it was Kernel panic the HBA controller and crashed at .pat install (on the 3622xs install)

Its a shame as it would run "fine" on the Gen 8 microserver (some little errors such as network slowdowns via 10gbe, but certainly useable) I can only assume its to do with drivers / assignment / Kernel - I wish I could help further to modify something so it could be a "one size fits all" for Tinycore, sadly I don't have the knowledge to do so. I suppose the positive is that if the drivers and kernels were tweaked, it could indeed work - but not really feasible on such a small project to get everyones hardware running (especially server grade items)

Disregard this thread, switched to openmediavault and everything working perfectly first time including nvme and 10gbe network card, P840AR in HBA mode (smart data values showing correctly on drives in OMV too). And used R-Sync to mount remote folders and transfer all of my data over at full speed of what the drives are capable of. Docker up and running, with Shinobi to replace Surveillance station.

I contemplated this but the USB drives I have, in ideal situations transfer at around 80mb/s MAX so wouldnt really show any meaningful information - I do have a couple of spare nvme drives I could try with, but I would imagine that those are nigh on impossible to get working with Xpenology.

Yep, it does seem to be a limitation sadly, Looks like I will just set up rsync and wait a long time for the data to sync / copy over from one to the other - OR finally take the plunge into a supported system, sadly as time has gone on it appears Xpenology isnt feasible anymore given the amount of little problems that appear, which is a shame as I love the Synology Surveillance station and how it integrates with Home assistant.

Sadly not, the kernel for 3622xs crashes the Raid card when in HBA mode - but you are probably onto something - this project certainly doesnt seem to like my hardware (edit: Ive just tried ubuntu booted from USB on the microserver to to a ubuntu boot CD mounted in esxi and all was very speedy and stable, so more than likely xpenology again sadly - its appears to hate me)

Sadly not, same outcome - great suggestion that I had not tried however, so I appreciate the suggestion.

Nobody answers any questions outside of the thread, i've tried before when i first ever installed Juns loader on a Microserver N54L and then a Microserver Gen 8, and I did that here 2 days ago https://xpenology.com/forum/topic/65689-ds3622xs-image-crashes-hp-dl380-gen9-p840ar-hba/- It seems nobody can / will help - They appear to be concentrating on getting the menus looking nicer...or adding a new way of doing exactly the same job that's already available but called something slightly different, or a different .sh version of it (Which is fine, its their own time and they are helping most people). For clarity - The server has run for many years perfectly at work (For MUCH more intensive things)- in an ESXI environment, and is running now in ESXI perfectly, the drives have all been checked as perfect, and its happily running now - its the kernel / driver....and compatibility with the server hardware I would imagine (I can recreate the problem on another server with the same spec, processor, More RAM but using a P440ar RAID card and 24 x SFF drive bays - I'm lucky enough to have both, free from work)but given I'm using proper server grade hardware and not some cobbled together 20 year old parts which most people wont have access to - I would imagine its not an easy problem to fix or diagnose. So, to confirm, its doesn't work on 2 different DL380 Gen9 Servers, with slightly different RAID cards and different drives - Both work with RAID enabled and singular RAID 0 created for each drive, both Kernel panic when HBA mode is enabled and you install the .pat file after loader creation. The fact it works fine on the 3615xs "End of life image" means something has been changed in the newer images (3622xs+) and not changed in the 3615xs - Sadly i'm just not intellegent enough to know what that is or how i would go about rectifying it!

Hi All, SLOW TRANSFER SPEEDS Trying to transfer my data from my old NAS (HP Microserver Gen 8 - Baremetal) to my New NAS (HP DL380 G9 12 Bay LFF - ESXI). Both have the same 10GBE X520-T2 card in them (aswell as the built in cards), patch cable between them, have them both running a DS3622xs 7.1.1-42962 image. I have set the IP addresses on a different range for both X520-T2 cards within Synology (192.168.5.x) Mounted a virtual folder in the new NAS from the old on in Filestation using CIFS (\\192.168.1.x\Backupfolder) When i try and transfer from the Mounted folder to the new folder in diskstation to migrate the data (by dragging and dropping) I get an initial transfer speed of 160MB/s - after around 3-4 minutes that then drops to 60 mb/s (ish). I have enabled MTU 9000 on both network cards in DSM (and also i in ESXI for the virtual card) - link speed showing at 10000mbps as it should, jumbo packets enabled. I have around 20TB to transfer so this isn't acceptable - any ideas? - I cannot run both machine as baremetal sadly as the DS3622xs image simply kernel panicks the P840AR HBA when trying to instal the .pat (thats why ive had to settle for virtual)

UPDATE: Just for verification the HPSA driver is being recognised and installed correctly, I have also manually added it into the images. I can Install 7.0.1-42218 loader and install the .pat file correctly, so something is different between these DS3622xs-7.1.1-42962 - NOT WORKING - Crashes the HP P840ar RAID / HBA controller (The one I want) DS3622xs-7.0.1-42218 - WORKING DS3615XS-7.1.1-42962 - WORKING Any ideas? Anyone at all please ?

Hi Mate, Cheers for the reply, yep, added that manually a few days ago (although it had already added and built it in - hence why it was working correctly when creating a hardware RAID in the BIOS) It appears whatever version of the HPSA driver is being added via the pocopico repository isn't suitable for the P840AR controller on a 3622xs-7.1.1-42962 sadly, as soon as it gets to installing the PAT it simply crashes the card (when in HBA mode). I can only presume the DS3615xs image build is using an older version of this driver? - Again, works fine with that one! EDIT: Just tried an older version of DSM DS3622xs-7.0.1-42218 - Installs fine.....so its the recent images that are broken (for me) So the question is - What is different between 7.0.1 and 7.1.1 images that are being built...

Hi all, Using ARPL or TCRP I have the same problem on my rack server. I can generate the USB boot drive fine on both TCRP and ARPL, have verified the Hpsa driver is being added (sataportmap recognises the 3 disks connected to the P840ar) when building the loader, my problems start when Installing the .pat file, on the ds3622 image, always fails between 60-70%, fans ramp up on server and HBA card crashes, have to reboot to get it back. If I turn off HBA mode in the Bios for the P840AR, enable raid, create Raid 0 for all separate disks, Ds3622xs installs fine (but this is wrong as no smart data etc) Install works perfectly when using the DS3615xs image in HBA mode on TCRP, but not in ARPL, although successful on TCRP, it only shows 2 cores, id prefer to be on DS3622xs - anyone have any ideas.

Jusr done this manually - still fails at same point, fans ramp up on the server at about 60% indicating the P840AR card has crashed, seems to be the problem and nothing I can do to fix it....disappointing. EDIT: Just flashed back to 3615xs and all working....so, basically, its the "updated" images such as 3622xs / process being pulled thats the problem. Glad its not me.

Yep, just done it manually too - same problem...

It appears in the modules list when i first boot to configure the loader, I was under the impression it loaded the modules automatically as I have not manually selected any of them (and when card is in RAID mode instead of HBA - installs fine? - I just REALLY need it to be in HBA mode before I can switch all my data over!)

Can anyone help me with a problem please? Baremetal Install - HP DL380 Gen9 12 x LFF Bays / P840ar Card in HBA mode / E5-2640 v4 / 32GB RAM Image used: DS3622xs (have also tried 3615, 3617 with the same result) Followed the guide through, I get to install the .pat file, fails at 69-72% - Drives appear to be showing, however if i retry, fails at 0% (almost like the p840ar is crashing) I CAN get this to work if i put the P840ar card into RAID mode, create a new raid for EVERY drive to a RAID 0 seperately - however this then doesn't forward any smart data etc to DSM - but does allow me to install correctly and get up and running - I'd like to get this working as I would like to get rid of the Microserver gen8 its currently on (I want more drive bays)

Sorry again for the re-quote - Could you be so kind as to tell me how to add the hpsa driver, Im loathed to start transfering all my data from my Microserver gen8 before doing this.

I've used ARPL instead which apparantly autodetects and has all the drivers built in - but still wont work without doing hardware raid (on the 3622 image) - I believe when I used TCRP method i set satamap and diskidx to something like 0 and 0x0 - or something similar, given there are no SATA controllers present (was the same for Both the 3615 and 3622 images - although recognised drives in both - just wouldnt install DSM after 50+ % on the 3622)

Got this working on a Baremetal HP DL380 Gen9 With LFF drive bays - Strangely I had to turn OFF HBA mode on the P840AR Raid card (which works in HBA mode on TCRP but on the DS3615xs image). For this to work, I had to enable the smart storage controller RAID mode, set up each individual disk in RAID 0 (so they all present to DSM as a single disk each) and lo and behold, success. Any ideas why it wont install the 3622XS PAT file when i'm using HBA mode? - I have always though hardware raid is a bad thing on things like this and it is preferable to have HBA.

To follow up and this, I have solved the problem with not being able to use the DS3622xs Image! Simply put it was the P840AR card was in HBA mode, as i would believe it should be! (and worked on 3615xs) I changed it back into "RAID" mode, set up a RAID0 for all the drives seperately (so they present as a single drive) and voila, All working now. The problem I have is, with the controller in RAID mode, I believe this is non optimal for something that uses software RAID.....Still very strange it works on the 3615xs image and not the 3622! I'll keep beavering away!

Yea, that was my thoughts exactly, it does seem strange - Processor is a E5-2620 v4 - So shouldn't be an issue - I Do have another DL380 g9 (My main server with my Ubuntu 22.01 home server + docker apps etc on it, MacOS VM, server 2019 image etc etc) with ESXi on it and I have spun a quick image up on that with the same problem - (that does have a different processor however, 10 core instead of 8 ) I can literally set it all up as the 3615xs and then Change the loader to the 3622XS (or 3167xs) and it fails at pat install exactly the same - I can then rebuild the loader back to a 3615xs and it works again (although have to reinstall the .pAT)- Have been at it all day now - I mean it doesn't matter TOO much as its working - but I am intrigued!

Hey all, Don't suppose anyone has managed to get any other image higher than a DS3615xs on a HP DL380 G9 Baremetal? (HBA mode enabled on RAID card - P840AR) - I can get the 3615xs booted, installed and recognising drives but any other image (I have tried 3617xs and 3622XS+ to no avail - always fails when installing the synology .pat file) Just refuses to install.

- Outcome of the update: SUCCESSFULL - DSM version prior update: FRESH INSTALL - Loader version and model: Jun's Loader v1.03b - DS3615XS - Using custom extra.lzma: No - Installation type: BAREMETAL - HP Microserver Gen 8 - Standard components - Additional comment: Install 6.2-23739 PAT first, then manual install from within Synology of 6.2.3-25426 - will auto update to U3 on manual install of 6.2.3.