dmesg Analysis
I recently upgraded/reinstalled 4.7 RELEASE and apparently lost use of my SCSI tape backup system. The dmesg command indicates that FreeBSD found the controller and tape but I don't understand much more than that. Does anyone know where I might find some documentation which would explain output resulting from running dmesg? For instance, one of the lines reads: sa0 at adv0 bus 0 target 4 lun 0 ? Just looking for some direction. Thanks To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: dmesg Analysis
On Mon, Mar 24, 2003 at 09:08:31PM -0500, Bob Perry wrote: > I recently upgraded/reinstalled 4.7 RELEASE and apparently lost use of my > SCSI tape backup system. The dmesg command indicates that FreeBSD found the > controller and tape but I don't understand much more than that. > > Does anyone know where I might find some documentation which would explain > output resulting from running dmesg? For instance, one of the lines reads: > sa0 at adv0 bus 0 target 4 lun 0 > ? > Just looking for some direction. > > Thanks > I don't know of any docs that really explain reading a dmesg in detail, but I'd be willing to help you sort your issues if you posted your dmesg. Josh To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: dmesg Analysis
> On Mon, Mar 24, 2003 at 09:08:31PM -0500, Bob Perry wrote: > > I recently upgraded/reinstalled 4.7 RELEASE and apparently lost use of my > > SCSI tape backup system. The dmesg command indicates that FreeBSD found the > > controller and tape but I don't understand much more than that. > > > > Does anyone know where I might find some documentation which would explain > > output resulting from running dmesg? For instance, one of the lines reads: > > sa0 at adv0 bus 0 target 4 lun 0 > > ? > > Just looking for some direction. > > > > Thanks > > > > I don't know of any docs that really explain reading a dmesg in detail, but > I'd be willing to help you sort your issues if you posted your dmesg. Thanks Josh, I have a SCSI Seagate TapeStor system that worked fine under 4.5 RELEASE. It worked equally as well when I tried a binary upgrade to 4.7. There were too many other problems with the upgrade so later I did a complete install of 4.7. This is where I found that my tape system no longer responded to any mt commands. I ran the command dmesg | grep sa0 for the tape device and got the following: sa0 at adv0 bus 0 target 4 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 10,000 MB/s transfers (10,000 MHz, offset 15) Also ran dmesg | grep adv0 for the controller: adv0: AdvanSys Ultra SCSI Host Adapter SCSI ID 7, queue depth 240 adv0: port 0xb400-0xb4ff mem 0x500-0xd5ff irq 11 at device 12.0 on pci0 My kernel SCSI controller data reads: adv0at isa? My kernel SCSI peripheral data reads: saSequential Access (tape, etc) The best I can pull from this is that FreeBSD finds the tape and controller when it boots. Thanks again To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: dmesg Analysis
On Monday 24 March 2003 09:08 pm, Bob Perry wrote: > I recently upgraded/reinstalled 4.7 RELEASE and apparently lost use of my > SCSI tape backup system. The dmesg command indicates that FreeBSD found > the controller and tape but I don't understand much more than that. > > Does anyone know where I might find some documentation which would explain > output resulting from running dmesg? For instance, one of the lines reads: > sa0 at adv0 bus 0 target 4 lun 0 many (most?) of the items in dmesg are device drivers and have manpages. so first read man man then try things like man -aw sa you'll see: /usr/share/man/cat8/sa.8.gz (source: /usr/share/man/man8/sa.8.gz) /usr/share/man/man4/sa.4.gz which tells you there are two man pages for sa. one is what you are looking for, one is not, so use man 4 sa to see the right one. repeat that for all the things in dmesg and you'll learn a lot of what you're looking for. This can potentially throw you off by some things that have the same name and are not device drivers. eg man 4 fd wil not get you the floppy driver, but man 4 fdc will. hth, Tim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: dmesg Analysis
On Monday 24 March 2003 09:48 pm, Bob Perry wrote: > > On Mon, Mar 24, 2003 at 09:08:31PM -0500, Bob Perry wrote: > > > I recently upgraded/reinstalled 4.7 RELEASE and apparently lost use of > my > > > SCSI tape backup system. The dmesg command indicates that FreeBSD > > > found > the > > > controller and tape but I don't understand much more than that. > > > > > > Does anyone know where I might find some documentation which would > explain > > > output resulting from running dmesg? For instance, one of the lines > reads: > > > sa0 at adv0 bus 0 target 4 lun 0 > > > > I don't know of any docs that really explain reading a dmesg in detail, > > but > > > I'd be willing to help you sort your issues if you posted your dmesg. > > Thanks Josh, > > I have a SCSI Seagate TapeStor system that worked fine under 4.5 RELEASE. > It worked equally as well when I tried a binary upgrade to 4.7. There were > too many other problems with the upgrade so later I did a complete install > of 4.7. This is where I found that my tape system no longer responded to > any mt commands. What errors do you get? Its always good to include those. > I ran the command dmesg | grep sa0 for the tape device and got the > following: > sa0 at adv0 bus 0 target 4 lun 0 > sa0: Removable Sequential Access SCSI-2 > device > sa0: 10,000 MB/s transfers (10,000 MHz, offset 15) > > Also ran dmesg | grep adv0 for the controller: > adv0: AdvanSys Ultra SCSI Host Adapter SCSI ID 7, queue depth 240 > adv0: port 0xb400-0xb4ff mem > 0x500-0xd5ff irq 11 at device 12.0 on pci0 > > My kernel SCSI controller data reads: > adv0at isa? > My kernel SCSI peripheral data reads: > saSequential Access (tape, etc) > > The best I can pull from this is that FreeBSD finds the tape and controller > when it boots. Yep, that's exactly it. So since it sees it, I don't have any idea what would cause the problem in it not working. As I mentioned, you'll have to include the error. Since it's not likely a problem in how FreeBSD sees the device, the links on how to read dmesg will not help you that much, but hopefully will be instructive anyway. Tim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: dmesg Analysis
- Original Message - From: "taxman" <[EMAIL PROTECTED]> To: "Bob Perry" <[EMAIL PROTECTED]>; "Josh Paetzel" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Monday, March 24, 2003 11:13 PM Subject: Re: dmesg Analysis > On Monday 24 March 2003 09:48 pm, Bob Perry wrote: > > > On Mon, Mar 24, 2003 at 09:08:31PM -0500, Bob Perry wrote: > > > > I recently upgraded/reinstalled 4.7 RELEASE and apparently lost use of > > my > > > > SCSI tape backup system. The dmesg command indicates that FreeBSD > > > > found > > the > > > > controller and tape but I don't understand much more than that. > > > > > > > > Does anyone know where I might find some documentation which would > > explain > > > > output resulting from running dmesg? For instance, one of the lines > > reads: > > > > sa0 at adv0 bus 0 target 4 lun 0 > > > > > > I don't know of any docs that really explain reading a dmesg in detail, > > > > but > > > > > I'd be willing to help you sort your issues if you posted your dmesg. > > > > Thanks Josh, > > > > I have a SCSI Seagate TapeStor system that worked fine under 4.5 RELEASE. > > It worked equally as well when I tried a binary upgrade to 4.7. There were > > too many other problems with the upgrade so later I did a complete install > > of 4.7. This is where I found that my tape system no longer responded to > > any mt commands. > > What errors do you get? Its always good to include those. The errors are: w/tape inserted "Input/Output error" wo/tape inserted "Device not configured" > > > I ran the command dmesg | grep sa0 for the tape device and got the > > following: > > sa0 at adv0 bus 0 target 4 lun 0 > > sa0: Removable Sequential Access SCSI-2 > > device > > sa0: 10,000 MB/s transfers (10,000 MHz, offset 15) > > > > Also ran dmesg | grep adv0 for the controller: > > adv0: AdvanSys Ultra SCSI Host Adapter SCSI ID 7, queue depth 240 > > adv0: port 0xb400-0xb4ff mem > > 0x500-0xd5ff irq 11 at device 12.0 on pci0 > > > > My kernel SCSI controller data reads: > > adv0at isa? > > My kernel SCSI peripheral data reads: > > saSequential Access (tape, etc) > > > > The best I can pull from this is that FreeBSD finds the tape and controller > > when it boots. > > Yep, that's exactly it. So since it sees it, I don't have any idea what would > cause the problem in it not working. As I mentioned, you'll have to include > the error. > Since it's not likely a problem in how FreeBSD sees the device, the links on > how to read dmesg will not help you that much, but hopefully will be > instructive anyway. > > Tim > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: dmesg Analysis
- Original Message - From: "taxman" <[EMAIL PROTECTED]> To: "Bob Perry" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Monday, March 24, 2003 11:08 PM Subject: Re: dmesg Analysis > On Monday 24 March 2003 09:08 pm, Bob Perry wrote: > > I recently upgraded/reinstalled 4.7 RELEASE and apparently lost use of my > > SCSI tape backup system. The dmesg command indicates that FreeBSD found > > the controller and tape but I don't understand much more than that. > > > > Does anyone know where I might find some documentation which would explain > > output resulting from running dmesg? For instance, one of the lines reads: > > sa0 at adv0 bus 0 target 4 lun 0 > > many (most?) of the items in dmesg are device drivers and have manpages. > so first read man man then try things like > man -aw sa you'll see: > /usr/share/man/cat8/sa.8.gz (source: /usr/share/man/man8/sa.8.gz) > /usr/share/man/man4/sa.4.gz > which tells you there are two man pages for sa. one is what you are looking > for, one is not, so use > man 4 sa to see the right one. > > repeat that for all the things in dmesg and you'll learn a lot of what you're > looking for. I'll pay more attention to the man pages. Thanks for the input. > This can potentially throw you off by some things that have the same name and > are not device drivers. eg man 4 fd wil not get you the floppy driver, but > man 4 fdc will. > > hth, > > Tim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: dmesg Analysis
- Original Message - From: "Bob Perry" <[EMAIL PROTECTED]> To: "taxman" <[EMAIL PROTECTED]>; "Josh Paetzel" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Monday, March 24, 2003 11:31 PM Subject: Re: dmesg Analysis > > - Original Message - > From: "taxman" <[EMAIL PROTECTED]> > To: "Bob Perry" <[EMAIL PROTECTED]>; "Josh Paetzel" > <[EMAIL PROTECTED]> > Cc: <[EMAIL PROTECTED]> > Sent: Monday, March 24, 2003 11:13 PM > Subject: Re: dmesg Analysis > > > > On Monday 24 March 2003 09:48 pm, Bob Perry wrote: > > > > On Mon, Mar 24, 2003 at 09:08:31PM -0500, Bob Perry wrote: > > > > > I recently upgraded/reinstalled 4.7 RELEASE and apparently lost use > of > > > my > > > > > SCSI tape backup system. The dmesg command indicates that FreeBSD > > > > > found > > > the > > > > > controller and tape but I don't understand much more than that. > > > > > > > > > > Does anyone know where I might find some documentation which would > > > explain > > > > > output resulting from running dmesg? For instance, one of the lines > > > reads: > > > > > sa0 at adv0 bus 0 target 4 lun 0 > > > > > > > > I don't know of any docs that really explain reading a dmesg in > detail, > > > > > > but > > > > > > > I'd be willing to help you sort your issues if you posted your dmesg. > > > > > > Thanks Josh, > > > > > > I have a SCSI Seagate TapeStor system that worked fine under 4.5 > RELEASE. > > > It worked equally as well when I tried a binary upgrade to 4.7. There > were > > > too many other problems with the upgrade so later I did a complete > install > > > of 4.7. This is where I found that my tape system no longer responded > to > > > any mt commands. > > > > What errors do you get? Its always good to include those. > > The errors are: > w/tape inserted "Input/Output error" > wo/tape inserted "Device not configured" > > > > > I ran the command dmesg | grep sa0 for the tape device and got the > > > following: > > > sa0 at adv0 bus 0 target 4 lun 0 > > > sa0: Removable Sequential Access SCSI-2 > > > device > > > sa0: 10,000 MB/s transfers (10,000 MHz, offset 15) > > > > > > Also ran dmesg | grep adv0 for the controller: > > > adv0: AdvanSys Ultra SCSI Host Adapter SCSI ID 7, queue depth > 240 > > > adv0: port 0xb400-0xb4ff > mem > > > 0x500-0xd5ff irq 11 at device 12.0 on pci0 > > > > > > My kernel SCSI controller data reads: > > > adv0at isa? > > > My kernel SCSI peripheral data reads: > > > saSequential Access (tape, etc) > > > > > > The best I can pull from this is that FreeBSD finds the tape and > controller > > > when it boots. > > > > Yep, that's exactly it. So since it sees it, I don't have any idea what > would > > cause the problem in it not working. As I mentioned, you'll have to > include > > the error. > > Since it's not likely a problem in how FreeBSD sees the device, the links > on > > how to read dmesg will not help you that much, but hopefully will be > > instructive anyway. > > > > Tim Due to the timing of the whole event, I never gave the hardware a thorough check. I checked the connections but nothing more. I forgot to check the two-week old Travan 20GB tape cartridge. It was broke! I stuck in an older (3 year old) cartridge and it works just fine. Thanks to everyone for your time and input. I won't forget this one. Bob ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
