February 12, 201412 yr What does the following mean? My array was running, and a preclear was also running on screen (the utility). Around halfway along preclear, the following came to my PuTTY window. I can log into the array as root via PuTTY and can mount drives, but I'm afraid of doing or touching anything now. Full syslog attached. Yes, it is the full syslog copied with cp /var/log/syslog /boot root@TheMonolith:~# screen 130503+0 records in 130503+0 records out 273684627456 bytes (274 GB) copied, 2589.56 s, 106 MB/s Wrote 273,684,627,456 bytes out of 2,000,398,934,016 bytes (13% Done) Message from syslogd@TheMonolith at Wed Feb 12 11:56:23 2014 ... TheMonolith kernel: Process scsi_eh_8 (pid: 1024, ti=f75c8000 task=f12710e0 task.ti=f75c8000) Message from syslogd@TheMonolith at Wed Feb 12 11:56:23 2014 ... TheMonolith kernel: Call Trace: Message from syslogd@TheMonolith at Wed Feb 12 11:56:23 2014 ... TheMonolith kernel: Code: 41 10 b9 00 00 02 00 89 04 24 89 d8 ff 96 c0 00 00 00 31 c0 83 c4 34 5b 5e 5f 5d c3 55 89 e5 57 89 c7 56 89 d6 53 89 cb 83 ec 14 <83> 79 08 00 0f 84 18 01 00 00 f6 42 14 05 75 48 8b 49 0c 85 c9 Message from syslogd@TheMonolith at Wed Feb 12 11:56:23 2014 ... TheMonolith kernel: Stack: Message from syslogd@TheMonolith at Wed Feb 12 11:56:23 2014 ... TheMonolith kernel: EIP: [<f84c23b0>] mvs_slot_task_free+0xf/0x139 [mvsas] SS:ESP 0068:f75c9e38 syslog.txt
February 12, 201412 yr Also enter "cp /var/log/syslog.* /boot" and attach any additional logs. zip if needed.
February 13, 201412 yr Author The array works fine. I suspect the preclear went awry, perhaps a busted disk - it's quite an old one. Also enter "cp /var/log/syslog.* /boot" and attach any additional logs. zip if needed. That's all there is: cp: cannot stat `/var/log/syslog.*': No such file or directory. We went through this a few weeks ago in another thread. My syslogs are always the short ones attached to the OP, and I (nor anyone else) don't know how to fix that.
February 13, 201412 yr Author check memory (free) and disk space (df -h)? Memory after reboot: total used free shared buffers cached Mem: 8308892 1068172 7240720 0 411868 224068 -/+ buffers/cache: 432236 7876656 Swap: 0 0 0 Disk space Filesystem Size Used Avail Use% Mounted on tmpfs 128M 2.4M 126M 2% /var/log /dev/sdc1 7.5G 156M 7.3G 3% /boot /dev/md1 1.9T 1.7T 203G 90% /mnt/disk1 /dev/md2 1.9T 1.8T 104G 95% /mnt/disk2 /dev/md3 1.9T 1.7T 143G 93% /mnt/disk3 /dev/md4 1.9T 1.3T 550G 71% /mnt/disk4 /dev/md5 1.9T 1.8T 83G 96% /mnt/disk5 /dev/md6 1.9T 1.6T 250G 87% /mnt/disk6 /dev/md7 1.9T 1.3T 554G 71% /mnt/disk7 /dev/md8 1.9T 1.2T 726G 62% /mnt/disk8 shfs 15T 13T 2.6T 83% /mnt/user
February 13, 201412 yr Author What does "ls /var/log" show? Here: cron packages/ removed_packages/ sa/ scripts/ syslog dmesg plugins/ removed_scripts/ samba/ setup/ syslog.1 syslog.1 (attached) wasn't there when I wrote my previous response to you. It contains entries from boot last night until now, and doesn't cover the time of the suspicious preclear stop. After that event there was only the terse syslog attached to the OP. syslog.1.zip
February 13, 201412 yr Run memtest overnight. Check for BIOS and firmware updates for the MB and SATA card.
February 14, 201412 yr Run memtest overnight. Check for BIOS and firmware updates for the MB and SATA card. agree... If it was my machine, I'd suspect a RAM problem.
Archived
This topic is now archived and is closed to further replies.