SCSI Hardware problem?
Subhro
subhro.kar at gmail.com
Thu Jan 6 19:07:36 PST 2005
> -----Original Message-----
> From: owner-freebsd-questions at freebsd.org [mailto:owner-freebsd-
> questions at freebsd.org] On Behalf Of Tom Vilot
> Sent: Friday, January 07, 2005 3:48
> To: FreeBSD Questions
> Subject: SCSI Hardware problem?
>
> 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
Is the SCSI bus terminated properly. Changing LUNs help?
>
> -----------------------------------
>
> I'm guessing I will want to copy this entire drive over to another one.
> What's the best way .... dd?
dd works only and only if the source drive and the target drive are *exact*
clones of each other, which is not something seen very frequently. Why don't
you use dump?
>
> 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?
Ctrl+D
> Thanks in advance.
Welcome :-)
Regards
S.
Indian Institute of Information Technology
Subhro Sankha Kar
Block AQ-13/1, Sector V
Salt Lake City
PIN 700091
India
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3677 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20050107/0672ef6f/smime.bin
More information about the freebsd-questions
mailing list