Jump to content
Sign in to follow this  
PaDadof2

unclean shutdown, now cache drive unmountable

8 posts in this topic Last Reply

Recommended Posts

I noticed my 1 GB SSD cache drive was showing "Unmountable: No file system". I tried to use this guide I'm not sure I'm doing it right and I'm concerned I may screw something up.  Can someone ELI5 how to do this?  Here is my setup  I've also attached the diagnostics and the error log from SSD.  Thank you in advance.

 

tower-diagnostics-20190108-1935.zip

unraid ssd error.PNG

Share this post


Link to post
6 hours ago, PaDadof2 said:

I tried to use this guide

That's your best bet.

 

P.S. syslog is spammed with errors like these:

 

Jan  6 04:40:01 Tower kernel: ACPI Error: AE_AML_BUFFER_LIMIT, Evaluating _PMM (20180531/power_meter-338)
Jan  6 04:40:02 Tower kernel: ACPI Error: SMBus/IPMI/GenericSerialBus write requires Buffer of length 66, found length 32 (20180531/exfield-393)
Jan  6 04:40:02 Tower kernel: ACPI Error: Method parse/execution failed \_SB.PMI0._PMM, AE_AML_BUFFER_LIMIT (20180531/psparse-516)
Jan  6 04:40:02 Tower kernel: ACPI Error: AE_AML_BUFFER_LIMIT, Evaluating _PMM (20180531/power_meter-338)
Jan  6 04:40:03 Tower kernel: ACPI Error: SMBus/IPMI/GenericSerialBus write requires Buffer of length 66, found length 32 (20180531/exfield-393)
Jan  6 04:40:03 Tower kernel: ACPI Error: Method parse/execution failed \_SB.PMI0._PMM, AE_AML_BUFFER_LIMIT (20180531/psparse-516)
Jan  6 04:40:03 Tower kernel: ACPI Error: AE_AML_BUFFER_LIMIT, Evaluating _PMM (20180531/power_meter-338)
Jan  6 04:40:04 Tower kernel: ACPI Error: SMBus/IPMI/GenericSerialBus write requires Buffer of length 66, found length 32 (20180531/exfield-393)
Jan  6 04:40:04 Tower kernel: ACPI Error: Method parse/execution failed \_SB.PMI0._PMM, AE_AML_BUFFER_LIMIT (20180531/psparse-516)

 

And so useless.

Share this post


Link to post

thanks, Johnnie.black.  

 

I've tried the guide, but I'm not getting anywhere.  

 

can anyone help me with this guide and walk me through what each item should read

 

mkdir /x  what should x be?

 

mount -o recovery,ro /dev/sdf1 /x     I used sdf1, but again not sure what x should be

 

thanks a lot

 

 

 

 

Share this post


Link to post
2 minutes ago, PaDadof2 said:

mkdir /x  what should x be?

it can just be x or any other name you want, it's just for a temporary mount point

Share this post


Link to post

Thank you for the quick response, I just tried that and got this error

mount: /x: can't read superblock on /dev/sdf1.

 

Do I need to have my array in maintenance mode?  

 

I really appreciate the help!

Share this post


Link to post

That means the superblock is damaged, try the mount -o recovery option and/or btrfs restore with a backup superblock, though a damaged superblock implies severe corruption, so recovery not so likely.

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this