I had a data drive quasi-flake out on me so I replaced it and let UnRAID do a rebuild. It still had missing files, so I ran reiserfsck, which told me to run a rebuild-tree. I reluctantly did so and it created the requisite lost+found directory. Now I'd like to get in there and see what it recovered but I can't. I've tried accessing the directory via the webGUI, but it responds with:

 

Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 72 bytes) in /usr/local/emhttp/plugins/dynamix/include/Helpers.php on line 52

 

I also tried just straight up mapping the drive to networked machine, but it just constantly loads the file list and eventually craps out or locks up.

 

I finally dropped down to the command line and navigated to the directory from the disk level. That at least returned something, but it's greek to me and I wouldn't know what to do with it from the command line anyway as I believe it to be a significant number of files. I'd upload it but even zipped it clocks in at 1.2MB, too large according to the rules of the forums.

 

Am I able to adjust the PHP of dynamix to up the allowed memory size to 1GB or something? Any other ideas as to how I could access and successfully manipulate these files? Many of them are precious family videos (or course it would be that disk, out of 10 possibilities)?

 

I should also note that using the browse function from the Array Devices table on the Main tab, I'm able to see names of SOME of the files in what I assume were their original locations. Many of the files I'm unable to access have yellow text instead of dark blue. The line item details also show which drives a file is using, but one of those drive numbers has an asterisk next to it with no additional detail. For example, files are show with a location of Disk 4,8*

 

What does the star and/or the yellowish orange text color that mean? What's my next step to recovering as much of this data as possible?

 

One final reminder: I still have the original drive from before the UnRAID rebuild, which is also from before the reiser rebuild-tree, if that would be useful.

 

Thanks, everyone! I want my baby girl's video files back.

 

Oh, I'm on 6.1.9.

I haven't been able to find a reference, but I believe that the yellow coloured text means that the file in question exists on more than one disk within the user share that you're browsing - in other words, it indicates duplicates. In your particular example you are browsing a sub-folder of your Camcorder_Archives user share and there are two instances of each of the files .DS_Store and ._.DS_Store within that sub-folder, one on Disk 4 and one on Disk 8. I don't know what the asterisk signifies but it might be worth checking to see if Disk 8 is excluded from that user share. The interactive help doesn't help in this case.

 

Your explanation is exactly right.

 

The asterisk means the same path/filename combination is found on multiple disks, aka duplicate file.

 

The GUI shows duplicated files in orange color.

 

The memory size error seems to come from /var/log running out of space.

 

Telnet into your system (or use console) and post the result of:

 

df -h /var/log

 

The memory size error seems to come from /var/log running out of space.

 

Telnet into your system (or use console) and post the result of:

 

df -h /var/log

 

Filesystem      Size  Used Avail Use% Mounted on

tmpfs          128M  2.0M  127M  2% /var/log

The memory size error seems to come from /var/log running out of space.

 

Telnet into your system (or use console) and post the result of:

 

df -h /var/log

Only time I've ever seen that error is from when PHP has run out of space (128M) allocated by default for each programs variables.

 

Sent from my LG-D852 using Tapatalk

 

 

My biggest fear is losing data, although I'm comforted a bit by knowing that orange text means it's a duplicate, opposed to a split file (and thus a file that's potentially missing half of its data). I just wish I could access that directory and see what's in there.

 

I'm running a deep scan right now using the Fix Common Problems plug-in. I intend to run a parity check afterwards, but I want to be sure that's the right move. Can you guys confirm whether I should be doing something else?