noja Posted January 13, 2020 Share Posted January 13, 2020 (edited) Hi - I'm on 6.8.0 and my I had an unresponsive GUI and noticed before a reboot that the log was at 100%. Now after reboot, I only have ssh access and ls -all /var/log shows total 114408 drwxr-xr-x 9 root root 640 Jan 12 04:40 ./ drwxr-xr-x 13 root root 300 Jan 9 2017 ../ -rw-r--r-- 1 root root 191 Jan 12 19:08 apcupsd.events -rw-r--r-- 1 root root 299 Jan 12 04:40 apcupsd.events.1 -rw-r--r-- 1 root root 299 Jan 5 04:40 apcupsd.events.2 -rw-r--r-- 1 root root 193 Dec 29 04:40 apcupsd.events.3 -rw------- 1 root root 0 Dec 10 12:25 btmp -rw-r--r-- 1 root root 0 Aug 20 13:44 cron -rw-r--r-- 1 root root 0 Aug 20 13:44 debug -rw-rw-rw- 1 root root 83046 Dec 24 21:41 dmesg -rw-rw-rw- 1 root root 2730 Jan 10 06:02 docker.log -rw-r--r-- 1 root root 0 Oct 18 15:59 faillog -rw-r--r-- 1 root root 0 Jan 13 00:57 lastlog drwxr-xr-x 3 root root 140 Dec 24 21:47 libvirt/ -rw-r--r-- 1 root root 9837 Jan 10 06:03 maillog -rw-r--r-- 1 root root 0 Aug 20 13:44 messages drwxr-xr-x 2 root root 40 May 15 2001 nfsd/ drwxr-x--- 2 nobody root 60 Dec 24 21:42 nginx/ lrwxrwxrwx 1 root root 24 Dec 10 12:24 packages -> ../lib/pkgtools/packages/ drwxr-xr-x 4 root root 80 Nov 24 16:12 pkgtools/ drwxr-xr-x 2 root root 600 Jan 8 00:00 plugins/ lrwxrwxrwx 1 root root 25 Dec 10 12:26 removed_packages -> pkgtools/removed_packages/ lrwxrwxrwx 1 root root 24 Dec 10 12:26 removed_scripts -> pkgtools/removed_scripts/ drwxr-xr-x 3 root root 240 Jan 12 12:12 samba/ lrwxrwxrwx 1 root root 23 Dec 10 12:24 scripts -> ../lib/pkgtools/scripts/ -rw-r--r-- 1 root root 0 Aug 20 13:44 secure lrwxrwxrwx 1 root root 21 Dec 10 12:24 setup -> ../lib/pkgtools/setup/ -rw-r--r-- 1 root root 0 Aug 20 13:44 spooler drwxr-xr-x 3 root root 60 Nov 16 16:07 swtpm/ -rw-r--r-- 1 root root 30896128 Jan 13 01:12 syslog -rw-r--r-- 1 root root 86130570 Jan 12 04:40 syslog.1 -rw-rw-r-- 1 root utmp 8064 Jan 13 00:57 wtmp The syslog seems overly huge. Is there a way to pull some diagnostics from SSH? Or a better idea where to start? - Thanks EDIT So I ran cat /var/log/syslog to see what's up and I got this a million times I think Jan 12 12:55:05 MANKY-DREADFUL emhttpd: Starting services... Jan 12 12:55:05 MANKY-DREADFUL emhttpd: shcmd (454399): /etc/rc.d/rc.samba restart Jan 12 12:55:05 MANKY-DREADFUL root: cp: cannot create regular file '/boot/config/secrets.tdb': Input/output error Jan 12 12:55:05 MANKY-DREADFUL kernel: FAT-fs (sda1): FAT read failed (blocknr 1313) Jan 12 12:55:07 MANKY-DREADFUL root: /etc/rc.d/rc.samba: line 25: /boot/config/machine-id: Input/output error Jan 12 12:55:07 MANKY-DREADFUL kernel: fat__get_entry: 1014 callbacks suppressed Jan 12 12:55:07 MANKY-DREADFUL kernel: FAT-fs (sda1): Directory bread(block 8608) failed Jan 12 12:55:07 MANKY-DREADFUL kernel: FAT-fs (sda1): Directory bread(block 8609) failed Jan 12 12:55:07 MANKY-DREADFUL kernel: FAT-fs (sda1): Directory bread(block 8610) failed Jan 12 12:55:07 MANKY-DREADFUL kernel: FAT-fs (sda1): Directory bread(block 8611) failed Jan 12 12:55:07 MANKY-DREADFUL kernel: FAT-fs (sda1): Directory bread(block 8612) failed Jan 12 12:55:07 MANKY-DREADFUL kernel: FAT-fs (sda1): Directory bread(block 8613) failed Jan 12 12:55:07 MANKY-DREADFUL kernel: FAT-fs (sda1): Directory bread(block 8614) failed Jan 12 12:55:07 MANKY-DREADFUL kernel: FAT-fs (sda1): Directory bread(block 8615) failed Jan 12 12:55:07 MANKY-DREADFUL kernel: FAT-fs (sda1): Directory bread(block 8616) failed Jan 12 12:55:07 MANKY-DREADFUL kernel: FAT-fs (sda1): Directory bread(block 8617) failed Jan 12 12:55:07 MANKY-DREADFUL kernel: FAT-fs (sda1): FAT read failed (blocknr 1313) Jan 12 12:55:07 MANKY-DREADFUL root: cp: cannot stat '/boot/config/machine-id': No such file or directory Jan 12 12:55:07 MANKY-DREADFUL root: Starting Samba: /usr/sbin/smbd -D Jan 12 12:55:07 MANKY-DREADFUL root: /usr/sbin/nmbd -D Jan 12 12:55:07 MANKY-DREADFUL root: /usr/sbin/winbindd -D Jan 12 12:55:08 MANKY-DREADFUL kernel: FAT-fs (sda1): FAT read failed (blocknr 1313) Jan 12 12:55:08 MANKY-DREADFUL kernel: FAT-fs (sda1): FAT read failed (blocknr 1313) Is this showing me that my flash drive is essentially failing? The log seems to have stopped post reboot, but I'm not sure. Edited January 13, 2020 by noja Quote Link to comment
JonathanM Posted January 13, 2020 Share Posted January 13, 2020 6 hours ago, noja said: Is this showing me that my flash drive is essentially failing? Possibly. It's showing that the drive was disconnected, whether because it's failing or there was a port problem, I'm not sure how to tell the difference. Are you using a USB2.0 device in a USB2.0 port? If using a 3.x port, try switching to a 2.0 Quote Link to comment
noja Posted January 13, 2020 Author Share Posted January 13, 2020 3 hours ago, jonathanm said: ...Are you using a USB2.0 device in a USB2.0 port? If using a 3.x port, try switching to a 2.0 Hmm, I think its the other way around. I think its a 3.0 device in the on-board 2.0 port of a supermicro X8DTL-3f. IPMI isn't showing me any errors, but I don't know if it would for this in any case. Would it help for me to post the entire raw syslog in a .txt doc? Is there anything in there that I shouldn't be posting in the open? Quote Link to comment
noja Posted January 15, 2020 Author Share Posted January 15, 2020 On 1/13/2020 at 2:35 AM, jonathanm said: Possibly. It's showing that the drive was disconnected, whether because it's failing or there was a port problem, I'm not sure how to tell the difference. Are you using a USB2.0 device in a USB2.0 port? If using a 3.x port, try switching to a 2.0 It was a dead USB. Thanks for the help! Quote Link to comment
Recommended Posts
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.