mephtik Posted June 6, 2015 Share Posted June 6, 2015 I noticed the other day that I couldn't write files to my tower (named Atlas). Kept giving me an "Access denied" error. When I looked at the error log, I saw the following: Jun 5 15:15:07 Atlas kernel: REISERFS error (device sdi1): zam-7001 reiserfs_find_entry: io error (Errors) Jun 5 15:24:47 Atlas shfs/user: shfs_write: write: (5) Input/output error (Errors) Jun 5 15:24:47 Atlas shfs/user: shfs_write: write: (5) Input/output error (Errors) Jun 5 15:25:20 Atlas kernel: Buffer I/O error on device sdi1, logical block 96405551 (Errors) Jun 5 15:25:20 Atlas kernel: lost page write due to I/O error on sdi1 (Errors) Jun 5 15:28:45 Atlas shfs/user: shfs_write: write: (5) Input/output error (Errors) Jun 5 15:28:45 Atlas shfs/user: shfs_write: write: (5) Input/output error (Errors) Jun 5 15:29:15 Atlas kernel: Buffer I/O error on device sdi1, logical block 96405551 (Errors) Jun 5 15:29:15 Atlas kernel: lost page write due to I/O error on sdi1 (Errors) Jun 5 15:29:21 Atlas shfs/user: shfs_write: write: (5) Input/output error (Errors) Jun 5 15:29:21 Atlas shfs/user: shfs_write: write: (5) Input/output error (Errors) Jun 5 15:29:51 Atlas kernel: Buffer I/O error on device sdi1, logical block 96405551 (Errors) Jun 5 15:29:51 Atlas kernel: lost page write due to I/O error on sdi1 (Errors) Jun 5 15:44:49 Atlas shfs/user: shfs_write: write: (5) Input/output error (Errors) Jun 5 15:44:49 Atlas shfs/user: shfs_write: write: (5) Input/output error (Errors) Jun 5 15:45:21 Atlas kernel: Buffer I/O error on device sdi1, logical block 96405551 (Errors) Jun 5 15:45:21 Atlas kernel: lost page write due to I/O error on sdi1 (Errors) Jun 5 15:48:45 Atlas shfs/user: shfs_write: write: (5) Input/output error (Errors) Jun 5 15:48:45 Atlas shfs/user: shfs_write: write: (5) Input/output error (Errors) Jun 5 15:49:15 Atlas kernel: Buffer I/O error on device sdi1, logical block 96405551 (Errors) Jun 5 15:49:15 Atlas kernel: lost page write due to I/O error on sdi1 (Errors) Jun 5 15:49:22 Atlas shfs/user: shfs_write: write: (5) Input/output error (Errors) Jun 5 15:49:22 Atlas shfs/user: shfs_write: write: (5) Input/output error (Errors) Jun 5 15:49:52 Atlas kernel: Buffer I/O error on device sdi1, logical block 96405551 (Errors) Jun 5 15:49:52 Atlas kernel: lost page write due to I/O error on sdi1 (Errors) Jun 5 15:55:05 Atlas shfs/user: shfs_write: write: (5) Input/output error (Errors) Jun 5 15:55:07 Atlas shfs/user: shfs_write: write: (5) Input/output error (Errors) I see it referencing problems with device sdi1, but (as far as I know) I have no device sdi1. Here's a list of devices: I've started running reiser check disk utility (following directions at http://lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems) but I've gone through half the disks so far and found no problems. Should I be doing something else, or...? Link to comment
trurl Posted June 6, 2015 Share Posted June 6, 2015 Post a more complete screenshot and a complete and current syslog. Link to comment
mephtik Posted June 6, 2015 Author Share Posted June 6, 2015 The code I posted was all that appeared when I'd try to write files to the system. For the past day I've been in maintenance mode running reiserfsck, hence the outdated-ness of the log. I don't know what you mean by wanting a more complete screenshot? That lists the details about the devices. Does knowing the current temperature of the drives matter for diagnosing this problem? Link to comment
trurl Posted June 6, 2015 Share Posted June 6, 2015 I'm on v6 and it's been a while since I've seen a v5 UI. Isn't there columns for error and read/writes? Also, it looks like your parity is invalid. Maybe take a look at some of the other pages and see what else it says that may be useful. Can you tell from reading your syslog right now which of the disks in the screenshot it is talking about? If you can't, then post a complete and current syslog please. Link to comment
mephtik Posted June 6, 2015 Author Share Posted June 6, 2015 I finished running the reiser check disk utility on all the disks, couldn't find any problems. Had the crazy idea to reboot the system. Everything is working fine now. Not getting SMB access errors, not seeing any errors in the log. Ugh. Link to comment
trurl Posted June 7, 2015 Share Posted June 7, 2015 Your previous screenshot didn't have a green ball next to the parity drive. Is that also fixed now? Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.