shutterbug Posted January 18, 2016 Share Posted January 18, 2016 I'm currently running UNRAID 6.1.7 and have been upgrading to new versions on a relatively regular basis (i.e. applying the last 4 or 5 updates within a few days of release and rebooting). The other day I went to watch something on a PC running KODI, a video file that was in my KODI library (meaning it had previously indexed the file), and got the error that the file wasn't found. I went to another computer, checked the share on unraid, and sure enough, I found that I had lost all but 3 files within that particular directory. There would have been around 100 video files total, only 3 remained. I double checked through the unraid web gui, files showing as missing there as well. I'm not terribly upset about the loss of these particular video files, they can always be re-ripped, but I'm concerned about why they were lost, and what else I may have lost that I'm not seeing. Another thing I've noticed, but seemingly unrelated. My cache pool was nearly full - I looked at it, and I had 150gigs of video files sitting there apparently waiting to be moved (files that had been copied to unraid many weeks before). I initiated the mover, no change. I then went to manually move the files only to realize the files already existed in their destination folders. So they had been copied from the cache pool, but never removed. What next steps should I take? I've run a parity check (it completed with zero errors), and my unraid GUI shows no problems with any of my 8 drives (running 8 drives including parity, a combination of 2 and 3TB drives). I've seen reference to Reiserfsck in the unraid forums, should I run this? If so, can someone provide me with the recommended syntax/options of the command for unraid 6.1.7? Getting the files back would be nice, but more importantly I'd like to know why they vanished. Any logs I can be reviewing? Any other suggestions? Link to comment
shutterbug Posted January 18, 2016 Author Share Posted January 18, 2016 Thanks for the link, will give it a shot and report back once I've completed. Link to comment
shutterbug Posted January 19, 2016 Author Share Posted January 19, 2016 I completed a reiserfsck on each of my drives, all report no corruptions found. In looking at the system log that's accessible from the GUI under tools, I am seeing a slew of errors. Any thoughts on the errors below? What are my next steps? After checking all the drives with reiserfsck and re-running my parity check (which again completes with zero errors), my files are still missing. **NEW DEVELOPMENT: Last night I went to watch something from a folder I was viewer 24hrs prior, and it is gone as well. The folder and all sub-folders/files just gone. Probably around 20 files in this case just simply gone. This is in addition to the files missing since I started this post. Jan 17 10:51:58 zorg kernel: CPU: 0 PID: 1 Comm: swapper/0 Tainted: G I 4.1.15-unRAID #1 Jan 17 10:51:58 zorg kernel: Call Trace: Jan 17 10:51:58 zorg kernel: CPU: 0 PID: 1 Comm: swapper/0 Tainted: G W I 4.1.15-unRAID #1 Jan 17 10:51:58 zorg kernel: Call Trace: Jan 17 10:51:58 zorg kernel: CPU: 0 PID: 1 Comm: swapper/0 Tainted: G W I 4.1.15-unRAID #1 Jan 17 10:51:58 zorg kernel: Call Trace: Jan 17 10:51:58 zorg kernel: CPU: 0 PID: 1 Comm: swapper/0 Tainted: G W I 4.1.15-unRAID #1 Jan 17 10:51:58 zorg kernel: Call Trace: Jan 17 10:51:58 zorg kernel: CPU: 0 PID: 1 Comm: swapper/0 Tainted: G W I 4.1.15-unRAID #1 Jan 17 10:51:58 zorg kernel: Call Trace: Jan 17 10:51:58 zorg kernel: CPU: 0 PID: 1 Comm: swapper/0 Tainted: G W I 4.1.15-unRAID #1 Jan 17 10:51:58 zorg kernel: Call Trace: Jan 17 10:51:58 zorg kernel: CPU: 0 PID: 1 Comm: swapper/0 Tainted: G W I 4.1.15-unRAID #1 Jan 17 10:51:58 zorg kernel: Call Trace: Jan 17 10:51:58 zorg kernel: CPU: 0 PID: 1 Comm: swapper/0 Tainted: G W I 4.1.15-unRAID #1 Jan 17 10:51:58 zorg kernel: Call Trace: Jan 17 10:51:58 zorg kernel: ata4.00: exception Emask 0x0 SAct 0x1 SErr 0x280000 action 0x6 Jan 17 10:51:58 zorg kernel: ata4.00: irq_stat 0x00020002, device error via SDB FIS Jan 17 10:51:58 zorg kernel: ata4.00: error: { ICRC ABRT } Jan 17 10:51:58 zorg kernel: ata4.00: exception Emask 0x0 SAct 0x1 SErr 0x280000 action 0x6 Jan 17 10:51:58 zorg kernel: ata4.00: irq_stat 0x00020002, device error via SDB FIS Jan 17 10:51:58 zorg kernel: ata4.00: error: { ICRC ABRT } Jan 17 10:51:58 zorg kernel: ata18.00: exception Emask 0x1 SAct 0x0 SErr 0x0 action 0x0 Jan 17 10:51:58 zorg kernel: ata4.00: exception Emask 0x0 SAct 0x1 SErr 0x200000 action 0x6 Jan 17 10:51:58 zorg kernel: ata4.00: irq_stat 0x00020002, device error via SDB FIS Jan 17 10:51:58 zorg kernel: ata4.00: error: { ICRC ABRT } Jan 17 10:51:58 zorg kernel: ata4.00: exception Emask 0x0 SAct 0x1 SErr 0x280000 action 0x6 Jan 17 10:51:58 zorg kernel: ata4.00: irq_stat 0x00020002, device error via SDB FIS Jan 17 10:51:58 zorg kernel: ata4.00: error: { ICRC ABRT } Jan 17 10:51:58 zorg kernel: blk_update_request: I/O error, dev sde, sector 896 Jan 17 10:51:58 zorg kernel: blk_update_request: I/O error, dev sde, sector 896 Jan 17 10:51:58 zorg kernel: Buffer I/O error on dev sde, logical block 112, async page read Jan 17 10:51:58 zorg kernel: blk_update_request: I/O error, dev sde, sector 512 Jan 17 10:51:58 zorg kernel: blk_update_request: I/O error, dev sde, sector 512 Jan 17 10:51:58 zorg kernel: Buffer I/O error on dev sde, logical block 64, async page read Jan 17 10:51:58 zorg kernel: blk_update_request: I/O error, dev sde, sector 32 Jan 17 10:51:58 zorg kernel: blk_update_request: I/O error, dev sde, sector 32 Jan 17 10:51:58 zorg kernel: Buffer I/O error on dev sde, logical block 4, async page read Jan 17 10:51:58 zorg kernel: blk_update_request: I/O error, dev sde, sector 4096 Jan 17 10:51:58 zorg kernel: Buffer I/O error on dev sde, logical block 512, async page read Jan 17 10:51:58 zorg kernel: blk_update_request: I/O error, dev sde, sector 234441407 Jan 17 10:51:58 zorg kernel: blk_update_request: I/O error, dev sde, sector 234441407 Jan 17 10:51:58 zorg kernel: Buffer I/O error on dev sde1, logical block 234441344, async page read Jan 17 10:51:58 zorg kernel: blk_update_request: I/O error, dev sde, sector 234441408 Jan 17 10:51:58 zorg kernel: Buffer I/O error on dev sde1, logical block 234441345, async page read Jan 17 10:51:58 zorg kernel: Buffer I/O error on dev sde1, logical block 234441346, async page read Jan 17 10:51:58 zorg kernel: Buffer I/O error on dev sde1, logical block 234441347, async page read Jan 17 10:51:58 zorg kernel: Buffer I/O error on dev sde1, logical block 234441348, async page read Jan 17 10:51:58 zorg kernel: Buffer I/O error on dev sde1, logical block 234441349, async page read Jan 17 10:52:02 zorg kernel: blk_update_request: I/O error, dev sde, sector 234441472 Jan 17 10:52:02 zorg kernel: blk_update_request: I/O error, dev sde, sector 234441472 Jan 17 10:52:02 zorg kernel: Buffer I/O error on dev sde, logical block 29305184, async page read Jan 17 10:52:02 zorg kernel: blk_update_request: I/O error, dev sde, sector 234441632 Jan 17 10:52:02 zorg kernel: blk_update_request: I/O error, dev sde, sector 234441632 Jan 17 10:52:02 zorg kernel: Buffer I/O error on dev sde, logical block 29305204, async page read Jan 17 10:52:02 zorg kernel: blk_update_request: I/O error, dev sde, sector 0 Jan 17 10:52:02 zorg kernel: blk_update_request: I/O error, dev sde, sector 0 Jan 17 10:52:02 zorg kernel: Buffer I/O error on dev sde, logical block 0, async page read Jan 17 10:52:02 zorg kernel: blk_update_request: I/O error, dev sde, sector 8 Jan 17 10:52:02 zorg kernel: Buffer I/O error on dev sde, logical block 1, async page read Jan 17 10:52:02 zorg kernel: blk_update_request: I/O error, dev sde, sector 234441640 Jan 17 10:52:02 zorg kernel: Buffer I/O error on dev sde, logical block 29305205, async page read Jan 17 10:52:02 zorg kernel: blk_update_request: I/O error, dev sde, sector 234441640 Jan 17 10:52:02 zorg kernel: Buffer I/O error on dev sde, logical block 29305205, async page read Jan 17 10:52:02 zorg kernel: blk_update_request: I/O error, dev sde, sector 234441640 Jan 17 10:52:02 zorg kernel: Buffer I/O error on dev sde, logical block 29305205, async page read Jan 17 10:52:02 zorg kernel: Buffer I/O error on dev sde, logical block 29305205, async page read Jan 17 10:52:02 zorg kernel: Buffer I/O error on dev sde, logical block 29305205, async page read Jan 17 10:52:02 zorg kernel: Buffer I/O error on dev sde, logical block 29305205, async page read Jan 19 07:47:09 zorg kernel: blk_update_request: I/O error, dev sde, sector 234441407 Jan 19 07:47:09 zorg kernel: blk_update_request: I/O error, dev sde, sector 234441407 Jan 19 07:47:09 zorg kernel: Buffer I/O error on dev sde1, logical block 234441344, async page read Jan 19 07:47:09 zorg kernel: blk_update_request: I/O error, dev sde, sector 234441408 Jan 19 07:47:09 zorg kernel: Buffer I/O error on dev sde1, logical block 234441345, async page read Link to comment
trurl Posted January 19, 2016 Share Posted January 19, 2016 On any of the other computers you are using, do you have any drives mapped to your unRAID? Link to comment
shutterbug Posted January 19, 2016 Author Share Posted January 19, 2016 Typically I access via unc, but one of my VMs does have mapped drives, yes Link to comment
trurl Posted January 19, 2016 Share Posted January 19, 2016 Since parity agrees with your data then I think something is deleting the files. Maybe something can be done with inotify to see what is happening. inotify-tools is in NerdPack then google inotifywatch. I haven't used this. Link to comment
shutterbug Posted January 19, 2016 Author Share Posted January 19, 2016 Thank you, I will look into that. Any comments on the errors above? Should I be concerned about these? Link to comment
trurl Posted January 19, 2016 Share Posted January 19, 2016 Do you have any counts in the errors column on Main for sde? What does its SMART look like? Link to comment
shutterbug Posted January 19, 2016 Author Share Posted January 19, 2016 yes, SDE is part of the cache pool and needs to be replaced, currently it's just unassigned (not part of the pool). SMART is A-OK across the array. Link to comment
shutterbug Posted January 19, 2016 Author Share Posted January 19, 2016 I pulled my failing, unassigned SSD, and all errors except the kernal tainted errors were resolved. So the only errors left in the log are a bunch of these: Jan 19 10:49:44 zorg kernel: CPU: 0 PID: 1 Comm: swapper/0 Tainted: G I 4.1.15-unRAID #1 Jan 19 10:49:44 zorg kernel: Call Trace: Jan 19 10:49:44 zorg kernel: CPU: 0 PID: 1 Comm: swapper/0 Tainted: G W I 4.1.15-unRAID #1 Jan 19 10:49:44 zorg kernel: Call Trace: Jan 19 10:49:44 zorg kernel: CPU: 0 PID: 1 Comm: swapper/0 Tainted: G W I 4.1.15-unRAID #1 Jan 19 10:49:44 zorg kernel: Call Trace: Jan 19 10:49:44 zorg kernel: CPU: 0 PID: 1 Comm: swapper/0 Tainted: G W I 4.1.15-unRAID #1 Jan 19 10:49:44 zorg kernel: Call Trace: Jan 19 10:49:44 zorg kernel: CPU: 0 PID: 1 Comm: swapper/0 Tainted: G W I 4.1.15-unRAID #1 Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.