JorgeB Posted February 5, 2020 Share Posted February 5, 2020 Failure to unmount means something is still using the disk, diags that are saved to flash after a shutdown timeout might show the problem. Quote Link to comment
comet424 Posted February 5, 2020 Author Share Posted February 5, 2020 ah ok so far it hasn't done the retrying... now when I had that error I was using no cache drive and I was using the laptop hard drive as cache drive now that I formatted the ssd to be cache and copied files back to the ssd,, then stopped the array and started its working again.. crazy how issues... I did notice I tried to follow these instructions https://ownyourbits.com/2019/03/03/how-to-recover-a-btrfs-partition/ but none of the commands liked working and also you cant scrub a unmountable drive... or if its unassigned drive yet says btrfs the scrub is grayed out.. is it ok to scrub my data disks does it help clean up any errors as I seen it says check box repair blocks.. just curious if it helps performance?? so is setting the appdata updater is it good to set to daily and set to 5 so that means it will keep 5 copies right? or what is a good settings you use.. and I gonna insall the vm plugin you mentioned... is there any other plugins I need etc... as I have 1 ssd for cache/vms but I don't use it as cache and would it be ok to instead of adding vms appdata domains etc to cache drive... what if I add the SSD to my hard drive pool and exclude all shares except appdata domain system isos to write to that SSD then Parity would protect it is that safe to use ? I just asking it popped in my head as I writing this.. and I like to thank you for getting my files back as I was hitting road blocks googling.. and I make sure I switched to the new board sooner... as nothing but issues... but do love this unraid works great on a Asus gaming board didn't need to buy specific server grade stuff...…. it be nice your console typing etc was in the gui too but hey its ok least its back 🙂 Quote Link to comment
comet424 Posted February 5, 2020 Author Share Posted February 5, 2020 maybe I need to start over with my server... I having issues one the Recycling bin process sat for an 40 min or so at the bottom of screen as it disabled VMS and Dockers its now done I guess but Dockers still offline here is diagnostic file maybe you can see... as maybe I just need to do a fresh setup and transfer over and can you tell me if the array files are not corrupt etc.. then I wouldn't have to re copy all that and maybe only dockers and vms.. as I have not tried just swapping mobos and seeing if that corrects all errors from my current glitchy board tower-diagnostics-20200205-1123.zip Quote Link to comment
JorgeB Posted February 5, 2020 Share Posted February 5, 2020 Problems with the cache device: Feb 5 11:21:11 Tower kernel: sd 13:0:2:0: Power-on or device reset occurred Feb 5 11:21:11 Tower kernel: mpt2sas_cm0: log_info(0x31120303): originator(PL), code(0x12), sub_code(0x0303) ### [PREVIOUS LINE REPEATED 5 TIMES] ### Feb 5 11:21:11 Tower kernel: sd 13:0:2:0: [sdf] tag#175 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=0x00 Feb 5 11:21:11 Tower kernel: sd 13:0:2:0: [sdf] tag#175 CDB: opcode=0x2a 2a 00 00 00 b7 c0 00 00 40 00 Feb 5 11:21:11 Tower kernel: print_req_error: I/O error, dev sdf, sector 47040 Feb 5 11:21:11 Tower kernel: BTRFS error (device sdf1): bdev /dev/sdf1 errs: wr 3, rd 0, flush 0, corrupt 0, gen 0 Feb 5 11:21:11 Tower kernel: BTRFS error (device sdf1): bdev /dev/sdf1 errs: wr 4, rd 0, flush 0, corrupt 0, gen 0 Feb 5 11:21:11 Tower kernel: mpt2sas_cm0: log_info(0x31120303): originator(PL), code(0x12), sub_code(0x0303) ### [PREVIOUS LINE REPEATED 1 TIMES] ### Feb 5 11:21:12 Tower kernel: sd 13:0:2:0: Power-on or device reset occurred Feb 5 11:21:12 Tower kernel: mpt2sas_cm0: log_info(0x31120303): originator(PL), code(0x12), sub_code(0x0303) ### [PREVIOUS LINE REPEATED 7 TIMES] ### Feb 5 11:21:13 Tower kernel: mpt2sas_cm0: log_info(0x31111000): originator(PL), code(0x11), sub_code(0x1000) ### [PREVIOUS LINE REPEATED 2 TIMES] ### Feb 5 11:21:13 Tower kernel: sd 13:0:2:0: [sdf] tag#184 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=0x00 Feb 5 11:21:13 Tower kernel: sd 13:0:2:0: [sdf] tag#184 CDB: opcode=0x2a 2a 00 00 29 86 40 00 00 20 00 Feb 5 11:21:13 Tower kernel: print_req_error: I/O error, dev sdf, sector 2721344 Try it on a different controller. Quote Link to comment
comet424 Posted February 5, 2020 Author Share Posted February 5, 2020 is that switching cache to a different sata… its currently on LSI Raid Controller card... ill give it a try with the onboard sata port.. thanks for figuring things out so fast 🙂 Quote Link to comment
comet424 Posted February 5, 2020 Author Share Posted February 5, 2020 is there a test to test if its the ssd or if its the controller that is the problem I see now the ssd has a error under the drive 199 UDMA CRC error count 0x0032 100 100 --- Old age Always Never 103 so I have it plugged into the sata on the mobo… is there any tests to run to see if a drive or controller is failing Quote Link to comment
JorgeB Posted February 5, 2020 Share Posted February 5, 2020 Most likely a controller compatibility or cable issue, hence why I suggested using a different controller, see how it behaves there, UDMA CRC errors are a connection issue, not a device problem. Quote Link to comment
comet424 Posted February 5, 2020 Author Share Posted February 5, 2020 ok thanks very frustrating trouble shooting issues sometimes... ill try to load up some dockers see if it glitchs 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.