Not if fsck wont fix it. ;( But..will give it a shot
On 10/28/06, Derek Ragona <[EMAIL PROTECTED]> wrote:
You should be able to remove the bad drive leaving the good one in use.
-Derek
At 03:18 PM 10/28/2006, Jeff Mohler wrote:
Appears the issue is in the IBM servers RAID.
I
You should be able to remove the bad drive leaving the good one in use.
-Derek
At 03:18 PM 10/28/2006, Jeff Mohler wrote:
Appears the issue is in the IBM servers RAID.
Its a RAID1, and the mirror raid is totally hosed according to the
machine bios, and that hung up the primary side of
Appears the issue is in the IBM servers RAID.
Its a RAID1, and the mirror raid is totally hosed according to the
machine bios, and that hung up the primary side of the mirror when the
backup side went tango uniform.
On 10/27/06, Derek Ragona <[EMAIL PROTECTED]> wrote:
reboot single user, cd
reboot single user, cd /var/log and delete anything you can there. Then
try fsck.
-Derek
At 07:26 PM 10/27/2006, Jeff Mohler wrote:
So..last night im workin away, and then the machine gets slow, then
stops responding to anything.
I can ping it, but no telnet, www...anything. Hung h
So..last night im workin away, and then the machine gets slow, then
stops responding to anything.
I can ping it, but no telnet, www...anything. Hung hard. Last thing
I saw in a make buildworld was a 'cant write to filesystem' error..or
something like that but not a 'no room on device' error.
H
