[Drive Disabled, Request Advice]

16 hours ago, JorgeB said:

Looks like a SATA cable problem, replace the cable and if the emulated disk is mounting and contents look correct you can rebuild on top.

Thanks for the reply, the cable is from the raid card and is a mini sas to 4 sata break out cable (not the exact cable I have just an example of it), should I replace the whole cable or just swap to another of the 3 sata connectors on the cable? The case is also a Silverstone ds380b so the cable plugs into the hotswap pcb.

 

Also with the rebuilding it is to deselect the drive, run the array, turn off the array, then re-select the drive?

[Drive Disabled, Request Advice]

Hello, just today one of my drives (Disk 2) because disabled with the red X (Unraid 6.9.2). I have attached the diagnostics for it as well. I was transferring some files on it when it started to get errors for example (Jun 26 09:27:53 Tower kernel: md: disk2 write error, sector=194517880). A little bit before this started happening I had gotten a notification about "UDMA CRC error count" for the drive as well.

 

I am not sure how to proceed and am asking for any advice on what appears to be the issue and how to resolve it, like if the drive is starting to die and should be replaced etc or some other action needs to be taken.

tower-diagnostics-20230626-1009.zip

[(SOLVED) Smart Error: Offline uncorrectable/Current pending sector]

35 minutes ago, trurl said:

For future reference, Diagnostics zip already includes SMART for all attached disks and syslog since reboot, so no need to attach separately.

 

# 1  Extended offline    Completed: read failure       50%      9570         8595749280

 

Replace disk.

Thanks bud, good to know it is only diagnostics that I need to attach, will look at replacing the disk.

 

I really appreciate the help

[(SOLVED) Smart Error: Offline uncorrectable/Current pending sector]

Hello, I recently got a notification in Unraid of Offline uncorrectable/Current pending sector errors, where both have a value of 16 on the drive "ST8000DM004-2CX188_WCT00DET - 8 TB". I ran a SMART extended self-test and got a "Errors occurred - Check SMART report" result, I have included the Smart Report as well as diagnostics and Syslog as I don't really know how severe of an issue it is.

I have seen in other posts about this issue that it may not indicate the drive is dying, but I would just like some feedback if possible if the attached logs etc can help determine the severity and if it is dying and should be replaced.

Any help would be appreciated

tower-diagnostics-20210812-1009.zip

[(Solved)LSI 9211-8i IT Mode Firmware Flash Problems]

4 hours ago, Benson said:

Reboot won't bricked it.

 

I don't think NTFS is the problem, otherwise you can't execute sas2flash.

 

For my understanding, flash firmware won't help PAL error issue.

So even though I have erased the flash memory, everything says to not reboot, but for what ever reason I am unable to get it to execute the commands, but maddeningly it let me do the erasing one.

 

3 hours ago, Abnorm said:

A summary of what i did in terms of flashing the card, just check the last post, hopefully it helps :

 

Hi thanks for the link, just not sure it can help all that much as stated above when ever I do the "sas2flsh.efi -o -f 2118it.bin" it just gives me the syntax error and will not let me do anything. Still have the machine on in case there's anything that can be done.

[(Solved)LSI 9211-8i IT Mode Firmware Flash Problems]

uhg this is likely in the wrong section of the forums for this also >_<

[(Solved)LSI 9211-8i IT Mode Firmware Flash Problems]

Hello, I have spent all day following guides on how to flash a LSI 9211-8i into IT mode via USB as I had just bought the card. I am unable to do the flashing via BIOS due to the PAL errors which from everything I have read means the Mobo is UEFI (Gigabyte Z170N-WIFI). I had also tried every way online on how to try get my usb key set up to UEFI but for what ever reason the computer just would not enter the shell, I would get the option to load the USB in UEFI but it would just flash and go back the menu on boot devices (Rufus>FreeDOS>Fat32 etc etc and the usb drive is only 8GB) or if I selected the non UEFI it would just load into FreeDOS. (I had tried every different form of sas2flash.efi in the root directory of freedos usb or non bootable usb, had tried the /efi/root/ efi goes here and none would ever load up the UEFI options which were set as boot priority it just would not load just do that flicker thing).

For what ever brain aneurysm I had at the time in rufus I noticed a UEFI:NTFS option which for the hell of it I tried and put in the sas2flash.efi as well as the shellx64.efi in the efi/root folder and it actually booted up so I started following the UEFI guides commands

 

fs0:/> sas2flash.efi -listall
fs0:/> sas2flash.efi -o -e 6
fs0:/> sas2flash.efi -o -f 2118it.bin -b mptsas2.rom
fs0:/> sas2flash.efi -listall

2118it.bin & mptsas2.rom (latest versions) are in the root directory with the sas2flash.efi

 

basically I got to the -o -e 6 and it worked and I was ecstatic as it was finally working. I did the second line and I would get a 

ERROR: Could not open file: 2118it.bin, Syntax Error see Command Usage Below: 

-f x: Flash firmware image
x = the firmware file to flash

that for both files, it would not let me flash them.

 

So atm I still have the machine running as everything says to not turn it off. I have likely bricked it with how the usb drive is in ntfs and not fat32. The main question is, is there any way to try salvage it to somehow get the files to install or failing that if i have to reboot is there any way to unbrick the card. Any help would be appreciated.