leonade

Flipped from Peter Suh's TCRP M-Shell back to pocopico's "tinycore-redpill-uefi.v0.10.0.0.img" and this has corrected all my issues. No idea what the difference is... Even below on the working environment, I have 0 HBA's listed.

Switched from DDSML to EUDEV Now no drives are detected.

So I rebuilt my TCRP bootloader. I now have Bays 2-12 populated and one of my drives is now being detected as an external drive...

Hi all, I know this is a well-worn topic, but I have not been able to find a specific answer on my situation. I understand how and why the SataPortMap & DiskIdxMap fields are used, (well, I think I understand it enough...) But my questions is: How does one go about determining what these values should be? I am currently running a: · TinyCore RedPill Loader with M-Shell (Latest as of 20240305) · Asus P11C-M4L with all SATA controllers turned off in the BIOS · ASUS PIKE II 3008 8-port SAS HBA card · 12GB/s SGPIO Expander hot-swap backplane that the connects back to the PIKE II card via 2 MiniHD Cables · 12 SAS disks attached to the this backplane · All 12 disks are being presented to Xpenology as individual disk. With: SataPortMap: 1 DiskIdxMap: 00 I end with DSM detecting all 12 disks, but the disk count starts at 02 and goes through to 13. Like other users I am trying to configure my system to use ports 01-12 I have read some comments suggesting that SAS configurations do not utilise the SataPort Map setting, however I find if I manipulate these settings, does affect the disk layout in DSM. As I have disabled my onboard SATA controllers I believe the PIKE Card is the first control which holds 8 ports, evern though via the SAS backplane it has 12 disks attached. As SataPortMap only uses 1 digit to configure the ports, I assume I need to use: SataPortMap: 8 SataPortMap: 1 DiskIdxMap: 00 Assigns my 12 disks from: sdb through to sdm and SataPortMap: 8 DiskIdxMap: 00 Assigns my 12 disks from: sdd through to sdo So these values are affecting my DSM configuration, what I do not understand is how to calculate the HEX values for the DiskIdxMap. I believe setting DiskIdxMap: 00 means that the first disk detected should be assigned to sda. Ssh-ing into the DSM, there is no sda listed, so I don’t believe there are any other disk controllers at play here. Have I misunderstood a concept here? Is there any glaringly obvious I have missed or misunderstood? Cheers, Leon