This is the old XigmaNAS forum in read only mode,
it will taken offline by the end of march 2021!


I like to aks Users and Admins to rewrite/take over important post from here into the new fresh main forum!
Its not possible for us to export from here and import it to the main forum!

Br10i in IT mode error

Hard disks, HDD, RAID Hardware, disk controllers, SATA, PATA, SCSI, IDE, On Board, USB, Firewire, CF (Compact Flash)
Forum rules
• Set-Up Guide • FAQs • Forum Rules
Post Reply
hellokevin11
Starter
Starter
Posts: 45
Joined: 04 Apr 2014 04:16
Status: Offline

Br10i in IT mode error

Post by hellokevin11 »

Image

Image

Card was flashed to IT mode.
Top
User avatar
b0ssman
Forum Moderator
Forum Moderator
Posts: 2438
Joined: 14 Feb 2013 08:34
Location: Munich, Germany
Status: Offline

Re: Br10i in IT mode error

Post by b0ssman »

does the firmware match the driver vesrion?

check the dmesg output
Nas4Free 11.1.0.4.4517. Supermicro X10SLL-F, 16gb ECC, i3 4130, IBM M1015 with IT firmware. 4x 3tb WD Red, 4x 2TB Samsung F4, both GEOM AES 256 encrypted.
Top
hellokevin11
Starter
Starter
Posts: 45
Joined: 04 Apr 2014 04:16
Status: Offline

Re: Br10i in IT mode error

Post by hellokevin11 »

I upgraded from 20 to 21 firmware IT mode.

MPI version = 1.5.20.0

SAS1068E is compatible with mpt(4)

Not sure how to proceed past this point, I did a lot of google searching.

Unsure if upgrading fixed it.
Top
User avatar
b0ssman
Forum Moderator
Forum Moderator
Posts: 2438
Joined: 14 Feb 2013 08:34
Location: Munich, Germany
Status: Offline

Re: Br10i in IT mode error

Post by b0ssman »

give us some more info on your hardware.

what version of nas4free are you running?

was is working before? what did you change

etc...
Nas4Free 11.1.0.4.4517. Supermicro X10SLL-F, 16gb ECC, i3 4130, IBM M1015 with IT firmware. 4x 3tb WD Red, 4x 2TB Samsung F4, both GEOM AES 256 encrypted.
Top
hellokevin11
Starter
Starter
Posts: 45
Joined: 04 Apr 2014 04:16
Status: Offline

Re: Br10i in IT mode error

Post by hellokevin11 »

Initial install.

Version 9.3.0.2 - Nayla (revision 1349)
Build date Tue Feb 10 03:12:22 CET 2015
Platform OS FreeBSD Revision: 199506
FreeBSD 9.3-RELEASE-p9 #0 r278463M: Mon Feb 9 18:31:18 CET 2015
Platform x64-embedded on AMD Sempron(tm) 145 Processor
System ASUSTeK Computer INC. M5A78L-M LX PLUS
Br10i flashed to LSi sas1068e Firemware 21 IT mode

errors still happening:

Mar 26 12:00:44 nas4free kernel: mpt0: completing timedout/aborted req 0xffffff80007574a0:3636
Mar 26 12:00:44 nas4free kernel: mpt0: abort of req 0xffffff80007574a0:0 completed
Mar 26 12:01:04 nas4free kernel: mpt0: request 0xffffff800074c2e0:3647 timed out for ccb 0xfffffe000ad48000 (req->ccb 0xfffffe000ad48000)
Mar 26 12:01:04 nas4free kernel: mpt0: attempting to abort req 0xffffff800074c2e0:3647 function 0
Mar 26 12:01:05 nas4free kernel: mpt0: completing timedout/aborted req 0xffffff800074c2e0:3647
Mar 26 12:01:05 nas4free kernel: mpt0: abort of req 0xffffff800074c2e0:0 completed
Mar 26 12:01:25 nas4free kernel: mpt0: request 0xffffff8000755520:3649 timed out for ccb 0xfffffe000ad48000 (req->ccb 0xfffffe000ad48000)
Mar 26 12:01:25 nas4free kernel: mpt0: attempting to abort req 0xffffff8000755520:3649 function 0
Mar 26 12:01:25 nas4free kernel: mpt0: completing timedout/aborted req 0xffffff8000755520:3649
Mar 26 12:01:25 nas4free kernel: mpt0: abort of req 0xffffff8000755520:0 completed
Mar 26 12:01:46 nas4free kernel: mpt0: request 0xffffff800074f100:3660 timed out for ccb 0xfffffe000ad48000 (req->ccb 0xfffffe000ad48000)
Mar 26 12:01:46 nas4free kernel: mpt0: attempting to abort req 0xffffff800074f100:3660 function 0
Mar 26 12:01:46 nas4free kernel: mpt0: completing timedout/aborted req 0xffffff800074f100:3660
Mar 26 12:01:46 nas4free kernel: mpt0: abort of req 0xffffff800074f100:0 completed
Mar 26 12:02:06 nas4free kernel: mpt0: request 0xffffff800074e1d0:3662 timed out for ccb 0xfffffe000ad48000 (req->ccb 0xfffffe000ad48000)
Mar 26 12:02:06 nas4free kernel: mpt0: attempting to abort req 0xffffff800074e1d0:3662 function 0
Mar 26 12:02:07 nas4free kernel: mpt0: completing timedout/aborted req 0xffffff800074e1d0:3662
Mar 26 12:02:07 nas4free kernel: mpt0: abort of req 0xffffff800074e1d0:0 completed
Mar 26 12:02:27 nas4free kernel: mpt0: request 0xffffff800074ed10:3673 timed out for ccb 0xfffffe000ad48000 (req->ccb 0xfffffe000ad48000)
Mar 26 12:02:27 nas4free kernel: mpt0: attempting to abort req 0xffffff800074ed10:3673 function 0
Mar 26 12:02:27 nas4free kernel: mpt0: completing timedout/aborted req 0xffffff800074ed10:3673
Mar 26 12:02:27 nas4free kernel: mpt0: abort of req 0xffffff800074ed10:0 completed
Mar 26 12:02:47 nas4free kernel: mpt0: request 0xffffff800074e770:3675 timed out for ccb 0xfffffe000ad48000 (req->ccb 0xfffffe000ad48000)
Mar 26 12:02:47 nas4free kernel: mpt0: attempting to abort req 0xffffff800074e770:3675 function 0
Mar 26 12:02:48 nas4free kernel: mpt0: completing timedout/aborted req 0xffffff800074e770:3675
Mar 26 12:02:48 nas4free kernel: mpt0: abort of req 0xffffff800074e770:0 completed
Mar 26 12:03:08 nas4free kernel: mpt0: request 0xffffff800074fc40:3686 timed out for ccb 0xfffffe000ad48000 (req->ccb 0xfffffe000ad48000)
Mar 26 12:03:08 nas4free kernel: mpt0: attempting to abort req 0xffffff800074fc40:3686 function 0
Mar 26 12:03:09 nas4free kernel: mpt0: completing timedout/aborted req 0xffffff800074fc40:3686
Mar 26 12:03:09 nas4free kernel: mpt0: abort of req 0xffffff800074fc40:0 completed
Mar 26 12:03:29 nas4free kernel: mpt0: request 0xffffff800074f6a0:3688 timed out for ccb 0xfffffe000ad48000 (req->ccb 0xfffffe000ad48000)
Mar 26 12:03:29 nas4free kernel: mpt0: attempting to abort req 0xffffff800074f6a0:3688 function 0
Mar 26 12:03:29 nas4free kernel: mpt0: completing timedout/aborted req 0xffffff800074f6a0:3688
Mar 26 12:03:29 nas4free kernel: mpt0: abort of req 0xffffff800074f6a0:0 completed
Mar 26 12:03:50 nas4free kernel: mpt0: request 0xffffff800074f340:3699 timed out for ccb 0xfffffe000ad48000 (req->ccb 0xfffffe000ad48000)
Mar 26 12:03:50 nas4free kernel: mpt0: attempting to abort req 0xffffff800074f340:3699 function 0
Mar 26 12:03:51 nas4free kernel: mpt0: completing timedout/aborted req 0xffffff800074f340:3699
Mar 26 12:03:51 nas4free kernel: mpt0: abort of req 0xffffff800074f340:0 completed
Mar 26 12:04:11 nas4free kernel: mpt0: request 0xffffff800074e9b0:3701 timed out for ccb 0xfffffe000ad48000 (req->ccb 0xfffffe000ad48000)
Mar 26 12:04:11 nas4free kernel: mpt0: attempting to abort req 0xffffff800074e9b0:3701 function 0
Mar 26 12:04:11 nas4free kernel: mpt0: completing timedout/aborted req 0xffffff800074e9b0:3701
Mar 26 12:04:11 nas4free kernel: mpt0: abort of req 0xffffff800074e9b0:0 completed
Mar 26 12:04:31 nas4free kernel: mpt0: request 0xffffff80007562a0:3712 timed out for ccb 0xfffffe000ad48000 (req->ccb 0xfffffe000ad48000)
Mar 26 12:04:31 nas4free kernel: mpt0: attempting to abort req 0xffffff80007562a0:3712 function 0
Mar 26 12:04:32 nas4free kernel: mpt0: completing timedout/aborted req 0xffffff80007562a0:3712
Mar 26 12:04:32 nas4free kernel: mpt0: abort of req 0xffffff80007562a0:0 completed
Mar 26 12:04:52 nas4free kernel: mpt0: request 0xffffff800074f4f0:3714 timed out for ccb 0xfffffe000ad48000 (req->ccb 0xfffffe000ad48000)
Mar 26 12:04:52 nas4free kernel: mpt0: attempting to abort req 0xffffff800074f4f0:3714 function 0
Mar 26 12:04:52 nas4free kernel: mpt0: completing timedout/aborted req 0xffffff800074f4f0:3714
Mar 26 12:04:52 nas4free kernel: mpt0: abort of req 0xffffff800074f4f0:0 completed
Mar 26 12:05:12 nas4free kernel: mpt0: request 0xffffff80007571d0:3725 timed out for ccb 0xfffffe000ad48000 (req->ccb 0xfffffe000ad48000)
Mar 26 12:05:12 nas4free kernel: mpt0: attempting to abort req 0xffffff80007571d0:3725 function 0
Mar 26 12:05:13 nas4free kernel: mpt0: completing timedout/aborted req 0xffffff80007571d0:3725
Mar 26 12:05:13 nas4free kernel: mpt0: abort of req 0xffffff80007571d0:0 completed
Mar 26 12:05:33 nas4free kernel: mpt0: request 0xffffff800074c640:3727 timed out for ccb 0xfffffe000ad48000 (req->ccb 0xfffffe000ad48000)
Mar 26 12:05:33 nas4free kernel: mpt0: attempting to abort req 0xffffff800074c640:3727 function 0
Mar 26 12:05:33 nas4free kernel: mpt0: completing timedout/aborted req 0xffffff800074c640:3727
Mar 26 12:05:33 nas4free kernel: mpt0: abort of req 0xffffff800074c640:0 completed
Mar 26 12:05:40 nas4free kernel: (da7:mpt0:0:8:0): READ(6). CDB: 08 00 00 08 01 00
Mar 26 12:05:40 nas4free kernel: (da7:mpt0:0:8:0): CAM status: SCSI Status Error
Mar 26 12:05:40 nas4free kernel: (da7:mpt0:0:8:0): SCSI status: Check Condition
Mar 26 12:05:40 nas4free kernel: (da7:mpt0:0:8:0): SCSI sense: UNIT ATTENTION asc:29,0 (Power on, reset, or bus device reset occurred)
Mar 26 12:05:40 nas4free kernel: (da7:mpt0:0:8:0): Retrying command (per sense data)
Mar 26 12:05:40 nas4free kernel: (da6:mpt0:0:7:0): READ(6). CDB: 08 00 00 08 01 00
Mar 26 12:05:40 nas4free kernel: (da6:mpt0:0:7:0): CAM status: SCSI Status Error
Mar 26 12:05:40 nas4free kernel: (da6:mpt0:0:7:0): SCSI status: Check Condition
Mar 26 12:05:40 nas4free kernel: (da6:mpt0:0:7:0): SCSI sense: UNIT ATTENTION asc:29,0 (Power on, reset, or bus device reset occurred)
Mar 26 12:05:40 nas4free kernel: (da6:mpt0:0:7:0): Retrying command (per sense data)
Mar 26 12:05:40 nas4free kernel: (da5:mpt0:0:6:0): READ(6). CDB: 08 00 00 08 01 00
Mar 26 12:05:40 nas4free kernel: (da5:mpt0:0:6:0): CAM status: SCSI Status Error
Mar 26 12:05:40 nas4free kernel: (da5:mpt0:0:6:0): SCSI status: Check Condition
Mar 26 12:05:40 nas4free kernel: (da5:mpt0:0:6:0): SCSI sense: UNIT ATTENTION asc:29,0 (Power on, reset, or bus device reset occurred)
Mar 26 12:05:40 nas4free kernel: (da5:mpt0:0:6:0): Retrying command (per sense data)
Mar 26 12:05:40 nas4free kernel: (da4:mpt0:0:5:0): READ(6). CDB: 08 00 00 08 01 00
Mar 26 12:05:40 nas4free kernel: (da4:mpt0:0:5:0): CAM status: SCSI Status Error
Mar 26 12:05:40 nas4free kernel: (da4:mpt0:0:5:0): SCSI status: Check Condition
Mar 26 12:05:40 nas4free kernel: (da4:mpt0:0:5:0): SCSI sense: UNIT ATTENTION asc:29,0 (Power on, reset, or bus device reset occurred)
Mar 26 12:05:40 nas4free kernel: (da4:mpt0:0:5:0): Retrying command (per sense data)
Mar 26 12:05:41 nas4free kernel: (da3:mpt0:0:4:0): READ(6). CDB: 08 00 00 08 01 00
Mar 26 12:05:41 nas4free kernel: (da3:mpt0:0:4:0): CAM status: SCSI Status Error
Mar 26 12:05:41 nas4free kernel: (da3:mpt0:0:4:0): SCSI status: Check Condition
Mar 26 12:05:41 nas4free kernel: (da3:mpt0:0:4:0): SCSI sense: UNIT ATTENTION asc:29,0 (Power on, reset, or bus device reset occurred)
Mar 26 12:05:41 nas4free kernel: (da3:mpt0:0:4:0): Retrying command (per sense data)
Mar 26 12:05:41 nas4free kernel: (da2:mpt0:0:3:0): READ(6). CDB: 08 00 00 08 01 00
Mar 26 12:05:41 nas4free kernel: (da2:mpt0:0:3:0): CAM status: SCSI Status Error
Mar 26 12:05:41 nas4free kernel: (da2:mpt0:0:3:0): SCSI status: Check Condition
Mar 26 12:05:41 nas4free kernel: (da2:mpt0:0:3:0): SCSI sense: UNIT ATTENTION asc:29,0 (Power on, reset, or bus device reset occurred)
Mar 26 12:05:41 nas4free kernel: (da2:mpt0:0:3:0): Retrying command (per sense data)
Mar 26 12:05:42 nas4free kernel: (da1:mpt0:0:2:0): READ(6). CDB: 08 00 00 08 01 00
Mar 26 12:05:42 nas4free kernel: (da1:mpt0:0:2:0): CAM status: SCSI Status Error
Mar 26 12:05:42 nas4free kernel: (da1:mpt0:0:2:0): SCSI status: Check Condition
Mar 26 12:05:42 nas4free kernel: (da1:mpt0:0:2:0): SCSI sense: UNIT ATTENTION asc:29,0 (Power on, reset, or bus device reset occurred)
Mar 26 12:05:42 nas4free kernel: (da1:mpt0:0:2:0): Retrying command (per sense data)
Mar 26 12:05:42 nas4free kernel: (da0:mpt0:0:1:0): READ(6). CDB: 08 00 00 08 01 00
Mar 26 12:05:42 nas4free kernel: (da0:mpt0:0:1:0): CAM status: SCSI Status Error
Mar 26 12:05:42 nas4free kernel: (da0:mpt0:0:1:0): SCSI status: Check Condition
Mar 26 12:05:42 nas4free kernel: (da0:mpt0:0:1:0): SCSI sense: UNIT ATTENTION asc:29,0 (Power on, reset, or bus device reset occurred)
Mar 26 12:05:42 nas4free kernel: (da0:mpt0:0:1:0): Retrying command (per sense data)
Top
User avatar
b0ssman
Forum Moderator
Forum Moderator
Posts: 2438
Joined: 14 Feb 2013 08:34
Location: Munich, Germany
Status: Offline

Re: Br10i in IT mode error

Post by b0ssman »

please post the entire dmesg output.

preferably to pastbin or formatted as code
Nas4Free 11.1.0.4.4517. Supermicro X10SLL-F, 16gb ECC, i3 4130, IBM M1015 with IT firmware. 4x 3tb WD Red, 4x 2TB Samsung F4, both GEOM AES 256 encrypted.
Top
hellokevin11
Starter
Starter
Posts: 45
Joined: 04 Apr 2014 04:16
Status: Offline

Re: Br10i in IT mode error

Post by hellokevin11 »

I received degraded message for SAS3801E-R Z3 with permanent damage.

SAS3801E-R is not supported controller, and cannot find P16 IT mod firmware.

Will order newer controller that is supported by bsd.
Top
Post Reply

Return to “Hard disk & controller”