PaDadof2 Posted January 9, 2019 Share Posted January 9, 2019 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 Quote Link to comment
JorgeB Posted January 9, 2019 Share Posted January 9, 2019 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. Quote Link to comment
PaDadof2 Posted January 10, 2019 Author Share Posted January 10, 2019 @johnnie.black How do I get rid of those, so my syslog isn't useless. Quote Link to comment
JorgeB Posted January 10, 2019 Share Posted January 10, 2019 Look for a bios update. Quote Link to comment
PaDadof2 Posted January 12, 2019 Author Share Posted January 12, 2019 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 Quote Link to comment
JorgeB Posted January 12, 2019 Share Posted January 12, 2019 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 Quote Link to comment
PaDadof2 Posted January 12, 2019 Author Share Posted January 12, 2019 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! Quote Link to comment
JorgeB Posted January 12, 2019 Share Posted January 12, 2019 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. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.