LOL - good point. I think the damage was done by rapid dismount since
only systems that were activly in use at the time seem effected but it
is certainly worth the check.
On Mon, Jul 26, 2010 at 6:07 PM, Stephen <
cryptworks@gmail.com> wrote:
> It might also be worth getting the HDD manufacturers diagnostics and
> see if the disk is 100% also.
>
> On Mon, Jul 26, 2010 at 3:20 PM, Technomage <technomage.hawke@gmail.com> wrote:
>> I would use a live cd to check that one. you may have a severe enough file
>> corruption that using even single user mode might encounter problems. after
>> you check and certify the system disc has no problems, I would start testing
>> the networking hardware using the same disc. if it runs into problems, you
>> may have to replace hardware (if a surge made it through the protector, then
>> its likely your supply is flaky and the MB may have also taken the hit ).
>>
>> I have had to deal with this scenario more often than once. When a Power
>> strip surge protector finally buys it, it tends to leave your system exposed
>> for a brief period of time during the surge that blew to the protector. This
>> can have unanticipated effects on your hardware.
>>
>> anyway, I hope its nothing more serious that an easily corrected filesystem.
>>
>>
>>
>> On 7/26/10 11:38 AM, Bryan O'Neal wrote:
>>>
>>> So I run a fedora based server in my house. Recently I had the local
>>> surge suppressor tip out and drop all my boxes. The server had wired
>>> problems ever since. I can not log into a local X session (it hangs
>>> trying to load a desktop) and I can not read files from the samba
>>> server (I can see the files but not access them). I can login over ssh
>>> and all the files are there. So I was thinking I would just run a
>>> quick fsck and see what turned up before doing a tar and export of the
>>> files and a wipe and rebuild of the server.
>>> However this is where I ran into trouble. i can get into single user
>>> mode no problem but I can not unmount the main partition? umount
>>> /de/VolGroup00/LogVol100 -f just returns - I am way to busy. But the
>>> only things I can see running are disk and council related related
>>> processes. lsof returns the stranded stuff /, /sbin/, /dev/counsole/,
>>> proc[#]/exe/, etc.
>>>
>>> But I do see lib64/ld-2.9.so, /lib64/libc-2.9.so,
>>> /usr/lib64/libplybootsplash.so.2.0.0, and
>>> /usr/lib64/libpng12.s0.0.37.0 as well - not sure why those files are
>>> open in single user mode - but in any case I can not umount the volume
>>> with -f so I can fschk.ext3 it Suggestions?
>>>
>>> And yes the drive is encrypted using the red hat / fedora standard
>>> encryption. This is why I used fedora at the time and not cent OS for
>>> this server, it made drive encryption very easy and reliable.
>>> ---------------------------------------------------
>>> PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
>>> To subscribe, unsubscribe, or to change your mail settings:
>>> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
>>>
>>>
>>
>> ---------------------------------------------------
>> PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
>> To subscribe, unsubscribe, or to change your mail settings:
>> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
>>
>
>
>
> --
> A mouse trap, placed on top of your alarm clock, will prevent you from
> rolling over and going back to sleep after you hit the snooze button.
>
> Stephen
> ---------------------------------------------------
> PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
> To subscribe, unsubscribe, or to change your mail settings:
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
>
---------------------------------------------------
PLUG-discuss mailing list -
PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change your mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
(text/plain)