do you know why on a linux server.
1. We turn the power off.
2. we unplug a hard drive, and then plug it back in and
it stops working when you turn it back on.

it's an ibm scsi controller card that's being used.

This has happened on 2 machines.

Any clues?

"Krusty" <danparker276@yahoo.com> wrote in message
news:f4a9a3fc.0312081700.563b847e@posting.google.c om...
> do you know why on a linux server.
> 1. We turn the power off.
> 2. we unplug a hard drive, and then plug it back in and
> it stops working when you turn it back on.
>
> it's an ibm scsi controller card that's being used.
>
> This has happened on 2 machines.

It's likely one of two things:

1: Your MBR was on that drive on the SCSI chain.
2: That drive had a lower number than the drive with your "/" or other
active partitions, and the re-ordering of your drives is confusing the drive
numbering and disk mounting scheme.

Can you post a copy of "/etc/fstab" and the contents of your
"/etc/lilo.conf" or "/etc/grub.conf"? And describe in more detail how it
"stops working"?

"Krusty" <danparker276@yahoo.com> wrote in message
news:f4a9a3fc.0312081700.563b847e@posting.google.c om...
> do you know why on a linux server.
> 1. We turn the power off.
> 2. we unplug a hard drive, and then plug it back in and
> it stops working when you turn it back on.


Is it because you changed the ID on the scsi drive ?

Is it because you plugged into a different scsi card ? or a different
interface on the same card ?


I can usually unplug a drive and reinstall it without disaster, but maybe
you treat it like a frisbee.
or something.

It's the same drive. It wasn't moved around at all. Just unplugged
from the scsi controller and then plugged back in.

"Leon." <leon@noteon.net> wrote in message news:<3fd57a53$1@news.rivernet.com.au>...
> "Krusty" <danparker276@yahoo.com> wrote in message
> news:f4a9a3fc.0312081700.563b847e@posting.google.c om...
> > do you know why on a linux server.
> > 1. We turn the power off.
> > 2. we unplug a hard drive, and then plug it back in and
> > it stops working when you turn it back on.
>
>
> Is it because you changed the ID on the scsi drive ?
>
> Is it because you plugged into a different scsi card ? or a different
> interface on the same card ?
>
>
> I can usually unplug a drive and reinstall it without disaster, but maybe
> you treat it like a frisbee.
> or something.

And by stop working, it doesn't boot up. It gives an error that it
can't find a hard drive.
"Leon." <leon@noteon.net> wrote in message news:<3fd57a53$1@news.rivernet.com.au>...
> "Krusty" <danparker276@yahoo.com> wrote in message
> news:f4a9a3fc.0312081700.563b847e@posting.google.c om...
> > do you know why on a linux server.
> > 1. We turn the power off.
> > 2. we unplug a hard drive, and then plug it back in and
> > it stops working when you turn it back on.
>
>
> Is it because you changed the ID on the scsi drive ?
>
> Is it because you plugged into a different scsi card ? or a different
> interface on the same card ?
>
>
> I can usually unplug a drive and reinstall it without disaster, but maybe
> you treat it like a frisbee.
> or something.

Krusty <danparker276@yahoo.com> wrote:
> And by stop working, it doesn't boot up. It gives an error that it

Please don't top post.

> can't find a hard drive.

Please don't post vaguenesses.

It doesn't say that at all. Be precise. It speaks of not being able to
mount the root file system ("VFS"). It finds "drives" (you mean
"disks") just fine.

Now you play ball and tell us what it DOES say. You tell us

1) what disks the kernel detects, under what device names
2) what it is set to have as root device
3) what you do have in the place where the kernel expects the root
device.

And you cpy it down verbatim, making the effort that you haven't
bothered to make so far.

And if you attempt to top post again, you can continue playing guessing
games with yoruself.

Peter

"Krusty" <danparker276@yahoo.com> wrote
> do you know why on a linux server.
> 1. We turn the power off.
> 2. we unplug a hard drive, and then plug it back in and
> it stops working when you turn it back on.
>
> it's an ibm scsi controller card that's being used.
Clutching at straws here...
a) you know that turning off the power via the front panel switch doesn't
really remove dc power from the motherboard on newer computers,
right? They often put a red idiot light on the mb to remind you of that.
b) if the scsi termination is 'iffy' then touching the hard disk case to the
computer case can push it over the line to 'too bad to run' until you
remove the hd case ground again.
c) don't assume your little Berg jumpers on the hard disk aren't broken.

Ok, sorry
When the power was turned off, the plug was taken out as well. Then
the drive was removed and put back in.
When turning on again, it goes through it's boot up and says,
Intel Boot Agent
PXE-E61 Media Test failure Check Cable,
PXE-M0F Exiting Intel PXE ROM
Operating System not found

When trying to reformat the drive and boot of CD rom it doesn't find
the hard drive.

Adaptec has some SCSI utilities options too. I'm not that familiar
with SCSI drives, but all that happened is that it was unplugged.



ptb@oboe.it.uc3m.es (P.T. Breuer) wrote in message news:<3d45rb.vui.ln@news.it.uc3m.es>...
> Krusty <danparker276@yahoo.com> wrote:
> > And by stop working, it doesn't boot up. It gives an error that it
>
> Please don't top post.
>
> > can't find a hard drive.
>
> Please don't post vaguenesses.
>
> It doesn't say that at all. Be precise. It speaks of not being able to
> mount the root file system ("VFS"). It finds "drives" (you mean
> "disks") just fine.
>
> Now you play ball and tell us what it DOES say. You tell us
>
> 1) what disks the kernel detects, under what device names
> 2) what it is set to have as root device
> 3) what you do have in the place where the kernel expects the root
> device.
>
> And you cpy it down verbatim, making the effort that you haven't
> bothered to make so far.
>
> And if you attempt to top post again, you can continue playing guessing
> games with yoruself.
>
> Peter

sorry it was just the case that was messed up.

ptb@oboe.it.uc3m.es (P.T. Breuer) wrote in message news:<3d45rb.vui.ln@news.it.uc3m.es>...
> Krusty <danparker276@yahoo.com> wrote:
> > And by stop working, it doesn't boot up. It gives an error that it
>
> Please don't top post.
>
> > can't find a hard drive.
>
> Please don't post vaguenesses.
>
> It doesn't say that at all. Be precise. It speaks of not being able to
> mount the root file system ("VFS"). It finds "drives" (you mean
> "disks") just fine.
>
> Now you play ball and tell us what it DOES say. You tell us
>
> 1) what disks the kernel detects, under what device names
> 2) what it is set to have as root device
> 3) what you do have in the place where the kernel expects the root
> device.
>
> And you cpy it down verbatim, making the effort that you haven't
> bothered to make so far.
>
> And if you attempt to top post again, you can continue playing guessing
> games with yoruself.
>
> Peter

Krusty <danparker276@yahoo.com> wrote:
> sorry it was just the case that was messed up.

Please don't top post! I have no idea what you are replying to.
Let's try fixing your post.

>
> ptb@oboe.it.uc3m.es (P.T. Breuer) wrote in message news:<3d45rb.vui.ln@news.it.uc3m.es>...
> > Krusty <danparker276@yahoo.com> wrote:
> > > And by stop working, it doesn't boot up. It gives an error that it
> >
> > Please don't top post.


Does your comment go here?

> sorry it was just the case that was messed up.

Nope.

> >
> > > can't find a hard drive.
> >
> > Please don't post vaguenesses.

Maybe here?

> sorry it was just the case that was messed up.

What's a "case"? I didn't say anything about a case! Not here.

> >
> > It doesn't say that at all. Be precise. It speaks of not being able to
> > mount the root file system ("VFS"). It finds "drives" (you mean
> > "disks") just fine.
> >
> > Now you play ball and tell us what it DOES say. You tell us
> >
> > 1) what disks the kernel detects, under what device names
> > 2) what it is set to have as root device
> > 3) what you do have in the place where the kernel expects the root
> > device.

Maybe here?

> sorry it was just the case that was messed up.


No - that's not a reply to anything I asked for.

> > And you cpy it down verbatim, making the effort that you haven't
> > bothered to make so far.

> sorry it was just the case that was messed up.


Well, maybe it goes here? Maybe you mean upper or lower case, and you
are referring to your non-copying of kernel messages?

If so, you are wrong. The message was way out from anything the kernel
says, and you have to copy it, not send me vague missives that abstract
wildly from what you think may be what you did, and get that wrong too.


> > And if you attempt to top post again, you can continue playing guessing
> > games with yoruself.

Maybe it goes here?

> sorry it was just the case that was messed up.

Ah, I get it! You're the "case"! You have trouble expressing yourself
coherently. You are a patient in a mental asylum, no?


Peter