senrab
-
Posts
89 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by senrab
-
-
50 minutes ago, JonathanM said:
RAM errors can do very random stuff, best case is unexplained crashes, worst case is persistent silent data corruption. All your data passes through RAM at some point.
With typical ECC, single bit errors are caught and corrected with a notation in the motherboard's hardware log, multi bit uncorrectable errors should trigger a complete lock so no further damage to your data can happen.
Memory issues are usually rare, but not rare enough to be ignorable.
Thanks for the info!
Do you know of a good AM4 board that uses ECC RAM?
I was hoping to go with a Ryzen 7 CPU because I currently have that in my gaming PC. I was thinking of upgrading that to a Ryzen 9 and move the Ryzen 7 into a new Unraid server.
-
17 hours ago, JonathanM said:
I prefer zero errors as opposed to very very few. Whether the extra cost is worth it is an exercise for the reader.
Cost isn't really a concern, as this is for my data so its important.
I am curious though, what kind of errors could I potencially see with non-ECC RAM?
Thanks!
-
50 minutes ago, Hoopster said:
unRAID is very hardware agnostic. It works on almost anything and certainly that MB/CPU combination is supported. Hardware choice for many comes down to what you want the server to be able to do; NAS only? NAS + Docker + VMs + several plugins? Something in between? Does it need to be able to do hardware transcoding for Plex, Emby, Jellyfin, etc? Do you need ECC RAM support (not required by unRAID)?
Decide what you want the system to do and then choose hardware that supports that.
Thanks for the reply!
I currently use my server for storing my files and Plex. I have docker installed and a few of the "recommended" plugins for unraid.
I don't see myself doing much more with it at this time but I guess I never know. Future proofing a little is never a bad thing.
As for ECC Ram, is that recommend?
Thanks again!
-
Hey everyone!
I am looking at upgrading my current unraid server's hardware. I am starting to notice its age.
I am wondering if a MSI X570-A Pro would be a good motherboard.
I have a brand new one and thought I could start with that and then put a Ryzen 7 5800x and go from there.
Would that motherboard work alright or should I look at a different one.
Thank you!
-
The transfer from Disk 3 to Disk 1 has finished but I noticed there are errors on Disk 1. I have tested multiple files and everything looks good and works. Should I be concerned? I clicked on Disk 1 and can't see anything out of the normal.
-
20 hours ago, jonathanm said:
My fault, I should have told you to skip step 4 as well.
The point of the extra steps is to move the drive assignments around so that content that started on disk1 will still be on disk1 when the procedure is done. However, it adds a bunch of complexity that is only needed if you care which disk holds what content. You mentioned earlier that you don't bother forcing content onto any particular disk, so it doesn't matter if the content is on a different number when you are done.
Also, the trailing slash thing is a common error. You forgot to put the slash after the source. The last slash on the destination doesn't matter, but you forgot the important one.
rsync --options /mnt/disk(source number)/ /mnt/disk(destination number)/
http://qdosmsq.dunbar-it.co.uk/blog/2013/02/rsync-to-slash-or-not-to-slash/
Thanks for the help!
I don't care which drive is assigned to which slot. As long as the data is safe, it doesn't matter to me.
-
9 minutes ago, Frank1940 said:
From my perspective, I don't have the time to work through exactly what you have done and what has to be done in future steps to achieve this position at the end of the conversion. I can only assume that the person who worked out this procedure in this section of the WIKI did try to make it as simple as possible to achieve the stated objective.
There are some other procedures described in the WIKI. So take a few minutes and read through the WIKI. You can also wait for @Squid to get back to you.
Ok, Thanks.
All I have done is skip the steps 10-15 as per @jonathanm instructions.
Once I verified the data from Disk 1 copied to Disk 4, I changed the file system of Disk 1 to XFS, formatted it and started copying the data from Disk 3 to Disk 1.
-
2 minutes ago, Frank1940 said:
This is the reason for steps 10 through 15 on the procedure that I pointed you to.
Can I leave it the way it is now and follow 10-15 when the transfer is done?
-
3 minutes ago, Frank1940 said:
Why?
I thought I was supposed to. The instructions say to put the swap disk in the excluded list.
Is this not correct anymore?
-
7 minutes ago, Squid said:
Post a screenshot of the error and of the main tab
Sent from my phone as I'm probably having a beer and enjoying a fire
I have posted the error, Global Share settings and the Movies Share settings showing that Disk1 is not in the included.
-
I cleared Disk 1 and started to move the data from Disk 3 to it.
I am getting an error that says 'disk1 disk2 disk3 is not defined / installed in the array. This will cause errors when writing to the array. Fix it here: Movies Settings'.
When I click 'Movies Settings' I see that the included disks are 2,3,4 ( I set disk 1 to exclude in the global share settings).
Should I be concerned about this? My data from Disk1 is now sitting on Disk4 so I am not too worried but I don't want parity to erase anything if it tries to fix anything.
Thanks!
-
1 minute ago, Frank1940 said:
It just knows! That is way you paid the big bucks to LimeTech so made sure that all of this type of detail is handled in the backgound without requiring any user intervention. The only time this is not true is if you restrict the data to certain disks and even then I don't it 'hides' data which is in a share which is not supposed to be on a particular disk, it just won't write more information to that share on that disk.
LOL! Thanks for the info!
I will stop the array and do a format/change file system and rinse and repeat for the next drive!
-
4 minutes ago, Squid said:
Parity is updated in real-time, so it will reflect the changes, and no check is strictly required or necessary
Great thanks!
If I now stop the array, change/format Disk1 (the disk I copied all data from) to XFS, then start the array, will this work?
From there I will copy all data from another drive to this drive (Disk 1). I guess what I am wondering is, how will Unraid know where the files are? My shares are setup across all drives. Since I have moved everything from Disk 1 to Disk 4, how does it know where the files are? Is it done through the shares? Some of my folders have data across multiple disks.
-
13 minutes ago, Squid said:
It means that on the rsync command you used, you added an extra slash to the command (if you look closely at the instructions, only one of the source and destination paths have the trailing slash (can't remember which), not both
Yes
Great thanks!
I have checked a bunch of files( a lot) and all seems good. Is the verify step recommended?
Also, do I have to do anything with parity? After I am done changing all of my drives to XFS, do I just need to run a parity check?
-
The transfer of files from the Disk1 to Disk4(destination drive) is complete.
I mapped to both disks from Windows to compare files and everything seems good!
What I am wondering though, on Disk4, it created a folder called Disk1 and put everything in there. Is this normal? Do I need to move the files back to the root?
Thanks!
-
OK. So the transfer of the first drive will complete in a few hours(Wow it takes a long time).
You mentioned that I can skip steps 10-18 from the instructions on the other post. In doing so, what are my next steps? After the copy and verify is done, I can format the original drive and use it for the next transfer. Do I have to do anything with parity? I'm assuming I need to reconfigure that at some point??
Thanks for the help!
-
Is it a problem to still have Plex running so my kids can still have access to their shows and movies?
-
2 minutes ago, jonathanm said:
Do you have any includes or excludes set currently?
No. All shares have access to all disks.
-
5 minutes ago, jonathanm said:
The array isn't going to be stopped, but if someone has files open, or adds files to a share that is being accessed, things get complicated. If you can tell people not to add or change files, and preferably temporarily not use the server, so much the better.
Best is to disable the docker and vm service so nothing is interfering there either.
If nobody is going to be accessing the files, then no need for a temporary folder, simply make an identical copy of all the folders. The side effect of this is that the temporarily duplicated files will be hidden from the user share system, so someone could make a change that you would subsequently format away. The file verification step should catch that, but easier not to have to mess with it at all.
Ok sounds good. This makes total sense.
I am the only one who writes to the server. The rest of the household uses it viewing media using Plex.
I just need to:
Add 3TB drive to the array as XFS
Run: cp -rpv /mnt/[source]/* /mnt/[dest]
format 'source' drive from previous step to XFS
Pick another drive and do the same.
Also, will I have to make any changes to my shares?
Thanks again for all of the help! It is greatly appreciated!
-
1 minute ago, jonathanm said:
It complicates some things, and simplifies others.
Is it acceptable to you to temporarily stop all array activity while the migration is happening, or will you be run out of town on a rail if certain people can't access what they want, when they want it?
LOL. I can manage either. If the array has to be stopped, it has to be stopped. I could also do this at certain times of the day when no one needs to access the server.
-
6 minutes ago, jonathanm said:
I was trying to get a feel for what the state of things were so I could recommend the most efficient order of operations.
Yes, add the 3TB as an additional array member and let unraid clear it. Be sure it is set to the format type you wish to use. Verify that only that drive is listed as unmountable, and select the option to format it. Copy (not move)* the entire content of one of the ReiserFS drives to the newly formatted drive. Verify the copy was complete and accurate, change the requested format type of the source drive, format it, lather rinse repeat.
*Moving the files is much slower than a copy, and eliminates the option for a do over if things go south.
Great! Thank you for the help!
Reading the directions on the other thread, it says I should make a folder on the destination drive(their example was the folder 't') and copy everything in there using:
cp -rpv /mnt/[source]/* /mnt/[dest]/t
Is this still the best way?
Sorry for all of the questions, I am learning that things are a lot different than when I first started with my unraid server(v5). I am just making sure everything is correct.( I am always nervous when I am moving my data around). lol
-
I know that new doesn't mean tested. Sorry, I was just stating that it wasn't in the server yet. I wasn't planning on putting it in the server(then testing it) until I was at that point.
I am just a little confused on the order this all should happen.
For the 3TB drive that I have sitting as unassigned, does that get added to the array as a new drive to the array? I am assuming that the drives in the array can be different file systems.
-
The 4TB is brand new. I haven't put it in the server yet. The 3TB that is sitting as unassigned is the former parity drive. I figured I would start with that one because the drives in my array are 3TB(2 of them) and a 2TB.
-
3 hours ago, Frank1940 said:
CRC errors are almost never caused by the HD itself. It is a communication issue between the HD and the buss (forget which one) on the MB. It is usually caused by a SATA data cable or its connection. Another point is that is not really a critical failure. The data will be retransmitted until it is received correctly. Of course, the side effort is that the data transfer rate will plummet during these corrections if there are very many errors occurring close together.
Great thanks for the info! I will try changing the sata cable and see if that corrects the CRC errors.
Looking to Upgrade Hardware
in Hardware
Posted
Actually, looking at the MSI board that I have, it says it supports Non-ECC, ECC (Non-ECC Mode) Unbuffered. Would that work or should I just go get a different one?
Thanks for the help!