FAQ Feedback - for FAQ for unRAID v6

[ChatNoir]

1 hour ago, Perforator said:

1) how do you replace parity disk

2) how do you replace data disk

3) how do you shrink your array

The answers to all those questions and many more can be found in the documentation : https://wiki.unraid.net/Official_Documentation

 

1. https://wiki.unraid.net/UnRAID_6/Storage_Management#Upgrading_parity_disk.28s.29
2. https://wiki.unraid.net/UnRAID_6/Storage_Management#Replacing_disks
3. https://wiki.unraid.net/UnRAID_6/Storage_Management#Removing_data_disk.28s.29

[itimpi]

3 hours ago, Perforator said:

1) how do you replace parity disk

2) how do you replace data disk

3) how do you shrink your array

All three of these are already covered in the online documentation.

[strykn]

On 3/8/2017 at 11:13 AM, JorgeB said:

 

 

Create a temporary mount point, e.g.:

mkdir /x

Now attempt to mount the filesystem read-only:

mount -o usebackuproot,ro /dev/sdX1 /x

For a single device: replace X with actual device, don't forget the 1 in the end, e.g., /dev/sdf1

For a pool: replace X with any of the devices from the pool to mount the whole pool (as long as there are no devices missing), don't forget the 1 in the end, e.g., /dev/sdf1, if the normal read only recovery mount doesn't work, e.g., because there's a damaged or missing device you should use instead:

 

i'm attempting to recover the cache data, ahead of reformatting

i believe i was able to create the directory "x"

however, i was unable to mount 

i entered

 

mount -o usebackuproot,ro /dev/nvmeOn1 /x

 

but got "does not exist"

i've attached screen shot, and was assuming for nvme, that was correct

 

 

>>>See Below, from Terminal<<<

Linux 4.19.107-Unraid.
Last login: Sun Oct 18 10:03:30 -0500 2020 on /dev/tty1.
root@Titan:~# mkdir /x
mkdir: cannot create directory ‘/x’: File exists
root@Titan:~# mount -o usebackuproot,ro /dev/nvmeOn1 /x
mount: /x: special device /dev/nvmeOn1 does not exist.
root@Titan:~# 

 

 

 

 

[trurl]

7 hours ago, strykn said:

i entered

 

mount -o usebackuproot,ro /dev/nvmeOn1 /x

You haven't specified the partition number, that is why the instructions say

On 3/8/2017 at 12:13 PM, JorgeB said:

don't forget the 1 in the end

  

 

 

[strykn]

1 hour ago, trurl said:

You haven't specified the partition number, that is why the instructions say

  

 

 

Isn't the "1" on the end correct?

 

nvmeOn1

 

if not, how do i find out?

[trurl]

The 1 you included is part of the device name. You need to specify the partition.

 

What do you get from the command line with this?

lsblk

 

[antonio3427]

On 2/4/2020 at 5:57 AM, JorgeB said:

What can I do to keep my Ryzen based server from crashing/locking up with Unraid?

 

 

Ryzen on Linux can lock up due to issues with c-states, and while this should mostly affect 1st gen Ryzen there are reports that 2nd and even 3rd gen can be affected in some cases, make sure bios is up to date, then look for "Power Supply Idle Control" (or similar) and set it to "typical current idle" (or similar).

 

More info here:
https://forums.unraid.net/bug-reports/prereleases/670-rc1-system-hard-lock-r354/

 

 

Also many of those servers seem to be running overclocked RAM, this is known to cause stability issues and even data corruption on some Ryzen/Threadripper systems, even if no errors are detected during memtest, server and overclock don't go well together, respect max RAM speed according to config and CPU listed on the tables below.

 

Note: Ryzen based APUs don't follow the same generation convention compared to regular desktop CPUs and are generally one generation behind, so for example Ryzen 3200G is a 2nd Gen CPU:

 

 

 

1st gen Ryzen:

 

2nd gen Ryzen:

 

3rd gen (3xxx) and Zen3 (5xxx) Ryzen :

 

Threadripper 1st Gen:

 

Threadripper 2nd Gen:

 

Threadripper 3rd Gen:

 

 

I have changed to DD4-3200

[krisha]

Regarding the cache replacement procedure as described here in the FAQ:

 

I had problems with the mover moving some symbolic links of docker data, due to:

- wrong permissions. This was solved using 'New permissions' on just the cache drive

- symbolic links to content in docker. Those were never moved.

 

I finally used the plugin 'CA Backup / Restore Appdata' to backup and restore the docker data. The procedure mentioned in the FAQ I followed any way (Backup before moving, restore after moving back), but think this is not really necessary.

 

Maybe it's possible to extend the FAQ post by those 2 hints.

[gellux]

Similarly to above, I am also replacing my cache and have followed the instructions. I am left with a small amount of appdata on the cache after Moving. it's a lot of Plex metadata, can i literally just copy it to my laptop, replace the drive and copy it back? or should I do what above has said and do a full back up of appdata and then just ignore what's left on my soon-to-be-ex cache?

 

thanks.