When I have seen semaphore errors it is normally due to Windows Storage and NIC drivers, that during flash-write operations the hardware semaphore is released too soon during the write process. If another software component begins to access it prior to the completion of the ongoing write-process, flash corruption could result. I generally only see it occur with firmware updates though, so I am not certain of the connection here. With those software fixes are needed in the Windows NIC drivers (which you stated are current) as well as corresponding NIC Management-API/Agent as well. This is to properly acquire the semaphore for the entire operation. The applications must also be updated to include the corrected NIC Management API too.
I would also make sure that the server is also current on its BIOS and iDrac as well.
I have been working to sort this out for a few months now. The server has been decommissioned and is now in my office for me to try and figure out why we can not copy large files from an external drive over the network to the server. I have updated the firmware on everything I could find firmware for and tested with as many different OS configurations as I could think of. I found that copying to the system drive, which is not Raided but is on the same controller, works. I have redone the RAID. This time it is RAID 0 and not RAID 5. The copies are now completing successfully. So My question is, is there a setting when creating the RAID 5 that might have something to do with what I am seeing?
DELL-Chris H
Moderator
•
9.7K Posts
0
March 29th, 2019 06:00
Denis.Muesy,
When I have seen semaphore errors it is normally due to Windows Storage and NIC drivers, that during flash-write operations the hardware semaphore is released too soon during the write process. If another software component begins to access it prior to the completion of the ongoing write-process, flash corruption could result. I generally only see it occur with firmware updates though, so I am not certain of the connection here. With those software fixes are needed in the Windows NIC drivers (which you stated are current) as well as corresponding NIC Management-API/Agent as well. This is to properly acquire the semaphore for the entire operation. The applications must also be updated to include the corrected NIC Management API too.
I would also make sure that the server is also current on its BIOS and iDrac as well.
Let me know.
Denis.Meusy
1 Rookie
•
2 Posts
0
June 27th, 2019 16:00
I have been working to sort this out for a few months now. The server has been decommissioned and is now in my office for me to try and figure out why we can not copy large files from an external drive over the network to the server. I have updated the firmware on everything I could find firmware for and tested with as many different OS configurations as I could think of. I found that copying to the system drive, which is not Raided but is on the same controller, works. I have redone the RAID. This time it is RAID 0 and not RAID 5. The copies are now completing successfully. So My question is, is there a setting when creating the RAID 5 that might have something to do with what I am seeing?