Major disaster on file server

B

balanga

I had a major disaster with my file server. a ThinkCentre M73 today when it became invisible.

At first I thought the hard disk had failed but eventually it looked like the NIC had stopped working but the hard disk was OK.

I have now connected the hard disk to my ThinkPad X1 Carbon via a USB enclosure and after reconfiguring numerous settings I'm back in business, but the situation isn't ideal.

How would I go about testing the ThinkCentre? Are there any diagnostics I could run to see if the NIC has failed? Any errors msgs to look out for during bootup?
 
balanga said:
How would I go about testing the ThinkCentre? Are there any diagnostics I could run to see if the NIC has failed? Any errors msgs to look out for during bootup?
Click to expand...
Anything interesting in the logs? Is this NIC a discrete board or built in? Try to replace with something else. Also, in such case it is always a good idea to log in from console and what are the messages and what is happening.
 
It's a built in NIC, but I tried using a USB NIC but that didn't work.

I did attach a TV monitor but didn't notice any error messages.

I'll try booting with a different disk and see what happens. At the moment my laptop is functioning as my file server, so I can investigate the ThinkCentre independently.
 
cracauer@ said:
What does USBing the disk have to do with the NIC failing?
Click to expand...

I just connected the disk via a USB enclosure to a different system to have a file server available.

I did try using a USB NIC with the original system to see if I could get a connection, but nothing appeared.
 
I've just tried out the computer on its own an it seems to work fine.

What could have caused it to disconnect and become inaccessible?

Maybe overheating..... Which would be a log worth checking? There may have been some error msgs written indicating that there was a problem prior to it hanging.
 
We have no idea. It could be the disk itself, but as you said, it seems to work now. It could be the computer, like a bad connection, or a faulty component. It could have been caused by a memory error, and was just a simple crash that was cured by the next reboot. Given that you are not telling us any details, nor you seem to be doing disciplined debugging, it is not easy to tell.
 
You must log in or register to reply here.
Back
Top