Yipee Posted January 23, 2017 Share Posted January 23, 2017 Can someone please let me know what these errors mean? I have a bad cache drive? It's where I have Plex installed and I can't start it any more. an 23 08:23:23 Tower kernel: BTRFS error (device loop0): bdev /dev/loop0 errs: wr 0, rd 4120, flush 1, corrupt 0, gen 0 Jan 23 08:23:28 Tower shfs/user: err: shfs_readdir: fstatat: appdata (13) Permission denied Jan 23 08:23:28 Tower shfs/user: err: shfs_readdir: readdir_r: /mnt/cache/. (13) Permission denied Jan 23 08:23:28 Tower emhttp: err: get_filesystem_status: scandir: Permission denied Jan 23 08:23:28 Tower kernel: REISERFS error (device sdi1): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [2 5303 0x0 SD] Jan 23 08:23:29 Tower kernel: blk_update_request: I/O error, dev loop0, sector 191872 Jan 23 08:23:29 Tower kernel: BTRFS error (device loop0): bdev /dev/loop0 errs: wr 0, rd 4121, flush 1, corrupt 0, gen 0 Jan 23 08:23:29 Tower kernel: blk_update_request: I/O error, dev loop0, sector 2289024 Jan 23 08:23:29 Tower kernel: BTRFS error (device loop0): bdev /dev/loop0 errs: wr 0, rd 4122, flush 1, corrupt 0, gen 0 Jan 23 08:23:29 Tower kernel: blk_update_request: I/O error, dev loop0, sector 191872 Jan 23 08:23:29 Tower kernel: BTRFS error (device loop0): bdev /dev/loop0 errs: wr 0, rd 4123, flush 1, corrupt 0, gen 0 Jan 23 08:23:29 Tower kernel: blk_update_request: I/O error, dev loop0, sector 2289024 Jan 23 08:23:29 Tower kernel: BTRFS error (device loop0): bdev /dev/loop0 errs: wr 0, rd 4124, flush 1, corrupt 0, gen 0 Jan 23 08:23:29 Tower kernel: blk_update_request: I/O error, dev loop0, sector 191872 Jan 23 08:23:29 Tower kernel: BTRFS error (device loop0): bdev /dev/loop0 errs: wr 0, rd 4125, flush 1, corrupt 0, gen 0 Jan 23 08:23:29 Tower kernel: blk_update_request: I/O error, dev loop0, sector 2289024 Jan 23 08:23:29 Tower kernel: BTRFS error (device loop0): bdev /dev/loop0 errs: wr 0, rd 4126, flush 1, corrupt 0, gen 0 Jan 23 08:23:29 Tower kernel: blk_update_request: I/O error, dev loop0, sector 191872 Jan 23 08:23:29 Tower kernel: BTRFS error (device loop0): bdev /dev/loop0 errs: wr 0, rd 4127, flush 1, corrupt 0, gen 0 Jan 23 08:23:29 Tower kernel: blk_update_request: I/O error, dev loop0, sector 2289024 Jan 23 08:23:29 Tower kernel: BTRFS error (device loop0): bdev /dev/loop0 errs: wr 0, rd 4128, flush 1, corrupt 0, gen 0 Jan 23 08:23:29 Tower kernel: blk_update_request: I/O error, dev loop0, sector 191872 Jan 23 08:23:29 Tower kernel: BTRFS error (device loop0): bdev /dev/loop0 errs: wr 0, rd 4129, flush 1, corrupt 0, gen 0 Jan 23 08:23:29 Tower kernel: blk_update_request: I/O error, dev loop0, sector 2289024 Jan 23 08:23:29 Tower kernel: BTRFS error (device loop0): bdev /dev/loop0 errs: wr 0, rd 4130, flush 1, corrupt 0, gen 0 Jan 23 08:23:43 Tower shfs/user: err: shfs_readdir: fstatat: appdata (13) Permission denied Jan 23 08:23:43 Tower shfs/user: err: shfs_readdir: readdir_r: /mnt/cache/. (13) Permission denied Jan 23 08:23:43 Tower emhttp: err: get_filesystem_status: scandir: Permission denied Jan 23 08:23:43 Tower kernel: REISERFS error (device sdi1): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [2 5303 0x0 SD] Jan 23 08:24:01 Tower shfs/user: err: shfs_readdir: fstatat: appdata (13) Permission denied Jan 23 08:24:01 Tower shfs/user: err: shfs_readdir: readdir_r: /mnt/cache/. (13) Permission denied Jan 23 08:24:01 Tower emhttp: err: get_filesystem_status: scandir: Permission denied Jan 23 08:24:01 Tower kernel: REISERFS error (device sdi1): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [2 5303 0x0 SD] Jan 23 08:24:38 Tower shfs/user: err: shfs_readdir: fstatat: appdata (13) Permission denied Jan 23 08:24:38 Tower shfs/user: err: shfs_readdir: readdir_r: /mnt/cache/. (13) Permission denied Jan 23 08:24:38 Tower emhttp: err: get_filesystem_status: scandir: Permission denied Jan 23 08:24:38 Tower kernel: REISERFS error (device sdi1): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [2 5303 0x0 SD] Jan 23 08:25:01 Tower shfs/user: err: shfs_readdir: fstatat: appdata (13) Permission denied Jan 23 08:25:01 Tower shfs/user: err: shfs_readdir: readdir_r: /mnt/cache/. (13) Permission denied Jan 23 08:25:01 Tower emhttp: err: get_filesystem_status: scandir: Permission denied Jan 23 08:25:01 Tower kernel: REISERFS error (device sdi1): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [2 5303 0x0 SD] Jan 23 08:25:09 Tower kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Jan 23 08:25:09 Tower kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Jan 23 08:25:09 Tower kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Jan 23 08:25:09 Tower kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Jan 23 08:25:09 Tower kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Jan 23 08:26:01 Tower shfs/user: err: shfs_readdir: fstatat: appdata (13) Permission denied Jan 23 08:26:01 Tower shfs/user: err: shfs_readdir: readdir_r: /mnt/cache/. (13) Permission denied Jan 23 08:26:01 Tower kernel: REISERFS error (device sdi1): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [2 5303 0x0 SD] Jan 23 08:26:01 Tower emhttp: err: get_filesystem_status: scandir: Permission denied Jan 23 08:27:01 Tower shfs/user: err: shfs_readdir: fstatat: appdata (13) Permission denied Jan 23 08:27:01 Tower shfs/user: err: shfs_readdir: readdir_r: /mnt/cache/. (13) Permission denied Jan 23 08:27:01 Tower emhttp: err: get_filesystem_status: scandir: Permission denied Jan 23 08:27:01 Tower kernel: REISERFS error (device sdi1): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [2 5303 0x0 SD] Jan 23 08:28:01 Tower shfs/user: err: shfs_readdir: fstatat: appdata (13) Permission denied Jan 23 08:28:01 Tower shfs/user: err: shfs_readdir: readdir_r: /mnt/cache/. (13) Permission denied Jan 23 08:28:01 Tower emhttp: err: get_filesystem_status: scandir: Permission denied Jan 23 08:28:01 Tower kernel: REISERFS error (device sdi1): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [2 5303 0x0 SD] Jan 23 08:29:01 Tower shfs/user: err: shfs_readdir: fstatat: appdata (13) Permission denied Jan 23 08:29:01 Tower shfs/user: err: shfs_readdir: readdir_r: /mnt/cache/. (13) Permission denied Jan 23 08:29:01 Tower kernel: REISERFS error (device sdi1): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [2 5303 0x0 SD] Jan 23 08:29:01 Tower emhttp: err: get_filesystem_status: scandir: Permission denied Link to comment
Squid Posted January 23, 2017 Share Posted January 23, 2017 You should post your full diagnostics. You've got errors on your docker.img and your cache drive. Probably a bad cable caused the cache to drop offline but hard to tell w8thout diagnostics Sent from my LG-D852 using Tapatalk Link to comment
Yipee Posted January 23, 2017 Author Share Posted January 23, 2017 Diagnostic attached. TIA! tower-diagnostics-20170123-0857.zip Link to comment
trurl Posted January 23, 2017 Share Posted January 23, 2017 Your cache drive has dropped offline so we can't tell anything about it, but since that is where your docker.img is, that explains why your dockers don't work. Check connections. Disk4 is terrible. It needs to be replaced ASAP: Jan 20 20:05:41 Tower kernel: md: import disk4: (sdf) Hitachi_HDS5C3020ALA632_ML4220F3131YNK size: 1953514552 Serial Number: ML4220F3131YNK 5 Reallocated_Sector_Ct 0x0033 011 011 005 Pre-fail Always - 1776 196 Reallocated_Event_Count 0x0032 001 001 000 Old_age Always - 2781 197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 2 Disk7 doesn't look too good either: Jan 20 20:05:41 Tower kernel: md: import disk7: (sdj) ST3000DM001-9YN166_W1F1BK02 size: 2930266532 Serial Number: W1F1BK02 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 944 Also, all of your disks except disk8 are full or nearly full and ReiserFS, so you likely have performance issues trying to write to them. Since your parity is 3TB and disk4 is bad and only 2TB, you could replace disk4 with a 3TB disk and that would help some. First things first, check connections to cache disk and post a new diagnostic. Do you have backups? Link to comment
Yipee Posted January 23, 2017 Author Share Posted January 23, 2017 Thank you for the info trurl! I appreciated. I don't have a back up but I'll replace disk 4 and 7 hopefully today. I have one that is preclearing right now and waiting for another drive to come in. My cache drive still show active and connected. Hmmm. Maybe I need to replace it too because it went down before. What do you think about putting my docker.img and apps on the main array so it's protected? Link to comment
trurl Posted January 23, 2017 Share Posted January 23, 2017 Thank you for the info trurl! I appreciated. I don't have a back up but I'll replace disk 4 and 7 hopefully today. I have one that is preclearing right now and waiting for another drive to come in. My cache drive still show active and connected. Hmmm. Maybe I need to replace it too because it went down before. What do you think about putting my docker.img and apps on the main array so it's protected? If your cache drive is showing up now, post a new diagnostic so we can make sure it's OK. No I don't recommend putting apps on the array. Do you not have Notifications setup? You should have been getting emails telling you your disks were bad. It is very important that you don't allow disk problems to accumulate. If you have more disk failures than you have parity disks you will lose data. Parity by itself cannot save you. All bits of all disks must be reliable because all bits of all disks are required to calculate the data for a missing disk. And make a backup plan. You absolutely must have multiple copies of any irreplaceable files. Parity will not save you from not having backups either. Link to comment
Yipee Posted January 23, 2017 Author Share Posted January 23, 2017 Thanks for the advice. My cache drive never dropped of according to the main page. It shows normal operation, device is active, even when I ran the first diagnostic so I don't know what's going on. Link to comment
JorgeB Posted January 23, 2017 Share Posted January 23, 2017 Unlike array devices sometimes the only clue that the cache dropped offline is the lack of temperature display, most times it will still display a green dot. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.