-
Posts
43,977 -
Joined
-
Last visited
-
Days Won
137
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by trurl
-
-
Unless you actually zeroed the data drives, parity should not be zeroed.
-
-
USB not recommended for array or pools for many reasons
-
52 minutes ago, agik said:
newbie
Attach Diagnostics to your NEXT post in this thread
-
17 minutes ago, michaelhthomas said:
the only errors I see in the syslog appear to be related to a corrupted docker image?
You must have overlooked all these:
May 13 08:21:13 Gringotts kernel: md: disk1 read error, sector=2312 May 13 08:21:13 Gringotts kernel: md: disk2 read error, sector=2312 May 13 08:21:13 Gringotts kernel: md: disk3 read error, sector=2312
And lots more before and after.
Since multiple disks are involved, probably a power or controller issue.
Any power splitters?
-
1 hour ago, saltz said:
mdcmd command
We're you following the current documentation for parity Swap?
There is no reason to enter mdcmd.
-
The config folder from your flash backup has all of your configuration when the backup was made. You can copy that config folder to a new install. See if you can still use the same flash so you won't have to transfer the license.
You should consider getting UPS for your server.
-
Attach Diagnostics to your NEXT post in this thread.
-
Why are you loading so many things in /boot/extra?
-
Post new diagnostics
-
The config folder on flash has all of your configuration. Backup and restore config folder
-
Attach Diagnostics to your NEXT post in this thread.
-
Attach Diagnostics to your NEXT post in this thread.
-
3 minutes ago, dzyuba86 said:
to a new flash drive
Try to use the same flash drive so you don't have to do a license transfer.
-
1 minute ago, Boy Kai said:
Disk 8 and Disk 12 are still showing red Xs
Repairing the filesystem will not fix that. But it will allow you to rebuild a mountable filesystem now.
Looks like repair didn't create any lost+found, and the emulated disks are mounted with plenty of data.
You can rebuild both at the same time.
https://docs.unraid.net/unraid-os/manual/storage-management/#rebuilding-a-drive-onto-itself
-
6 minutes ago, csimpson said:
created a couple scripts to delete the ._ and .ds_store
-
USB not recommended for array or pools for many reasons.
-
Corrupt docker.img. Seems unlikely that you would have filled it though. Have you done memtest? If not, you might do that before anything else just in case. You never want to run any computer unless memory is working perfectly.
You will have to delete, recreate, reinstall docker, but we will get to that later.
Your appdata and system shares have files on the array.
Ideally, appdata, domains, system shares would have all files on cache or other fast pool, with nothing on the array, so Dockers/VMs will perform better, and so array disks can spin down since these files are always open.
Nothing can move or delete open files, so you will have to disable Docker and VM Manager in Settings before you can work with these.
Then set these shares to Primary:cache; Secondary:array; Mover action:array->cache.
Then run Mover, wait for it to finish, and post new diagnostics.
-
11 hours ago, Kurse2000 said:
I did some file transfers today. Never got over 3MB/s.
Can you try transfer from a different computer?
-
So your plex server has to get media across the network before it can serve them. I don't see how this can be a good configuration for multiple streams.
-
Attach Diagnostics to your NEXT post in this thread
-
9 hours ago, droyster said:
ran memtest and it's got a bunch of failures
You shouldn't even attempt to run any computer unless RAM is working perfectly. Everything goes through RAM, the OS and other executable code, your data, everything. The CPU can't do anything with anything until it is loaded into RAM.
-
1 hour ago, kydar said:
A) remove the parity drive from the array and reattach it after adding data to the data drives.
This
- 1
-
2 hours ago, Kurse2000 said:
I never use either
Do you mean your Plex Server is not your Unraid server?
Parity sync with all new drives – why slow?
in General Support
Posted
And zeroing parity would not be very fast anyway since all of the disk has to be written.