[LSI 9300-16i HDDs not showing up]

FYI that i just found. see this article from the TrueNAS forum site that has a non-public 16.00.12.00 firmware for the 9300-16i. 

 

Page Link: https://www.truenas.com/community/threads/lsi-9300-xx-firmware-update.85768/

 

SAS 9300-16i Firmware 16.00.12.00

    Download Link: https://www.truenas.com/community/resources/lsi-9300-xx-firmware-update.145/download

 

Also i setup a temp system with windows on it and loaded the Broadcom LSI Authority app on it. it makes identifying and updating firmware really easy!! (note that LSA is the replacement for the MegaRAID Software)

This is the latest version that i could find (ignore that it says for RAID)

 

 

Page Link: https://datacentersupport.lenovo.com/us/en/downloads/ds559924-lenovo-storage-devices-raid-adapter-windows-utility

LSA version = 008.002.017.000

    download link: https://download.lenovo.com/servers/mig/2022/12/09/56543/lnvgy_utl_raid_mr3.lsa-202208260254-0041_windows_indiv.zip

 

[Unraid Forum 100K Giveaway]

UNRAID has opened up the options for efficient and economical storage and so much more!! So much that we have two systems and we are on out 3rd (T3 aak Tower3) version of deployment. It keeps on getting better every day with not only the UNRAID Team, but the UNRAID community! We are in it all together!

 

Better Windows (yes i know) compatibility for domains (not business production, but lab production). 

[Unable to join Domain]

Unfortunately even after thinking it was fixed after we went live the SMB shares would not allow connectivity seemingly random. 

We had to disjoin from the domain and go back to a workgroup style. Once we did that it's been super stable. I know that unraid is Linux and it's not an enterprise platform, but it should be able to do this. We were migrating from an older unraid hardware setup to a new one and are just waiting for the dust to settle on the new hardware. Once that's done we'll wipe clean the old one and I'll have a chance to use that licensed stick for a new smaller deployment for testing purposes. The first thing I am going to test/try is AD join using what I have learned from the above. I will try and document what I can and share with the group. 

Sorry for the not helpful news (so far). 

[Unable to join Domain]

One other thing to note is that our system is still pre-production and we hadn't changed the root password from being blank. after changing it to a secure one (or any one) a number of the applied permission errors we were seeing are now completing successfully. 

don't know if this helps or does nothing, but just one more thing to review. if you are having a similar issue. 

[Unable to join Domain]

i am having the same problem. Server 2012R2 as DC01, 2016 as DC02. 

The main issue i have with the AD join page is that there's no "test credentials" function. i have no idea if it's a real error or human error. Nor are there any (that i can find with any ease) documentation as to what is expected in the fillable fields under the SMB "Active Directory Settings" (noted below). 

other Linux servers have joined before and way back when i was on my first unraid (running 5.x OS) tower 1.x (i am now on T3.0 [running 6.7.2]) 

 

as a last test i created a copy of my domain admin account called it t3admin, then created a AD security group called t3users. this was to eliminate the possibility of a code bug where a space in any of the names was causing an issue. 

 

::note for admins to review the code:: Solved, but not really solved. 

ok, in the middle of writing this my friend and i were able to join our T3 to the AD domain. it might be a fluke, but something to note is that after, or maybe in the process, of submitting the join attempt the SAMBA service/process either doesn't re-load or crashed upon re-load. this would cause share browsing issues and also AD join. note the below format of the fields i used and in the middle of joining my friend started SAMBA when it when down

 

User: t3admin

AD security group: t3users

::note it's not best practice, but both of the above user and group are in the root "Users" OU. i note this for replicating the test criteria if needed:: 

DNS FQDN: t3.mydomain.com

 

AD domain name (FQDN): mydomain.com
AD short domain name: myworkgroup
AD account login: t3admin

AD account password: 

AD initial owner: t3admin
AD initial group: t3users

 

Any questions feel free to ask. i will try to help and answer. 

 

Pete T.