Differences

This shows you the differences between two versions of the page.

--- error_messages [2022/02/03 00:46] – johnsanc
+++ error_messages [2023/07/04 15:31] (current) – johnsanc
@@ Line 2: / Line 2: @@
 ====== Error Messages ======
-|**ⓘ NOTE:** \\ This page is under construction and should not be considered comprehensive. This page aims to document all "friendly" errors you may encounter along with guidance how to resolve those errors. All Stack Trace errors should be considered bugs and reported on the [[https://discord.gg/fVJQPA8|RomVault Discord]].|
+<WRAP info>This page is under construction and should not be considered comprehensive. This page aims to document all "friendly" errors you may encounter along with guidance how to resolve those errors. All Stack Trace errors should be considered bugs and reported on the [[https://discord.gg/fVJQPA8|RomVault Discord]].</WRAP>
 \\
@@ Line 137: / Line 137: @@
 ==== Double Name Found ====
-  * Two or more DATs in a directory share the same value in their header "name" tag
+  * There are sets that share the same name with different character case
-  * Remediation: Move each of the conflicting DATs into their own subdirectory or modify the name tags in the DATs so they are unique. You can also try adjusting your Directory Rules to use the DAT Description value instead of Name.
+  * Remediation: Double check your filesystem case sensitivity settings and if you have multiple files/directories that have the same name but different character case. Remove any duplicates and try again.
 ==== Error is Set Missing Status in DatUpdate ====
@@ Line 208: / Line 208: @@
   * This error should never occur, and if it does there is likely a logic error in the RomVault code. Basically this error means there is an invalid combination of ROM statuses and fix statuses.
   * Remediation: Report the error on Discord.
+==== Deleting [X] Correct file not found. Rescan for [Y] ====
+  * Before deleting an unneeded file, RomVault checked that the other copy actually exists but could not find the file.
+  * Remediation: Rescan your files to ensure your cache is up-to-date with your filesystem.
+==== Deleting [X] Correct file timestamp not found. Rescan for [Y] ====
+  * Before deleting an unneeded file, RomVault checked that the other copy actually exists but the modified timestamp of that file didn't match what is in the cache.
+  * Remediation: Rescan your files to ensure your cache is up-to-date with your filesystem.
+==== Delete Check found multiple tree paths to the same file. Tree structure should be fixed: 1st Path = [X] 2nd Path = [Y] ====
+  * Before deleting an unneeded file, RomVault checked that the other copy actually exists but found that the same file was referenced from more than one path. This is most likely to occur if you have misconfigured directory rules or a ToSort directory that also exists underneath your RomRoot.
+  * Remediation: Check and correct any misconfigured directory rules ensuring they are mutually exclusive. Also check that no ToSort directories are located within your RomRoot. It is technically possible to have such a setup, but you must be careful not scan any files from that directory from the RomRoot path and only scan from the ToSort path.
+==== Rescan needed, File Not Found : [X] ====
+  * The file RomVault was attempting to use for a fix was not found. Your cache is out of sync with your filesystem. Its also possible there is a case sensitivity mismatch with the file RomVault is looking for.
+  * Remediation: Rescan your files to ensure your cache is up-to-date. If you continue to run into issues, check your case sensitivity configuration settings for any remote shares (rclone mounts, SMB shares, etc.).
+==== Rescan needed, File Changed : [X] ====
+  * The file RomVault was attempting to use for a fix was found, but the timestamp did not match what is recorded in the cache. Your cache is out of sync with your filesystem.
+  * Remediation: Rescan your files to ensure your cache is up-to-date. If you continue to run into issues, check your timestamp configuration settings for any remote shares. Its possible that the timestamp granularity conflicts could cause RomVault to flag a file as modified when it was not.