Loosing partial WU with power fail

[Core32]

Ok. The new 6166HE 4P is folding, but I have an issue with it I did not have with the 6128 version.
These are identical HW in every way except CPU.
I even cloned the 6128 HDD to the new HDD in the 6166HE system.

I had the first 6903 at 73% complete when I lost power. I was not at home so the UPS only lasted about 10 minutes with this load Only 600W ater all!
When I arrived home I restarted the system, ran the kraken and ran the fah6 start command. Noticed the fold did not restart and when I looked at the trail I saw this:

[22:09:04] Work directory not found. Creating...
[22:09:04] Loaded queue successfully.
[22:09:04] 
[22:09:04] + Processing work unit
[22:09:04] Core required: FahCore_a5.exe
[22:09:04] Core found.
[22:09:04] Working on queue slot 02 [March 31 22:09:04 UTC]
[22:09:04] + Working ...
thekraken: The Kraken 0.6 (compiled Mon Feb 20 21:12:14 EST 2012 by Core32@Core32-H8QG6)
thekraken: Processor affinity wrapper for Folding@Home
thekraken: The Kraken comes with ABSOLUTELY NO WARRANTY; licensed under GPLv2
thekraken: PID: 7271
thekraken: Logging to thekraken.log
[22:09:04] CoreStatus = 74 (116)
[22:09:04] The core could not find the work files specified. Removing from queue
[22:09:04] Deleting current work unit & continuing...

The work folder is there but when I tried to cd into it I received "Permission denied". So I ran from within /fah, "sudo -s", entered my password, as was able to cd to /work. Then I reran the fah start command.
That seems to have worked as it found the in progress WU this time and is now folding again at the spot it left off.
Why would the /work folder require I be root user to enter and how would fah have been able to use the work folder before to get there?
Seems I need to give my "user" permisisions to the entire fah folder again.
Also, even on my 6128 system, I can't get fah to restart on power up.
Where do I need to add the start command script line/file?
I thought I had followed most of the directions but I never followed up on this issue since I only power cycle when I change the OC.

 

[tear]

Why would the /work folder require I be root user to enter and how would fah have been able to use the work folder before to get there?

There are two likely possibilities:
1) You ran the client as root when work/ directory did not exist
2) You created copy of the client as root without preserving ownership ('cp -a' is the way to go)

Also, even on my 6128 system, I can't get fah to restart on power up.

I'd recommend against doing so. Depending on the nature of a crash,
queue/work files may be in a state not allowing successful resume and
subsequent work or WU loss but then again, outages in my area are very
rare...

I keep periodic backups and shall power outage occur I usually restore from
a backup.

 

[Core32]

Number 1 seems likely as after I created the clone I went into the new HDD and deleted all the stuff related to the WU that was running on the source HDD including the work/ folder.
I guess I need to do a -oneunit on this WU, then be sure when I restart the client to be user, not root?

 

[tear]

You'll need to take it further -- sudo chown -R non-root-username fahdirectory
(you get the idea) after you finish the unit.

You can examine state of affairs with 'ls -l' (will list contents of current directory including owner).

 

[Core32]

Got it. Forgot about file ownership chage. Guess I was thinking I would just delete the root owned items, restart a terminal as user, then restart the client.
I need to practice my commands more often and stop copying and pasting from the instruction threads!
Thanks.