-
Posts
43637 -
Joined
-
Last visited
-
Days Won
137
Community Answers
-
trurl's post in Lost Movie files was marked as the answer
You should never format a disk that contains data you want to keep.
Format is a write operation. It writes an empty filesystem to the disk. When you format a disk in the array, Unraid treats this write operation just as it does any other, by updating parity. So, after formatting a disk in the array, the only thing it can rebuild is an empty filesystem.
Not enough information at this late date to know exactly what happened.
If you had asked for help when you were having problems maybe we could have saved your data.
-
trurl's post in Hide VMS tab was marked as the answer
Try deleting config/domains.cfg from your flash drive.
-
trurl's post in Initial array setup queries was marked as the answer
SSDs in the array cannot be trimmed, and can only be written at speed of parity
-
trurl's post in Lost OS drive. How to reassign disks correctly? was marked as the answer
https://docs.unraid.net/unraid-os/manual/changing-the-flash-device/#what-to-do-if-you-have-no-backup-and-do-not-know-your-disk-assignments
-
trurl's post in Backup/restore user shares on all new hardware was marked as the answer
All of your webUI settings are in the config folder on flash, including the user share settings.
But without any data, the shares won't actually exist.
You could create an empty top level folder named for the share on an assigned disk. That would be an empty user share and it would have the settings from the corresponding config/shares/*.cfg file.
Or you could just create the user shares in the webUI, and copy their settings from your flash backup.
-
trurl's post in Add parity drive and replace data drive was marked as the answer
Simple as that, except no need to set slot to no device. Just select the new device in that slot.
I prefer to reserve the verb "add" for situations where you are actually adding a disk to a new slot that didn't already have a disk assigned. Parity2, for example, in your case, but could be used when talking about a new data slot. What you are doing with the data disk is "replace".
-
trurl's post in Boot straight into bios was marked as the answer
You only need the config folder from your flash backup. It has all of your configuration (all settings made in the webUI), including your license and your disk assignments.
-
trurl's post in upgrade cache drive was marked as the answer
https://docs.unraid.net/unraid-os/manual/storage-management/#backing-up-the-pool-to-the-array
-
trurl's post in Unable to boot 6.12.8 was marked as the answer
https://docs.unraid.net/unraid-os/manual/troubleshooting/#bzimage-checksum-errorfailure-reading-flash-drive
-
trurl's post in Replacing parity, adding/removing drive was marked as the answer
Good plan.
Some try to make this too complicated instead of just using parity for its intended purpose.
-
trurl's post in Unable to write to cache Fix Common Problems was marked as the answer
SMART Extended Self-test Log Version: 1 (1 sectors) Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed: read failure 70% 4527 13602456 replace
-
trurl's post in Dashboard not displaying on 6.12.8 was marked as the answer
disklocation-master.plg - 2024.03.06 (Update available: 2024.03.06c)
-
trurl's post in Getting information from AppData was marked as the answer
I don't know if Unassigned Devices will let you mount that single nvme without starting the array. Probably older version of UD didn't but maybe later version will,
Any linux should be able to mount it.
If you know which disks are parity you can just New Config and assign disks in whatever order and rebuild parity. Be careful with the parity slot assignments as mentioned.
-
trurl's post in UNRAID is using port 8443? or? was marked as the answer
You can check this yourself in Settings - Management Access - Unraid Connect
-
trurl's post in Parity Disk Error - Replacement only option? was marked as the answer
Replace.
The disk firmware has tested it and says it is bad
-
trurl's post in Share Disappeared suddenly was marked as the answer
Are you sure it didn't get moved into another share?
Why do you have so many (45) shares? Have you been creating folders at the top level of disks? Top level folders on pools and array are automatically user shares.
Why do you have 325G docker.img? Default 20G is often more than enough, maybe a little more if you have a lot of containers. The usual cause of filling docker.img is an application writing to a path that isn't mapped. Making it larger is not the fix for this. Usage shouldn't be growing.
Why are your docker and VM related files on the array? Ideally, these would all be on fast pool such as cache, so Dockers/VMs will perform better, and so array disks can spin down since these files are always open.
-
trurl's post in Disk too small was marked as the answer
https://docs.unraid.net/unraid-os/manual/tools/#new-config
-
trurl's post in Unable to Update plugins, community apps, or update Unraid to latest version. was marked as the answer
Looks like your boot flash drive has gone read-only.
Do you have a current backup of the boot flash?
-
trurl's post in 6.12.8 - UnRAID Docker service failed to start was marked as the answer
You have btrfs csum errors on sdc, which is probably the reason for corruption.
And a very good reason to do memtest.
Do memtest before doing anything else.
You don't even want to attempt to run any computer unless memory 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.
-
trurl's post in Disk Disabled- Contents Emulated was marked as the answer
Nothing in logs since reboot.
To rebuild the disk to itself:
Stop array Unassign disk Start array with disk unassigned Stop array Reassign disk Start array to begin rebuild If it offers to format anything, DON'T
-
trurl's post in Creating new array always defaults to xfs despite having btrfs - encrypted in disk settings was marked as the answer
https://docs.unraid.net/unraid-os/manual/storage-management/#changing-a-file-system-type
-
trurl's post in spare license backup strategy was marked as the answer
If you don't have any configuration you want to keep, all you need is the license .key file in the config folder, or at least keeping that .key file associated with that flash drive in some way. The bz files are included in every version install.
-
trurl's post in Is it possible to swap a parity drive with a data drive? was marked as the answer
If you can make the to-be parity drive empty with all of its data elsewhere, then you can just New Config with all of the disks as you want them to be assigned, rebuild parity on the new parity (formerly data) disk, and format the new data (formerly parity) disk so it is ready for access.
-
trurl's post in Docker apps can't write directly to Array was marked as the answer
Looks like Minimum Free on that share is larger than the free space on any of your array disks.