jbuszkie
-
Posts
711 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by jbuszkie
-
-
53 minutes ago, trurl said:
Not sure why you might think that.
Grasping at straws?? 😄
I think the shingled drive might be my answer...
-
I think my issue might be the fact that my destination drive is an archive (Shingled?) drive? That might be killing my writes?
Jim
-
1 minute ago, sota said:
also what parity write strategy are you using? RMW or Turbo Write? the former would definitely be ugly.
My md_write_method is set to reconstruct write.
-
1 minute ago, johnnie.black said:
Then dual parity isn't the reason for the slower performance, assuming the parity2 disk is working correctly, most likely it's copying small files or from a slower disk region.
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
-
I even turned off my crash plan docker before I started it...
-
No this is a modern 4 core.. (8 thread) i7..
-
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
-
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
-
6 minutes ago, Squid said:
You *can* however in the plugin's advanced settings set it to not stop the containers
That will work!! I didn't see the advanced settings! Thanks!
-
4 minutes ago, Squid said:
No. You have to do it manually if you want that
*pout* Not what I wanted to hear.. But what I expected to hear...
Thanks for confirming, Squid....
-
On 3/11/2020 at 9:37 AM, jbuszkie said:
Is there a way to just backup the flash drive? The appdata is (supposedly) getting backed up by crash plan. But The flash drive can no longer via crash plan.
So I'd like to use this to just back up the flash drive (then crash plan will backup the backup). I don't really want to stop all the dockers every time I want to back up the flash drive?
Bump...
-
11 hours ago, NitroNine said:
So I just ran this on disk 8 of my array (i first moved all the data off it to the other disks in my array), it completed (5TB drive so it took a while), I clicked Done. I then stopped the array, but when I went to tools>new config and checked all for Preserve current assignments, It didn't give me the option for apply, just Done. And I can't remove the drive from my array. I am using unraid 6.8.3 nvidia and don't have any parity drives at the moment.
Basically this drive is showing old, and before it starts to fail I want to remove it from the array, and replace it with a new 6TB drive.
Am I going about this the wrong way and/or is there an easier way for me to remove a drive from my array without any parity?
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!
-
Quote
Having only 1 parity drive in parity2 works just fine,
That's what I was looking for...
Quoteit's a bit more complex mathematically, so the CPU works ever so slightly harder.
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!
-
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..
-
*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*
-
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
-
Quote
At least that one is, it's using one of the two Asmedia ports.
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.
-
Quote
At least that one is, it's using one of the two Asmedia ports.
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 😄
-
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?
-
On 2/23/2020 at 11:31 PM, ramblinreck47 said:
Also, search for the BPN-DE3500HD, it's the newer version of the same thing.
Hehe.. You have an extra 0 in the part number! No wonder the search came up with nothing! 🙂
BPN-DE350HD
-
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
-
Look at the 800K one.. The errors start around 8:16ish
-
Yeah this after the reboots during the rebuild So the disabled disk info is not there...
... I actually found the syslogs..
-
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?
How slow is dual parity?
in General Support
Posted
I'm copying big enough files that get past the cache pretty quick, I imagine.. one thing I noticed when I broke the unbalance into smaller chunks, was that the copy would be "finished" but the remove (rm) command took a while.... or like it was waiting for the disk to be ready again before it could start the next group..