Drive with prev errors passing all tests suddenly

found the p20 drivers here…

As I’m on MACbook created a FAT USB with master boot record and then used unetbootin to make it bootable for freedos from https://unetbootin.github.io
Also found : GitHub - lrq3000/lsi_sas_hba_crossflash_guide: A 2023 guide and toolset to crossflash LSI SAS HBA controllers, including DELL and Fujitsu and get idea it might be of valua for someone.
will swop cards tomorrow, disconnect all current drives and attempt the flash…
strange looking at the dates… don’t know why I ever flashed my card with such old FW. might unknowingly just used a bin i found and not knowing it was a old version.
want to get a 16 port card… future plans.

G

4 Likes

Then the recommendation would be a 9305-16(i/e) on P16.00.12.00.
For flashing, skip FreeDOS, just put the sas(2,3)flash**.efi** tool and firmware on a FAT32 stick and boot to UEFI shell.
map to list file systems.
fs0: to go to said filesystem.
dir to list content. If that’s not your USB stick, keep on with fs1: etc.
Once you’ve found it, flash according to instructions.

for some reason always battle with the UEFI method…

going to try the simpler boot to dos…

Will make record of the 9305 notes above for when i get a 16 port.
have to see if i can find a gap in todays work to get this done.
will advise.
G

please help…

i found that even sas2flsh -ver is throwing this error,

after i created the bootable freedos usb it gave me a error looking for dos4gw.exe i downloaded that and placed it in the same directory…

I seem to be running into the following…

trying to make a UEFI USB boot, not having luck…
know I did this previously… flash a card… usb stick that was used is gone :frowning:
eventually figured out it does not like any stick over 2GB… old dos limit. trying to maybe make msdos was able to boot still ran into errors. so tried freedom, less errors… but as per above…

G

got it flashed…

but FFS now it does not want to recognise my 128GB SSD/M.2 drive on which the TrueNas software is…

pretty sure I had it set as UEFI for storage, also tried legacy…
If I connect the disk pool drives then it quickly tells me those are Trueness data drives and not to be used…

Might have to flash TN Scale onto a USB and see if I can boot… ad then see what I’ve changed since my last TN backup…

G

… after a interesting day… new “B” card is in and flashed…

root@vaultx[~]# sas2flash -list
LSI Corporation SAS2 Flash Utility
Version 20.00.00.00 (2014.09.18)
Copyright (c) 2008-2014 LSI Corporation. All rights reserved

    Adapter Selected is a LSI SAS: SAS2008(B2)   

    Controller Number              : 0
    Controller                     : SAS2008(B2)   
    PCI Address                    : 00:01:00:00
    SAS Address                    : 500605b-0-04d5-b530
    NVDATA Version (Default)       : 14.01.00.08
    NVDATA Version (Persistent)    : 14.01.00.08
    Firmware Product ID            : 0x2213 (IT)
    Firmware Version               : 20.00.07.00
    NVDATA Vendor                  : LSI
    NVDATA Product ID              : SAS9211-8i
    BIOS Version                   : N/A
    UEFI BSD Version               : N/A
    FCODE Version                  : N/A
    Board Name                     : SAS9211-8i
    Board Assembly                 : N/A
    Board Tracer Number            : N/A

    Finished Processing Commands Successfully.
    Exiting SAS2Flash.

root@vaultx[~]#

Lets see if system stabilises… really hope so… it’s required far to much attention the last 3 months.

hopefully have some quiet time… slowing me to plan the next phase… MB upgrade and a 16i card and then some more 12TB NAS drives… case to be determined, like the 45Drives HL15.

G

2 Likes

… new card is in…
how can i clear some previous logged errors on a drive, thinking the 8 errors i’m seeing currently is from previous scan’s… want to clear SMART memory and do a long scan on the drive.

G

I don’t think you can clear SMART errors but you can clear ZFS errors.
zpool clear Clears device errors in a pool, according to man page

I"m sitting with one drive that reported errors… want to confirm it is the drive and was not the old FW…

The disk pool is not showing errors.

G

wondering… dont shoot me…
had a drive that was causing allot of problems previously… took allot apart, flashed the HBA now… I’ve completed a couple of bad blocks runs on it now… passing with 0 errors…

Sitting with this drive /dev/sdc thats throwing the same 8 errors…

Wondering… if i run another bad blocks on the previous bad boy… and if it passes if I can consider swopping them out…

the disk pool is RaidZ2 based.

G

Long as it is within your personal risk tolerance, you can do anything you want!

Would I personally do it? Not unless I had a known good spare on had to resilver the moment that drive left the case.

thats the thing… wondering if it was the drive that was the problem… considering all the long tests and bad block tests it has now passed with no errors…

G

… Not to worry…

Figured I’d do a Long Test on the drive again… the error counter decided to scroll up like a roulette machine… Def have no future in machine.
very strange though, one day 0 errors, next it’s like crazy.

G

For those curious about this HDD.

G

sdf.txt (26.1 KB)

Replacement drive ordered.
Decided after the number of Ironwolf drives that gave issues I’m going to try the Exo’s.

G