Re: SCSI Hardware problem?
From: Jorn Argelo (jorn_at_wcborstel.nl)
Date: 01/06/05
- Previous message: Laurence Sanford: "Re: Remote upgrade possible?"
- In reply to: Tom Vilot: "SCSI Hardware problem?"
- Next in thread: Glenn Dawson: "Re: SCSI Hardware problem?"
- Reply: Glenn Dawson: "Re: SCSI Hardware problem?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
To: Tom Vilot <tom@vilot.com>, FreeBSD Questions <questions@freebsd.org> Date: Thu, 6 Jan 2005 23:30:34 +0100
On Thu, 06 Jan 2005 15:18:04 -0700, Tom Vilot wrote
> This looks to me like I've got a hardware problem. SCSI drive 0:4:0 -
> - or is this perhaps something else?
>
> I had to manually type this in ... :) copying it off the screen
> since I don't see this stuff in a log anywhere.
>
> FreeBSD 5.3 on a dual 450MHz Xeon with SCSI and IDE. GENERIC kernel.
>
> There was stuff above this, but it had scrolled off the screen and
> the console was locked up.
>
> da1 (scsi 4 on bus 0) is my boot drive.
>
> -----------------------------------
>
> <<<<<<<<<<<<<<<<<<<<Dump Card State Ends>>>>>>>>>>>>>>>>>>>>
>
> (da1:ahc1:0:4:0): SCB 0x3 - timed out
>
> sg[0] - Addr 0x2574b000
>
> (da1:ahc1:0:4:0): Queuing a BDR SCB
> (da1:ahc1:0:4:0): no longer in timeout, status = 24a
> ahc1: Timedout SCBs already complete. Interrupts may not be functioning.
> (da1:ahc1:0:4:0): WRITE(10). CDB: 2a, 0 0 47 49 23 0 0 4 0
> (da1:ahc1:0:4:0): CAM Status: SCSI Status Error
> (da1:ahc1:0:4:0): SCSI Status: Check Condition
> (da1:ahc1:0:4:0): UNIT ATTENTION asc:29,1
> (da1:ahc1:0:4:0): Power on occurred
> (da1:ahc1:0:4:0): Retrying Command (per sense Data)
> (da1:ahc1:0:4:0): WRITE(10). CDB: 2a, 0 0 47 49 23 0 0 4 0
> (da1:ahc1:0:4:0): CAM Status: SCSI Status Error
> (da1:ahc1:0:4:0): CAM Status: Check Condition
> (da1:ahc1:0:4:0): UNIT ATTENTION asc:29,1
> (da1:ahc1:0:4:0): Power on occurred
> (da1:ahc1:0:4:0): Retries Exhausted
> (da1:ahc1:0:4:0): lost device
> (da1:ahc1:0:4:0): invalidating pack
> panic: initiate_write_inodeblock_ufs2: already started
> Uptime: 3d12h50m3s
Make sure your SCSI controller is supported by the driver you're using. If it
is, it's probably a faulty disk.
>
> -----------------------------------
>
> I'm guessing I will want to copy this entire drive over to another
> one. What's the best way .... dd?
Doesn't matter too much AFAIK. As long as you can access the disk properly.
>
> Oh, one other question ...
>
> I'm used to runlevels on Linux. When I reset this machine, I'm
> presented with the prompt asking me for the default shell (/bin/sh).
> I hit enter, and I'm in sh where I can fsck the other drives and
> mount them. Cool. But ....once I have done that, how do I tell BSD
> to basically "continue" where it left off (i.e. run /etc/netstart
> sshd, httpd, psqld, zope, etc) without manually invoking each of
> those items?
I assume you boot in single user mode. I would just reboot the machine again
and boot normally (multi-user mode) after you're finished with fsck and stuff.
Cheers,
Jorn
> Thanks in advance.
>
> _______________________________________________
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"
- Previous message: Laurence Sanford: "Re: Remote upgrade possible?"
- In reply to: Tom Vilot: "SCSI Hardware problem?"
- Next in thread: Glenn Dawson: "Re: SCSI Hardware problem?"
- Reply: Glenn Dawson: "Re: SCSI Hardware problem?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
