Full log with multiple issues


Recommended Posts

Hi all,

 

I've had multiple issues recently that I would like to document.

 

1. I recently installed a new SSD as a new cache group - In the disc's logs I am constantly getting these errors, and I am not sure if this is fine or not. I don't know if this is related but last night, I copied a few files from one share to another and this morning that data was gone and I had to copy it again.

 

Log for the SSD:

Jan 11 13:34:40 mesawest kernel: sd 7:0:3:0: [sdj] Spinning up disk...
Jan 11 13:34:40 mesawest kernel: sd 7:0:3:0: [sdj] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
Jan 11 13:34:40 mesawest kernel: sd 7:0:3:0: [sdj] Write Protect is off
Jan 11 13:34:40 mesawest kernel: sd 7:0:3:0: [sdj] Mode Sense: 7f 00 10 08
Jan 11 13:34:40 mesawest kernel: sd 7:0:3:0: [sdj] Write cache: enabled, read cache: enabled, supports DPO and FUA
Jan 11 13:34:40 mesawest kernel: sdj: sdj1
Jan 11 13:34:40 mesawest kernel: sd 7:0:3:0: [sdj] Attached SCSI disk
Jan 11 13:35:07 mesawest emhttpd: WD_Blue_SA510_2.5_1000GB_22433T800639 (sdj) 512 1953525168
Jan 11 13:35:07 mesawest emhttpd: import 31 cache device: (sdj) WD_Blue_SA510_2.5_1000GB_22433T800639
Jan 11 13:35:07 mesawest emhttpd: read SMART /dev/sdj
Jan 11 13:35:14 mesawest emhttpd: shcmd (56): mount -t xfs -o noatime,nouuid /dev/sdj1 /mnt/cache_files
Jan 11 13:35:14 mesawest kernel: XFS (sdj1): Mounting V5 Filesystem
Jan 11 13:35:14 mesawest kernel: XFS (sdj1): Ending clean mount
Jan 12 00:10:07 mesawest kernel: sd 7:0:3:0: [sdj] tag#1698 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s
Jan 12 00:10:07 mesawest kernel: sd 7:0:3:0: [sdj] tag#1698 Sense Key : 0x5 [current] 
Jan 12 00:10:07 mesawest kernel: sd 7:0:3:0: [sdj] tag#1698 ASC=0x21 ASCQ=0x0 
Jan 12 00:10:07 mesawest kernel: sd 7:0:3:0: [sdj] tag#1698 CDB: opcode=0x42 42 00 00 00 00 00 00 00 18 00
Jan 12 00:10:07 mesawest kernel: blk_update_request: critical target error, dev sdj, sector 1951691109 op 0x3:(DISCARD) flags 0x0 phys_seg 1 prio class 0
Jan 13 00:10:07 mesawest kernel: sd 7:0:3:0: [sdj] tag#1698 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s
Jan 13 00:10:07 mesawest kernel: sd 7:0:3:0: [sdj] tag#1698 Sense Key : 0x5 [current] 
Jan 13 00:10:07 mesawest kernel: sd 7:0:3:0: [sdj] tag#1698 ASC=0x21 ASCQ=0x0 
Jan 13 00:10:07 mesawest kernel: sd 7:0:3:0: [sdj] tag#1698 CDB: opcode=0x42 42 00 00 00 00 00 00 00 18 00
Jan 13 00:10:07 mesawest kernel: blk_update_request: critical target error, dev sdj, sector 1951691109 op 0x3:(DISCARD) flags 0x0 phys_seg 1 prio class 0
Jan 14 00:10:07 mesawest kernel: sd 7:0:3:0: [sdj] tag#1701 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s
Jan 14 00:10:07 mesawest kernel: sd 7:0:3:0: [sdj] tag#1701 Sense Key : 0x5 [current] 
Jan 14 00:10:07 mesawest kernel: sd 7:0:3:0: [sdj] tag#1701 ASC=0x21 ASCQ=0x0 
Jan 14 00:10:07 mesawest kernel: sd 7:0:3:0: [sdj] tag#1701 CDB: opcode=0x42 42 00 00 00 00 00 00 00 18 00
Jan 14 00:10:07 mesawest kernel: blk_update_request: critical target error, dev sdj, sector 1951691109 op 0x3:(DISCARD) flags 0x0 phys_seg 1 prio class 0
Jan 15 00:10:07 mesawest kernel: sd 7:0:3:0: [sdj] tag#1738 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s
Jan 15 00:10:07 mesawest kernel: sd 7:0:3:0: [sdj] tag#1738 Sense Key : 0x5 [current] 
Jan 15 00:10:07 mesawest kernel: sd 7:0:3:0: [sdj] tag#1738 ASC=0x21 ASCQ=0x0 
Jan 15 00:10:07 mesawest kernel: sd 7:0:3:0: [sdj] tag#1738 CDB: opcode=0x42 42 00 00 00 00 00 00 00 18 00
Jan 15 00:10:07 mesawest kernel: blk_update_request: critical target error, dev sdj, sector 1951691109 op 0x3:(DISCARD) flags 0x0 phys_seg 1 prio class 0
Jan 16 00:10:07 mesawest kernel: sd 7:0:3:0: [sdj] tag#1827 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s
Jan 16 00:10:07 mesawest kernel: sd 7:0:3:0: [sdj] tag#1827 Sense Key : 0x5 [current] 
Jan 16 00:10:07 mesawest kernel: sd 7:0:3:0: [sdj] tag#1827 ASC=0x21 ASCQ=0x0 
Jan 16 00:10:07 mesawest kernel: sd 7:0:3:0: [sdj] tag#1827 CDB: opcode=0x42 42 00 00 00 00 00 00 00 18 00
Jan 16 00:10:07 mesawest kernel: blk_update_request: critical target error, dev sdj, sector 1952922358 op 0x3:(DISCARD) flags 0x800 phys_seg 1 prio class 0
Jan 17 00:10:06 mesawest kernel: sd 7:0:3:0: [sdj] tag#1896 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s
Jan 17 00:10:06 mesawest kernel: sd 7:0:3:0: [sdj] tag#1896 Sense Key : 0x5 [current] 
Jan 17 00:10:06 mesawest kernel: sd 7:0:3:0: [sdj] tag#1896 ASC=0x21 ASCQ=0x0 
Jan 17 00:10:06 mesawest kernel: sd 7:0:3:0: [sdj] tag#1896 CDB: opcode=0x42 42 00 00 00 00 00 00 00 18 00
Jan 17 00:10:06 mesawest kernel: blk_update_request: critical target error, dev sdj, sector 1950676478 op 0x3:(DISCARD) flags 0x0 phys_seg 1 prio class 0
Jan 18 00:10:06 mesawest kernel: sd 7:0:3:0: [sdj] tag#1859 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s
Jan 18 00:10:06 mesawest kernel: sd 7:0:3:0: [sdj] tag#1859 Sense Key : 0x5 [current] 
Jan 18 00:10:06 mesawest kernel: sd 7:0:3:0: [sdj] tag#1859 ASC=0x21 ASCQ=0x0 
Jan 18 00:10:06 mesawest kernel: sd 7:0:3:0: [sdj] tag#1859 CDB: opcode=0x42 42 00 00 00 00 00 00 00 18 00
Jan 18 00:10:06 mesawest kernel: blk_update_request: critical target error, dev sdj, sector 1950129000 op 0x3:(DISCARD) flags 0x800 phys_seg 1 prio class 0
Jan 19 00:10:05 mesawest kernel: sd 7:0:3:0: [sdj] tag#1856 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s
Jan 19 00:10:05 mesawest kernel: sd 7:0:3:0: [sdj] tag#1856 Sense Key : 0x5 [current] 
Jan 19 00:10:05 mesawest kernel: sd 7:0:3:0: [sdj] tag#1856 ASC=0x21 ASCQ=0x0 
Jan 19 00:10:05 mesawest kernel: sd 7:0:3:0: [sdj] tag#1856 CDB: opcode=0x42 42 00 00 00 00 00 00 00 18 00
Jan 19 00:10:05 mesawest kernel: blk_update_request: critical target error, dev sdj, sector 1950129000 op 0x3:(DISCARD) flags 0x800 phys_seg 1 prio class 0
Jan 20 00:10:13 mesawest kernel: sd 7:0:3:0: [sdj] tag#1957 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s
Jan 20 00:10:13 mesawest kernel: sd 7:0:3:0: [sdj] tag#1957 Sense Key : 0x5 [current] 
Jan 20 00:10:13 mesawest kernel: sd 7:0:3:0: [sdj] tag#1957 ASC=0x21 ASCQ=0x0 
Jan 20 00:10:13 mesawest kernel: sd 7:0:3:0: [sdj] tag#1957 CDB: opcode=0x42 42 00 00 00 00 00 00 00 18 00
Jan 20 00:10:13 mesawest kernel: blk_update_request: critical target error, dev sdj, sector 1951683685 op 0x3:(DISCARD) flags 0x0 phys_seg 1 prio class 0

 

 

2. I am constantly getting these errors, I assume from my UPS. Not sure what the correct fix for this is but I really want one because this keeps clogging up my logs.

 

mesawest usbhid-ups[5948]: nut_libusb_get_string: Pipe error.

 

3. I was looking to spin down my drives so as to save on energy - and this appears to be working! However, I am now getting a bunch of errors in my logs that relate to my drives and smart - can anyone shed some light as to what is going on?

 

Thank you very much for reading and your help.

mesawest-diagnostics-20230120-0930.zip

Link to comment

Hey JorgeB, thanks for the quick reply - 

 

I tried to update my firmware and at the part where you check what is the firmware currently installed (I used `./sas2flash -listall` since my card is different), I am getting the following:

 

root@mesawest:/lsi# ./sas2flash -listall
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)

Num   Ctlr            FW Ver        NVDATA        x86-BIOS         PCI Addr
----------------------------------------------------------------------------

0  SAS2008(B2)     20.00.02.00    14.01.00.08    07.39.00.00     00:04:00:00

        Finished Processing Commands Successfully.
        Exiting SAS2Flash.

 

So it seems to be that I have a newer firmware?

 

The LSI chip that I bought was listed on ebay as: 

LSI SAS 9211-8i 8-port 6Gb/s PCI-E Internal HBA Both Brackets - Bundle Options [Card Only,IT Mode (ZFS JBOD HBA)]

 

So on the driver website I found the following links:

9211-8i_Package_P20_IR_IT_Firmware_BIOS_for_MSDOS_Windows
Package_P20_Firmware_BIOS_for_MSDOS_Windows
Version:
20.00.07.00

 

and 

Installer_P20_for_Linux
Linux Installer
Version:
20.00.00.00

 

is there something that I am doing wrong here?

Haven't replugged the SSD into the motherboard, but will be doing that soon.

Link to comment
  • 1 month later...

Hey @JorgeB, apologies for the late reply, haven't had time to investigate this further.

 

Based on the guide linked, I will need both a Windows installer and a Linux installer. I believe that the Windows installer is indeed `20.00.07.00`, however, the Linux one seems to not have a version above 20.00.00.00.

 

Am I correct in this?

Link to comment

In your guide, I am getting "stuck" on using the sas2flash utility to verify my firmware files.
 

Quote

 

Before flashing we can confirm the adapter (or adapters) are being detected and check what is the firmware currently installed:

./sas3flash -listall


 



When I do this, the get this:


 

root@mesawest:/lsi# ./sas2flash -listall
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)

Num   Ctlr            FW Ver        NVDATA        x86-BIOS         PCI Addr
----------------------------------------------------------------------------

0  SAS2008(B2)     20.00.02.00    14.01.00.08    07.39.00.00     00:04:00:00

        Finished Processing Commands Successfully.
        Exiting SAS2Flash.

 

So I am using the sas2flash that I found inside the linux files (as specified) under:

Installer_P20_for_Linux\sas2flash_linux_i686_x86-64_rel\sas2flash

 

So am I right in thinking that the version of the Utility is 20.00.00.00 and my current board firmware is 20.00.02.00? So Im good to upgrade then?

 

 

Link to comment

Thank you!! I will write back in a day or so to ensure my logs are not getting filled up anymore.

 

root@mesawest:/lsi# ./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:04:00:00
        SAS Address                    : 500605b-0-0650-1ae0
        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                   : 07.39.02.00
        UEFI BSD Version               : N/A
        FCODE Version                  : N/A
        Board Name                     : SAS9211-8i
        Board Assembly                 : H3-25250-02F
        Board Tracer Number            : SP33006164

        Finished Processing Commands Successfully.
        Exiting SAS2Flash.

 

  • Like 1
Link to comment
  • 4 weeks later...

Hi, so its been a few weeks. I am still getting a lot of spam in my logs, unsure what is causing it.

 

I have also noticed that I was running a deprecated version of the NUT UPS plugin, so I updated that and also changed the USB cable that was being used for the UPS to the PC. I am still getting `nut_libusb_get_string: Pipe error.` errors. 

I am also getting a lot of messages that say "Port # entered disabled state". Hopefully you can shed some light on this.

 

mesawest-diagnostics-20230330-1404.zip

Link to comment
17 minutes ago, maxistviews said:

I am also getting a lot of messages that say "Port # entered disabled state". Hopefully you can shed some light on this.

 

Look for a docker container that's continually restarting.  Uptime should tell you.

 

18 minutes ago, maxistviews said:

I am still getting `nut_libusb_get_string: Pipe error.` errors

Best to switch to the replacement and if it still happens, then post in the relevant support thread

  • Like 1
Link to comment
7 minutes ago, Squid said:

Best to switch to the replacement and if it still happens, then post in the relevant support thread

 

I have switched to a new cable since March 6th, but I will post about it on the relevant thread.

 

I'll have to check again later since I just updated all my dockers. 

If a docker has the `--restart unless-stopped` parameters, that would still show up in the Uptime, right?

Should I also try to update to 11.5 at this point? I am currently on 10.3. I was waiting for things to settle before updating.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.