Hello,

 

I Can't acess to my interface anymore.

I joined the syslog that i've got using command line.

 

thanks for your help

syslog.txt

I've seen that config folder has desapeared on my usb stick.

- Are you able to find my disk's config back? I mean the one which is the parity drive and so on ?

- Am I able to get my VM back ?

 

What should I do ? Make a new usb stick with a fresh install ?

 

Thanks

All,

 

I've found an old nas diagnostic zip files.

I have been able to extract the backuped config directory directly to usb stick.

I am able to start the array, almost like before.

I mean that everything works fine, but I've lost my directories from the day I downloaded the nas diag files to present day.

 

How can I find my directories back please?

 

Thanks

nas-diagnostics-20170601-1327.zip

up.. please help me ! I'm so afraid to get lost my fies

16 hours ago, neuk34 said:

I mean that everything works fine, but I've lost my directories from the day I downloaded the nas diag files to present day.

 

Describe in more detail what you lost.  (I have the feeling that English is not your first language.)  Are there hard drives missing?  Are you missing shares?  If so, what are their names.  Are you just missing files?

 

It would also help if you would describe how you recovered the config directory and what files you copied onto your flash drive. 

 

EDIT: Since June 1, 2017, have you made any physical changes in the hard drives?  Replacing a drive?  Adding a new drive?  Are you still running version 6.3.5.

 

Post up a current diagnostics file. 

Edited September 27, 20178 yr by Frank1940

Frank,

 

First, sorry for my poor english, i'll try my best.

I'm running 6.3.5.

I didn't make any physical change, I didn't replace or add any drive.

Nothing is missing : my drives and my shares are still there.

I've just lost directories and files.

 

Here the story :

Yesterday, I was not able to access  my user interface anymore.

So, I took my flash drive, and I plugged it to my laptop.

I noticed that /config directory of the flash drive was missing. (That's why user interface was not reachable anymore).

 

I had an old backup (nas diagnostic file (*.zip) that I downloaded 06/2017 from my unraid).

So, I decided to extract the config directory from this old backup directly to my flash drive.

 

My unraid rebooted, and my user interface was reachable.

But it took the old config, and all new directories and new files created after 06/2017 are missing.

 

What Can I do ? I think about to create a fresh flash drive, building a new parity drive, hoping that it will be enough to get my files and directories back.

What can I do ?

 

Thanks

I can't think of any reason that they should have disappeared.  Perhaps, someone else may have a possible reason. 

 

Please post up a current diagnostics file in your next post so the the experts can have a look at it.      "Tools"   >>>    "Diagnostics"

It's too late !! my old config disappeared..

And except you, nobody tries to help me..

 

I make a fresh install, hoping i will be able to find my repositories back..

 

15 minutes ago, neuk34 said:

nobody tries to help me..

 

I suspect because like me they are not really understanding the issue.

 

5 hours ago, neuk34 said:

Nothing is missing : my drives and my shares are still there.

I've just lost directories and files.

 

Restoring an old config, as long as the assignments were all correct, won't delete any data.

 

Best way forward would probably be to format your flash drive, re-assign all disks and start over, your data won't be touched.

I made a fresh install, put the right disk assigment, but I have not been able to recover my files.

Copying old /config directory to the flash drive acts like a snapshot, it has deleted all datas created from this last snapshot.

I've lost 3 month data.

5 minutes ago, neuk34 said:

Copying old /config directory to the flash drive acts like a snapshot, it has deleted all datas created from this last snapshot.

 

That's just impossible, it's not how unRAID works, maybe you forgot to assign your cache or something.

@johnnie.black his signature indicated that he does have 3 ssd's assigned as cache drive. 

 

@neuk34 ,  Johnnie.black is correct.  the configuration file is not a roll back UNLESS you have added or changed out one or more of your hard drives.  Even in that case, you data should still be there!  It is a matter of locating it.  Please post up the current diagnostics file as I requested earlier! 

@johnnie.black I've got 2 ssd drive, one for my VM, another for sabnzbd cache. I don't use cache drive for unraid.

@Frank1940 You right, I think the data is here, just a problem of location. You'll find the syslog and nas diag attached.

 

I really appreciate your help.

 

thanks

nas-syslog-20170927-1304.zip

nas-diagnostics-20170927-1319.zip

Edited September 27, 20178 yr by neuk34

I had a red bullet on my disk 8 from 06/2017, but I left it like that because it was working. (the common mistake that the supermicro card can meet)

I think that all my new data is on the parity drive.

But I desactivated it when I did my new config.

I think I could recover everything if my parity drive was re-assigned, and if I launch a data rebuild on disk 8.Do you think it's possible?

 

Thanks

 

Edited September 27, 20178 yr by neuk34

Wait before you do anything.  You really need some expert advice here.  If I understand you correctly, you have been running with a data disk re-balled for the past three months! 

 

I was looking through both your diagnostics file and started to look at the smart reports on your drives and saw that there were nine hard drives, two ssd's and one flash drive listed.   But the syslog is only showing that you are mounting eight of them.   And you say that you never mounted the parity drive, that could explain that discrepancy.   But you should still have one drive red balled.  Do you have that drive red-balled?  

 

Next question, have you written anything to the array since you have been running without that parity drive assigned? 

Quote

you have been running with a data disk re-balled for the past three months! 

 

Yes, the disk 8 was red-bulled since 06/2017. All other disks were green.

Quote

Do you have that drive red-balled? 

No, not anymore. All drive went green when I extracted old backup /config directly to flash drive. But I lost all repository / file created since 06/2017.

 

Quote

But the syslog is only showing that you are mounting eight of them.

Yes, i unassigned the parity drive when I made the fresh install. it is presently into Unassigned Devices.

 

Quote

have you written anything to the array since you have been running without that parity drive assigned? 

No, I didn't write anything.

 

Thank you so much !

Edited September 27, 20178 yr by neuk34

10 minutes ago, neuk34 said:

I had a red bullet on my disk 8

 

You should have mentioned this in the first post.

 

11 minutes ago, neuk34 said:

from 06/2017, but I left it like that because it was working.

 

And should have fixed this ASAP, not let the array work degraded for months, disk8 is full of pending sectors and needs to be replaced.

 

Depending on if anything changed or not in the array you may still be able to recover the missing data, follow these steps carefully, any doubt ask before doing it:

 

-Tools -> New Config -> Retain current configuration: All -> Apply
-assign any missing disks, check that all disks are assigned, including parity and old disk8
-check both "parity is already valid" and "maintenance mode" before starting the array
-start the array
-stop array, unassign disk8
-start array, check emulated disk mounts and contents look correct, i.e., missing data is there

 

If it works copy the data from the emulated disk or better yet get a new disk to replace old disk8.

 

PS: You need to improve disk cooling, all your disk have reached between 55 and 60C in the past, that's way to hot, ideally they should never go above 40C, 45 tops.

Quote

Tools -> New Config -> Retain current configuration: All -> Apply

 

retain current configuration is grey. cannot change anything. it's just written None.

 

 

Isn't the "array must be stopped" below a clue?

sorry.. i'm following the procedure.

Quote

-Tools -> New Config -> Retain current configuration: All -> Apply
-assign any missing disks, check that all disks are assigned, including parity and old disk8
-check both "parity is already valid" and "maintenance mode" before starting the array
-start the array
-stop array, unassign disk8

 

OK, done. see picture.

Quote

start array, check emulated disk mounts and contents look correct, i.e., missing data is there

 

content is worst. it miss more files than before.

 

Quote

if it works copy the data from the emulated disk or better yet get a new disk to replace old disk8.

 

It didn't work. Content is not emulated.

 

What should I do now?

 

Thank for your help.

Stop the array, start the array in maintenance mode (you need to check that box before starting).

 

Then on the console or SSH type:

 

xfs_repair -v /dev/md8

 

Post the output

 

Now type:

 

xfs_repair -vL /dev/md8