Leaderboard

Извините, но при Вашей приверженности к самостоятельному и критическому подходу, любые мои советы попросту неуместны.

Its not a bug, its a feature. DSM really expects smart data from the disks. Hypervisors might pass smart data or may not. Smart shim gets here to help when there is no smart data coming from the disks. It fakes smart data for DSM to be happy.

Hi just wanted to say that I have always had problems with xpenology with the max disk settings over 24-26 disk. I have never been able to figure out why? There would be random crashes of the disk array, some times would loose connection, and a list of other weird things. This goes all the way back to DSM 6.0, your mileage may vary tho. Just wanted others to be aware of my experiences with high drive count.

I was able to find a solution with the devices all on the first virtual SATA controller. I'll post sample dts files when I can get the second controller working. EDIT: ESXi virtual sata controllers have 30 slots. After the first one, subsequent controller ports that are continuously enumerated in sequence in tinycore, which render them inaddressable. The DTS should be edited so so that all virtual SATA ports are referenced from zero (MOD 30 will handle all possibilities). I assume that this dts/dtb approach to port management means that partial population of a SATA controller will mean non-populated ports are non-functional. Therefore, a rebuild of the loader would be required if disks were added, correct?

Set user_config.json as below maxdisks = 36 internalportcfg = 0xfffffffff

The order I guided was wrong. Ttyd is not yet available Do the following in TC Linux. Use the command below to secure the ./redpill-load directory ./rploader.sh build apollolake-7.0.1-42218 Send the automatically added ext list with the command below first. ll ./redpill-load/c*/e*

Does the Intel X520-2 have dual ports?

Use the command below to secure the ./redpill-load directory ./rploader.sh build apollolake-7.0.1-42218 Send the automatically added ext list with the command below first. ll ./redpill-load/c*/e*

You were DS918+, not DS3622xs+. This is another matter. I don't know how many NICs there are It would be better to check the log first. It may be difficult, but send the log using the method below. If you can access the DSM installation request screen with ttyd as below, Then send me the log with the command you see. http://<youripaddr>:7681/
 id : root / pw : ( no password ) cat /var/log/junior_reason cat /var/log/*rc* P.S: Are there any additional NICs other than this 10GB NIC? You already have two NICs. Then I should be able to get an IP grant from 1gbe Perhaps the intel X520-2 is interfering as below intel X520-2 10gbe intel 1gbe Loading kmod #0 "dca.ko" for pocopico.igb (args: ) Loading kmod #1 "igb.ko" for pocopico.igb (args: ) Loading kmod #0 "udp_tunnel.ko" for pocopico.ixgbe (args: ) Loading kmod #1 "ip6_udp_tunnel.ko" for pocopico.ixgbe (args: ) Loading kmod #2 "dca.ko" for pocopico.ixgbe (args: ) insmod: can't insert 'dca.ko': File exists ERROR: kernel extensions "dca.ko" from pocopico.ixgbe failed to load Exit on error [99] rp ext init exec failure...

If the redpill-load directory is still in the TC, Under ./redpill-load/c*/e*, you will see three or more directories as follows: pocopico.e1000e pocopico.igb pocopico.ixgbe If you don't have a redpill-load in advance, ./rploader.sh build broadwellnk-7.0.1-42218 build first to obtain the redpill-load directory. Among them, the pocopico.ixgbe is deleted by force with the sudo rm -rf command Perform the ./rploader.sh build broadwellnk-7.0.1-42218 manual to rebuild the loader without pocopico.ixgbe. DS3622xxs+ already contains vanilla ixgbe ext, so I understand that it should not be added again. Since I don't actually have the above NIC, I haven't tested it myself and only know it in theory.

yes i did mate, was just checking, i did get to load with the 10gbe connected but when i rebooted it didn't come back. still working on it tho lol cheers bud

sure you can do, i thought you've already tried that.

got it now, i tried so many combinations and forgot to switch back to usb Thanks Pocopico!!

Did you follow @haydibe instructions for creating the VM ? The loader disk has to be on USB and the USB boot option has to be selected at GRUB. Please see his signature for details.

Пора переходить от слов к делу )))

Тогда вполне хватит и под Докер для Хоум Ассистента (или Бриджа, кому что ...) хватит