Smurf-IV
Becomes unresponsive during check command. Its crashed.
Been like this for a few hours:
State of Elucidate @ unresponsive:
Questions: 1 - via logs or other approaches, can we tell if SnapRAID has crashed or Elucidate? 2 - During a Check process, may I assume nothing in the array - including parity and content files are damaged? I.e.: If I force quit the app, everything should be fine? ...I can attempt to recheck etc.?
- SnapRaid was reporting 0% cpu which is strange, then it dumped an "Everything OK" message - Also Strange
- Did you se if SnapRaid was still running in the Apps -> Details tab of Task Manager?
- Read on the SnapRaid forum, but I think yes, eveythin should be readonly during a check - Scrub is the more "Active one"
a) Did you have an addition option to Stop on first error ? b) What version of SnapRaid Are you using ? c) What version of Elucidate ? d) can you compress the Elucidate logs for that run and attach to this please ?
First I should say I am a newbie user. This is a new W10 build using a preexisting drive/data set. However, I did an initial sync successfully. Then a scrub. Then added a few files to the array followed by another sync. All good. I'm not paranoid, but I'm new so I ran the check command.
I Ieft the system in the non-responding state over night - then I restarted the machine and another check is running.
Your questions:
- No I did not.
- OK - and confirmed a) No. b) SnapRAID 11.6 Windows x64 c) Elucidate 21.4.1030.4 d) Not sure how that is done. Log History is blank - and note the GUI issues in the upper left corner:
I am currently running another check - hoping that this was a "one-off" problem. Happy to provide you logs; but I'll need some direction. Thanks Simon.
Current check is at 51%. Check is proceeding as before - but no crash yet, I decide to check the Task Manager as requested:
I'll report either way; but reopen if it crashes again.
Last I checked it was at 60% - then just now, its back to 0%. What would cause it to start all over?
I have to say, that this is a problem. Running a check on 64TB's is a lengthy procedure - never mind if it stops midstream. Here I am - 3 days later - and its now at 1%.
Thanks for sticking with this..
I have Approx 48TB (protected by 3 *8TB drives), so you've definitely exceeded my current test capability (Still haven't filled up the rest of the possible space yet.). How many Raid drives have you set ?
Thank-fully, check completed.
Yay
I would be curious on how to check logs.
Located here:
There are 7x 8TB data drives protected by 1x 10TB parity drive. (I have a drive chassis expander and another 10 TB drive enroute - perhaps in a week.) All but one of the 7 drives are pretty full. (They have about 30-50GB's free.) The Parity drive has a 7.8 TP file on in.
Logs are attached.