• Posts

  • Joined

  • Last visited

Everything posted by jbuszkie

  1. I think my issue might be the fact that my destination drive is an archive (Shingled?) drive? That might be killing my writes? Jim
  2. My md_write_method is set to reconstruct write.
  3. No... These are DVD VOB's pretty decent size.. I just upgraded a disk. It finished before I started the move.. Everything is green.. But I wonder if it's still trying to emulate the disk I upgraded... Maybe I'll try a reboot. Also, I started a docker upgrade (just recently after I noticed the slow move) and it's taking forever! The dash board said I'm about 50-80% cpu usage... Extracting is taking forever... Once that's done I'll try a reboot, I guess... Jim
  4. I even turned off my crash plan docker before I started it...
  5. No this is a modern 4 core.. (8 thread) i7..
  6. I just added a second parity disk. That went fine. Now I'm trying to empty a disk (using unbalance) so I can finally change the few riserfs's I have left. Before dual parity, the move was about 30-45MB/s... Now with dual parity I'm hovering 13-15MB/s Is this expected? Thanks, Jim
  7. Bump.. I assume this hasn't been implemented yet? I'm rebuilding a data disk and I almost had to reboot the system (I think crash plan was bringing my system to a halt..) I was able to stop crash plan and the system started responding again.. But I'd love for it to remember where is was during a disk rebuild/parity check/Parity build... Jim
  8. That will work!! I didn't see the advanced settings! Thanks!
  9. *pout* Not what I wanted to hear.. But what I expected to hear... Thanks for confirming, Squid....
  10. If you don't have any parity then you don't have to run this script. With the array stopped just pick no device for that slot and go with the new config keep current assignments.... as I understand it. Now I've never tried this with no parity drive assigned.. So maybe there is a bug there... The whole Idea with the zeroing drive script is to keep parity valid while you remove a drive from the array. But you don't have parity so you should be able to just pull the drive. You could also try "new config" without the preserve and just re-assign. Just make sure you take a picture or write down the current assignments so you can duplicate them... What I did with the array stopped was to remove the drive from the list first, then I did the new config with preserve and it worked fine for me. Jim Edit: Now I see this was already replied to! Stupid browser not bringing me to the last message!
  11. That's what I was looking for... Very interesting and good to know. I knew that the 2nd parity uses drive position.. But I didn't know that it was the Parity 2 slot.. not just a 2nd parity drive!
  12. This is probably another dumb question... But I want to add a second parity disk (10TB). I'll assign it to the parity 2 slot. Now if for some reason I need the disk space and I want to go back to one parity disk... Can I get rid of the Parity 1 (8TB) disk and just have single parity on the parity 2 slot? Or do I have to re-assign the 10TB to Parity 1 and have to rebuild parity completely? Jim Edit: I will eventually make both parity 10TB.. But for now I'll stick with a 8TB array limit..
  13. *Sigh* Everyone may know this but I didn't... When using user scripts if you click outside the script window in the main window that will also kill the script. So not just hitting the "X".. I was about a 1/4 into zeroing out a drive when I accidentally click outside the script window and killed it! *sigh*
  14. Nice! I missed the 0000:04:00.0 being able to be mapped back to a PCI device! From the LSPCI I also could have seen that 04:00.0 mapped to the ASMedia device! Thanks, Jim
  15. Ok.. I give up.. How were you able to tell that ata7 and ata8 where the Asmedia ports from the syslog? Because I know my motherboard.. I could figure it out.. But I can't find anywhere which ports are mapped to which controller in the syslog... There is no mention of asmedia in the syslog.
  16. I keep forgetting how to piece everything together in the syslog! I haven't had to look at the syslog in a long time LOL. I have to re-learn each time 😄
  17. Has anyone ever had issues with a slot going bad in the Norco drive cages? Two different slots in two different cages are, potentially, giving me issues. One is causing the drive to disappear and the other is give sporadic CRC errors. I'm going to look into if it's the cables or the slot. But I was curious to know if anyone ever had a slot go bad on them?
  18. Hehe.. You have an extra 0 in the part number! No wonder the search came up with nothing! 🙂 BPN-DE350HD
  19. Crap! Those are two different Norco drive cages. One with the dropped disk and one with the CRC errors. And it's not like I bumped the machine or anything.. I guess it's time to open her up and check for loose cables to the cages! So the drive might be good??? hmm.. Anyone seen years of vibrations knocking a sata cable loose on a drive cage? I *think* both of those slots in question are connected to the MB not the LSI card... Has anyone seen norco slots go bad? Thanks @johnnie.black
  20. Look at the 800K one.. The errors start around 8:16ish
  21. Yeah this after the reboots during the rebuild So the disabled disk info is not there... ... I actually found the syslogs.. syslog-20200311-074811.txt syslog-20200311-082322.txt
  22. I'll give the diags.. But I'm not sure what help it will be. They don't contain any historical data about failed disks, right? You would be able to see the CRC errors in the SMART report.. What else is useful in there? tower-diagnostics-20200311-1114.zip
  23. I'm seeing this too.. I remember something sent to me about them requiring more log in This what I found on in my e-mail
  24. Yeah.. I know the CRC are connection issues.. usually.. But these cables haven't been touched in years... I'm worried about the drive red-balling in slot A... Is it the drive or the slot...