November 5, 20178 yr I keep seeing these errors in my log- Nov 5 04:38:56 Brunnhilde kernel: EXT4-fs (sdo1): error count since last fsck: 2 Nov 5 04:38:56 Brunnhilde kernel: EXT4-fs (sdo1): initial error at time 1507791667: __ext4_get_inode_loc:4339: inode 37760008: block 150995680 Nov 5 04:38:56 Brunnhilde kernel: EXT4-fs (sdo1): last error at time 1507791667: ext4_reserve_inode_write:5418: inode 37760008: block 150995680 Nov 5 05:13:53 Brunnhilde kernel: EXT4-fs (sdp1): error count since last fsck: 33845 Nov 5 05:13:53 Brunnhilde kernel: EXT4-fs (sdp1): initial error at time 1507791667: __ext4_get_inode_loc:4339: inode 37760008: block 150995680 Nov 5 05:13:53 Brunnhilde kernel: EXT4-fs (sdp1): last error at time 1508655672: ext4_find_entry:1463: inode 2 I only have one disk in my server formatted as EXT4 (sds) so I'm not sure what these errors mean or what is generating them. There isn't a disk sdo1 or sdp1. brunnhilde-diagnostics-20171105-0840.zip
November 5, 20178 yr Community Expert Well that disk started as sdo: Oct 14 20:07:28 Brunnhilde kernel: usb-storage 4-2.2:1.0: USB Mass Storage device detected Oct 14 20:07:28 Brunnhilde kernel: scsi host10: usb-storage 4-2.2:1.0 Oct 14 20:07:29 Brunnhilde kernel: scsi 10:0:0:0: Direct-Access Elite Pro USB 0 PQ: 0 ANSI: 6 Oct 14 20:07:29 Brunnhilde kernel: sd 10:0:0:0: Attached scsi generic sg12 type 0 Oct 14 20:07:29 Brunnhilde kernel: sd 10:0:0:0: [sdo] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB) Oct 14 20:07:29 Brunnhilde kernel: sd 10:0:0:0: [sdo] Write Protect is off Oct 14 20:07:29 Brunnhilde kernel: sd 10:0:0:0: [sdo] Mode Sense: 43 00 00 00 Oct 14 20:07:29 Brunnhilde kernel: sd 10:0:0:0: [sdo] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Oct 14 20:07:33 Brunnhilde kernel: sdo: sdo1 The it got disconnect and reconnect as sdp: Oct 14 20:44:23 Brunnhilde kernel: usb 4-2.2: USB disconnect, device number 7 Oct 14 20:44:23 Brunnhilde kernel: blk_update_request: I/O error, dev sdo, sector 0 Oct 14 20:44:23 Brunnhilde kernel: sd 10:0:0:0: [sdo] Synchronizing SCSI cache Oct 14 20:44:23 Brunnhilde kernel: sd 10:0:0:0: [sdo] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00 Oct 14 20:44:23 Brunnhilde rc.diskinfo[17670]: PHP Warning: Missing argument 2 for force_reload() in /etc/rc.d/rc.diskinfo on line 691 Oct 14 20:44:23 Brunnhilde rc.diskinfo[17670]: SIGHUP received, forcing refresh of disks info. Oct 14 20:44:23 Brunnhilde kernel: usb 4-2: new SuperSpeed USB device number 8 using xhci_hcd Oct 14 20:44:23 Brunnhilde kernel: hub 4-2:1.0: USB hub found Oct 14 20:44:23 Brunnhilde kernel: hub 4-2:1.0: 4 ports detected Oct 14 20:44:23 Brunnhilde kernel: usb 4-2.2: new SuperSpeed USB device number 9 using xhci_hcd Oct 14 20:44:23 Brunnhilde kernel: usb-storage 4-2.2:1.0: USB Mass Storage device detected Oct 14 20:44:23 Brunnhilde kernel: scsi host11: usb-storage 4-2.2:1.0 Oct 14 20:44:24 Brunnhilde rc.diskinfo[17670]: PHP Warning: Missing argument 2 for force_reload() in /etc/rc.d/rc.diskinfo on line 691 Oct 14 20:44:24 Brunnhilde rc.diskinfo[17670]: SIGHUP received, forcing refresh of disks info. Oct 14 20:44:25 Brunnhilde kernel: scsi 11:0:0:0: Direct-Access Elite Pro USB 0 PQ: 0 ANSI: 6 Oct 14 20:44:25 Brunnhilde kernel: sd 11:0:0:0: Attached scsi generic sg12 type 0 Oct 14 20:44:25 Brunnhilde kernel: sd 11:0:0:0: [sdp] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB) Oct 14 20:44:25 Brunnhilde kernel: sd 11:0:0:0: [sdp] Write Protect is off Oct 14 20:44:25 Brunnhilde kernel: sd 11:0:0:0: [sdp] Mode Sense: 43 00 00 00 Oct 14 20:44:25 Brunnhilde kernel: sd 11:0:0:0: [sdp] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Oct 14 20:44:25 Brunnhilde kernel: sdp: sdp1 Same thing repeatedly happened again and it get's reconnect with a different letter. Your log is full of USB disconnects, one of the reasons USB devices are not really recommend. Edited November 5, 20178 yr by johnnie.black
November 5, 20178 yr Author I removed the usb drive yesterday, because of the disconnects, and installed it in an empty slot in my server. It is now mounted as sds. Is it possible these errors are being generated from a drive that’s no longer present?
Archived
This topic is now archived and is closed to further replies.