Custom Query (1453 matches)
Results (109 - 111 of 1453)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#87 | duplicate | self test failed [Cannot allocate memory] | ||
Description |
Hello, I'm having trouble getting smartctl to run tests on our MegaRAID systems: [root@server ~]# smartctl -t long -d megaraid,0 /dev/sda smartctl 5.39.1 2010-01-28 r3054 [i686-pc-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net Long (extended) offline self test failed [Cannot allocate memory] I've tried recompiling 5.39.1, but not installing it, thinking it might not like being in HIGHMEM, however that did not help either. I'm at a loss as to what the problem could be, and as a last resort I've put in this ticket for assistance. [root@server ~]# cat /etc/redhat-release CentOS release 5.5 (Final) [root@server ~]# ulimit -a core file size (blocks, -c) 1000000 data seg size (kbytes, -d) unlimited scheduling priority (-e) 19 file size (blocks, -f) unlimited pending signals (-i) 192994 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 4096 pipe size (512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 14335 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited Any suggestions would be highly appreciated. |
|||
#287 | invalid | selective test percentage | ||
Description |
SMART Selective self-test log data structure revision number 1
Says 10% left when it's not even close (314572801-629145601 but it's still at 373710487). Is this some bug in smartd or just the HDD (Western Digital Green 2TB / 3TB, they all show the same behavior) reporting it wrong? Couldn't smartd calculate the correct percentage given it seems to know the current position? I'm trying to use select tests in smartd.conf as a full extended test just takes too long in one go. I wish I could specify the size directly there so I don't have to worry about it getting confused as to which size/address to use (which seems to happen a lot and doesn't raise an error - I'm already using savestates). Like when I do select tests outside of smartd for other reasons (when there was an I/O error at a specific address). It shouldn't use that as a reference for its own tests... |
|||
#1646 | duplicate | segmentation fault under linux ia64 | ||
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. |