Unmountable disk present

[JorgeB]

Memtest not finding an error does not mean RAM is OK, if it finds some then it's not OK for sure, if it's not RAM there's likely some other hardware issue, unless these are old errors, reset the pool stats, run a scrub and keep monitoring, if more corruption errors are detected there's still a problem, and likely it's bad RAM.

[folic86]

Thanks for the assistance Jorge.

 

It found 0 errors when I ran it when this issue began.

 

Does this info below help at all?

 

How would RAM effect the log file issue?

 

 

Also @JorgeB now I reset the stats and it says 0, do I just reboot and kill the corrupt log file and start again? What is your suggestion?

Edited January 20, 2023 by folic86
Additional info

[JorgeB]

16 minutes ago, folic86 said:

Does this info below help at all?

I already saw that in the diags.

 

17 minutes ago, folic86 said:

and kill the corrupt log file

Not sure what you mean by this, run a scrub and use the server normally, if more errors are detected there's still a problem.

 

[folic86]

Just now, JorgeB said:

I already saw that in the diags.

 

Not sure what you mean by this, run a scrub and use the server normally, if more errors are detected there's still a problem.

 

I still have an unmountable Disk 9 though!

[JorgeB]

That's the same as before, check filesystem then if the emulated disk looks OK you can rebuild, SATA cable should be replaced before doing it though.

[folic86]

2 minutes ago, JorgeB said:

That's the same as before, check filesystem then if the emulated disk looks OK you can rebuild, SATA cable should be replaced before doing it though.

Ok. Wil try, thanks Jorge!

[trurl]

6 hours ago, folic86 said:

How would RAM effect...?

Bad RAM can affect anything.

 

You shouldn't even attempt to run any computer unless RAM is working perfectly. Everything goes through memory, the OS and other executable code, your data, everything. The CPU can't even do anything with anything until it is loaded into RAM.

[folic86]

On 1/20/2023 at 4:16 PM, JorgeB said:

That's the same as before, check filesystem then if the emulated disk looks OK you can rebuild, SATA cable should be replaced before doing it though.

So I did this, and it repaired the errors. I then had a lost+found folder which is fine but I embarked on a data rebuild and it has come back in an error state and has stopped the rebuild. 

 

I am so puzzled. Can you advise? wopr-diagnostics-20230124-1647.zip

[JorgeB]

Looks like a power/connection problem, SMART looks fine, there are some UDMA CRC errors so it could just be a bad SATA cable.