Ok so I deleted some files by accident and used the info on here to get them back. I can see the Lost+Found Folder when I navigate to it through windows, but I get an error saying I can't open the folder.

 

If I use the Web based interface for Unraid I can see the recovered files and download them.

 

Just want to know how I can view them in windows so i can delete the ones I don't want and move the ones I do to the right folder.

 

Thanks.

Ok so I deleted some files by accident and used the info on here to get them back. I can see the Lost+Found Folder when I navigate to it through windows, but I get an error saying I can't open the folder.

 

If I use the Web based interface for Unraid I can see the recovered files and download them.

 

Just want to know how I can view them in windows so i can delete the ones I don't want and move the ones I do to the right folder.

This is probably just a permissions issue.  This can be corrected by doing one of the following

• From a telnet/consoled session run the command
  newperms "/mnt/user/lost+found"
  This is by the fastest option.  I expect that you used a telnet/console session to get the lost+found folder in the first place?
  
• Run the new permissions option from the GUI under the tools tab.  This can take a while to complete as it gores through every file/folder on the system.  You need to leave the browser window open while it is running
  

Thanks I'll try that.

 

I have another questions I ran the reiser recovery on another disk just now and it's taking longer and is on it's 4th pass. I don't think it did that many on the disk I was originally asking about.

 

Can I re-run the recovery program again on a disk I already did it on? I mean what is the procedure, or has it already found all it's going to?

Can I re-run the recovery program again on a disk I already did it on? I mean what is the procedure, or has it already found all it's going to?

You can run it again, but unless you change the parameter options you will get the same results.  If you want to run reiserfsck again as a confidence check I would suggest only using the --check option this time.

Ah ok. thanks. If i would get the same results then I won't do it.

 

It's just weird. I deleted some stuff and then wanted it back and haven't written to the drive since, but I'm missing what I'm looking for, but other stuff I deleted LIKE aged ago showed up.

 

Mainly stuff in multiple sub folders, but if would find those as well, right?

Ah ok. thanks. If i would get the same results then I won't do it.

 

It's just weird. I deleted some stuff and then wanted it back and haven't written to the drive since, but I'm missing what I'm looking for, but other stuff I deleted LIKE aged ago showed up.

 

Mainly stuff in multiple sub folders, but if would find those as well, right?

It is unusual to get back deleted items unless you used the --scan-whole-partition option, although I guess it could happen if the deletes did not complete properly because of file system corruption already present. .  When using --scan-whole-partition whether you get back deleted items can depend on whether the parts of the disk that previously contained the files gets re-used for new files and whether reiserfsck can locate enough of the pre-delete control structures to recognise a file was present.  It cam be a bit unpredictable what gets recovered in such cases.

I used "reiserfsck --rebuild-tree -S /dev/md1" how does this differ from the Scan whole partition?

I still want the answer to what I asked above, but once I got permission to open the folder in Windows I found what I was looking for, Thanks for the help.

I used "reiserfsck --rebuild-tree -S /dev/md1" how does this differ from the Scan whole partition?

I believe that the --rebuild-tree option uses the bit masks of used sectors to work out what to scan which means it does not need to read every sector on the partition.  When you also use the --scan-whole-partition option then every sector in the partition what looks like disk control structures.  This means it takes even longer and can find spurious data, but it can recover from worse corruption that simply using --rebuild-tree. 

Ok got it. Thanks.