Custom Query (1249 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (13 - 15 of 1249)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Ticket Resolution Summary Owner Reporter
#1646 duplicate segmentation fault under linux ia64 Anatoly Pugachev
Description

Hello!

Using debian sid (unstable) on my ia64 blade with hpsa (cciss) driver.

Running 'smartctl' for disk status, fails with segmentation fault:

# uname -a
Linux lifshitz 5.17.0-1-mckinley #1 SMP Debian 5.17.3-1 (2022-04-18) ia64 GNU/Linux
# ./smartctl -i /dev/sda -d cciss,0
smartctl 7.3 2022-02-28 r5338 [ia64-linux-5.17.0-1-mckinley] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

Segmentation fault (core dumped)

running under gdb (for stack trace):

smartmontools-7.3# gdb -q -c core ./smartctl
Reading symbols from ./smartctl...
[New LWP 1588376]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/ia64-linux-gnu/libthread_db.so.1".
Failed to read a valid object file image from memory.
Core was generated by `./smartctl -i /dev/sda -d cciss,0'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  tunnelled_device<ata_device, scsi_device>::get_tunnel_dev (this=0xc00000000004d2b8) at scsiata.cpp:499
499       if (!scsidev->scsi_pass_through(iop)) {
(gdb) bt
#0  tunnelled_device<ata_device, scsi_device>::get_tunnel_dev (this=0xc00000000004d2b8) at scsiata.cpp:499
#1  sat::sat_device::scsi_pass_through (this=0xc00000000004d2b8, iop=0x60000fffffe1edd0) at scsiata.cpp:498
#2  0x4000000000092000 in virtual thunk to sat::sat_device::scsi_pass_through(scsi_cmnd_io*) () at scsiata.cpp:1315
#3  0x4000000000083290 in scsi_pass_through_yield_sense (device=0x600000000003b1f8, iop=0x60000fffffe1edd0, sinfo=...) at scsicmds.cpp:1221
#4  0x4000000000084b90 in scsiInquiryVpd (device=0x600000000003b1f8, vpd_page=0, pBuf=0x60000fffffe1ee50 "", bufLen=252) at scsicmds.cpp:911
#5  0x4000000000084f40 in supported_vpd_pages::supported_vpd_pages (this=0x600000000003b270, device=0x600000000003b1f8) at scsicmds.cpp:54
#6  0x40000000000bd010 in scsiPrintMain (device=0x600000000003b1f8, options=...) at scsiprint.cpp:3214
#7  0x4000000000011740 in main_worker (argc=5, argv=0x60000fffffe23698) at smartctl.cpp:1655
#8  0x4000000000005d70 in main (argc=5, argv=0x60000fffffe23698) at smartctl.cpp:1676

any ideas how to fix this? Thanks.

#1644 invalid SMART Status not supported: Incomplete response, ATA output registers missing (CCISS) fereshtehloghmani
Description

hello I user server HP (DL360 G8) and raid controller p420i. I install smart on this server and I have some SATA and SSD hards that all of them are in a raid. when i use these command like: smartctl -a -d cciss,0 /dev/sg1 smartctl -a -d cciss,0 /dev/sda

i receive this error: SMART Status not supported: Incomplete response, ATA output registers missing

could you please help me with how can I monitor all kinds of hard in G8 and G7 HP servers? and is this problem related to the type of raid controller or type of server or something like this?

thanks in advance

#1642 fixed Swapped Bad_Blk_Ct_Erl/Lat values in drivedb for "Phison Driven SSDs" matjon
Description

Hello,

The drivedb currently contains the following entry:

  { "Phison Driven SSDs", // see MKP_521_Phison_SMART_attribute.pdf
[...]
    "-v 170,raw24/raw24:z54z10,Bad_Blk_Ct_Erl/Lat " // Early bad block/Later bad block

I think that the early and late bad block count values are swapped (late in place of early, early in place of late) and the description should be changed to "Bad_Blk_Ct_Lat/Erl".

According to the documentation in the PDF: https://media.kingston.com/support/downloads/MKP_521_Phison_SMART_attribute.pdf

“Bad Block Count (Early / Later)”
Counts the number of Bad blocks.

Raw Value Byte [1~0]: Early bad block count
Raw Value Byte [5~4]: Later bad block count

I have a drive that identifies itself as SSDPR-CX400-512-G2. It is not yet in the database (I will submit it shortly), but the SMART parameters are very likely the same as in SSDPR-CX400-512 (based on comparing with a vendor's tool). Since birth, it had "146" as the raw uninterpreted value of this attribute:

170 Unknown_Attribute       PO----   100   100   000    -    146

but when I modify the drivedb and add it to a regex for "Phison Driven SSDs", it is displayed as:

170 Bad_Blk_Ct_Erl/Lat      PO----   100   100   000    -    0/146

I think that the best way to fix this problem is to change the description to "Bad_Blk_Ct_Lat/Erl" to avoid confusion for people that have historical smartctl outputs stored somewhere.

Greetings,

Mateusz

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Note: See TracQuery for help on using queries.