RealActorRob Posted June 6, 2023 Share Posted June 6, 2023 I have the backup from pre-6.9.2 (end of April backup) I just downloaded the backup from the 'corrupted' 6.11.5 (today, 6 Jun 2023) and that completed normally and quickly. So, to me it just looks like a temp glitch. How do I know if it's really corrupted or just went offline for a bit? Diagnostics attached. blacktower-diagnostics-20230606-1527.zip Quote Link to comment
itimpi Posted June 6, 2023 Share Posted June 6, 2023 I notice that the disk.cfg file in the diagnostics is 0 bytes which is not normal. Not checked all the other .cfg files (they should all contain human readable text). Quote Link to comment
RealActorRob Posted June 6, 2023 Author Share Posted June 6, 2023 mmm...so what to do about that? I have of course the previous backup but that was for a diff Unriad version and I have the drive assignments screenshot. Quote Link to comment
RealActorRob Posted June 6, 2023 Author Share Posted June 6, 2023 Weird, the browser shows the file is present and non zero but vi opens it with zero length. Quote Link to comment
itimpi Posted June 6, 2023 Share Posted June 6, 2023 16 minutes ago, RealActorRob said: Weird, the browser shows the file is present and non zero but vi opens it with zero length. That could indicate it is corrupt and contains binary data rather than text? Quote Link to comment
RealActorRob Posted June 12, 2023 Author Share Posted June 12, 2023 So what's the fix? Quote Link to comment
RealActorRob Posted June 20, 2023 Author Share Posted June 20, 2023 Put drive in Windows 10 machine. Chkdsk and the 'Tools' option under 'Properties' vai right click reported no isses. disk.cfg was readable just fine. Did a drag and drop backup of files. Couple of .notify files were unreadable but no big deal there (the bitrot plugin checker that always reports storj node files as 'corrupt' despite my efforts to exclude them...forget the name) ugh now have an error on server...interrupt at 0000:5819 on Dell R720xd Quote Link to comment
RealActorRob Posted June 21, 2023 Author Share Posted June 21, 2023 (edited) Found corruption in disk.cfg such as "diskSpindownD%lay.8="-1" (see the % vs an 'e'.) Had to delete more .notify files that wouldn't drag and drop but got the array started finally. USB drive was dying which was causing the NMI error on my Dell R720xd. New USB drive, key transferred after update Community Apps and adding Unraid Connect. Boots now. Whew. Glad it wasn't hardware....also found a apparently unoptimized BIOS setting, something I/O related for storage that I turned on. Edited June 21, 2023 by RealActorRob Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.