September 22, 20205 yr Hi, I am trying to setup an Unraid server my goals are - use Unraid as a NAS - use Unraid with a win10 VM - run filemaker on vm Now i am having trouble with Unraid before reboot everything in the array looks fine After reboot in this case disk 1 is a unassigned drive. its says its missing but the drive is there. Now when i look assign the drive to Disk 1 it says its wrong. Can someone tell me whats wrong ?
September 22, 20205 yr Post your diagnostics (Tools - Diagnostics) - add entire zip file to your next post
September 22, 20205 yr It looks like you assigned the drive originally when it was on a built-in SATA port. Now you've moved it to your SAS controller, and it has changed the device identifier. Cross-flashing the controller to IT mode fixes this. (or move it back)
September 23, 20205 yr Community Expert 1 hour ago, Squid said: Cross-flashing the controller to IT mode fixes this. (or move it back) There are other good reasons for IT mode. Currently there aren't even any SMART reports for your disks, for example.
September 23, 20205 yr 2 minutes ago, trurl said: There are other good reasons for IT mode. Currently there aren't even any SMART reports for your disks, for example. Yeah, I forgot to mention that. Russian Roulette with hard drives isn't a good thing unless you're a Deer Hunter
September 23, 20205 yr Author Thanks for al the quick replys. Call me stupid but i dont get it i did not change the drives. The r710 has 4 drive bays connected to the sas controler not to a SATA port. When i start a new config and start over the same thing happens. after reboot it kicks out the drives
September 23, 20205 yr Community Expert HBA is crashing and keeps re-initializing: Sep 22 09:10:01 BMS kernel: mpt2sas_cm0: fault_state(0x2665)! Start by updating the firmware since it's on a very old one: Sep 22 09:10:03 BMS kernel: mpt2sas_cm0: LSISAS2008: FWVersion(02.15.63.00) Current one is 20.00.07.00
September 23, 20205 yr 45 minutes ago, Swelgje said: Call me stupid but i dont get it i did not change the drives. The r710 has 4 drive bays connected to the sas controler not to a SATA port. When i start a new config and start over the same thing happens. after reboot it kicks out the drives I am no expert on disk controller but I think I can give a bit more context to the suggestions of JorgeB, trurl & Squid. You are apparently using a RAID card that passes some information to the system and unraid. But a RAID card generally does not passes the drives S/N but some value that it assigns to each drive. However, this value is not always kept the same on each reboot. This might not be an issue for some type of application but unraid saves the disks allocation using the disks S/N. If unraid cannot find those identical S/N, unraid cannot do the assignement. That's why trurl suggests to flash your RAID drive into another mode (IT mode). Also, seems a good idea as JorgeB suggested to use the latest firmware.
September 25, 20205 yr Author Hi Guys, Thank you for all your input. I had updated the sas card and bios ect ect. Now it stays good when i reboot. however i need to flash the h200i to TI mode. can some tel me how to do this for this card ?
September 25, 20205 yr Community Expert According to the syslog it was already in IT mode, just on a very old firmware.
September 26, 20205 yr Author Where can i see if its in IT mode ? I update the controller to via the dell suport website Sep 26 06:58:26 BMS kernel: mpt2sas_cm0: LSISAS2008: FWVersion(07.15.08.00), ChipRevision(0x02), BiosVersion(07.11.10.00)
September 26, 20205 yr Author i tried to flash it to IT mode where can i see if i done it right ? Version is now correct but i stil cant see if its in IT mode mpt2sas_cm0: LSISAS2008: FWVersion(20.00.07.00), ChipRevision(0x02), BiosVersion(00.00.00.00) diagnostics-20200926-2008.zip
September 27, 20205 yr Community Expert Sep 26 10:02:31 BMS kernel: mpt2sas_cm0: Protocol=( Sep 26 10:02:31 BMS kernel: Initiator Sep 26 10:02:31 BMS kernel: ,Target Sep 26 10:02:31 BMS kernel: ), IT Mode = Initator-Target Mode
Archived
This topic is now archived and is closed to further replies.