SOLVED Stopped at kbdmux_init+0x277

[Fig Newton]

Hi all,

I got an email this morning from my NAS and it said

"server1.local kernel log messages:
> bad block 1358701947, ino 6
> pid 21 (softdepflush), uid 0 inumber 6 on /data: bad block"

I got home tonight and couldn't access any of my files. I tried to log into the GUI and nothing.
(I EVIDENTLY NEED TO HOST THESE PICTURES AGAIN. I APOLOGIZE.
Here is a screen shot before I shut it down. Click here
Here is the picture when it booted back up. Click here

I am just not sure what to try first.

FreeNAS 9.2? I think.
My main pool is encrypted
X10SLM-f
i3
16 GB Corsair ECC Ram
Freenas
If you need or want anymore info just let me know.

Yes I am a noob. Yes I have a backup of the important things BUT there are some pictures that were recently put on that I would love to keep. Thank you.

Joe

 

[SweetAndLow]

Your USB stick died. Replace it and upload your configuration file. Everything will be back to normal.

 

[Fig Newton]

That's good news.

My machine has run flawlessly for so many years, I will have to read up on how to do that again.

Thank you.

 

[Fig Newton]

Everything went well. This little fella is back up and running. Thank you for the help.


UPDATE 8/26: Bad power supply fan may have started this issue. When my system went down on Saturday I put my hand on the PSU and it was warmer than normal. I have finally gotten around to checking everything today and noticed that the fan was not turning on. Luckily I didn't leave the system on after I got it back up and running.

 

[SweetAndLow]

Great! Thanks for following up

Sent from my Nexus 5X using Tapatalk

 

[Fig Newton]

I hate to jinx it.......

Last UPDATE 1/25

Ended up quitting on me again. Everything was backed up so I was not worried about my data left on there.

I could start the system but it would just stop and give me a "no bootable media found message". I could power off the machine and it would boot fine for another 40-50 hours, then give me the same message.

Just happened to remember something about memory modules working themselves out of the socket. I have no idea if it was true but I was at my wits end with this set of hardware. Pulled the modules, reinstalled them and ran memtest. Everything came back good. So I loaded Kali on there and beat the crap out of the processor for awhile. The machine stayed on the entire time (about 3.5 weeks) with no problem.

I decided to start from scratch and load Freenas 9.10. I reloaded all of my files and media. Been working great ever since (3 or so weeks).

Anywho, I hope this helps someone. I still think the crappy power supply started all of this, and I will probably never know if it was a bad connection with the RAM.

If anyone has any suggestions for next time, just let me know. You won't hurt my feelings. :)