Aug 2009 16:52:31 +0400
> From: Andrei Crivoi
> Subject: Sony PRS-505 Reader and camcontrol load problem
> To: freebsd-questions@freebsd.org
> Message-ID:
> <332c55d60908020552h4b89e7d5y97e4c8b29f313...@mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
Hi gaise,
i'm trying to mount a memory stick card on my Sony Portable Reader PRS-505
device and constantly getting the "Error received from start unit command"
message when issuing "camcontrol load" command.
Here is the full log:
[r...@morbo /usr/home/andrei]# camcontrol
0
(probe6:ahc0:0:6:0): Unexpected busfree in Message-out phase
SEQADDR == 0x170
and each time I run
# camcontrol rescan all
Re-scan of bus 0 was successful
#
I get these lines added to dmesg:
(probe6:ahc0:0:6:0): INQUIRY. CDB: 12 0 0 0 24 0
(probe6:ahc0:0:6:0): Unexpected busfree in Message-out phase
S
ng in the OS
before/after I swap out a drive? I've seen people talk about rescanning and
running other camcontrol commands before...
Any other tips?
Thanks,
Josh
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/list
On Sun, May 13, 2007 at 01:14:57AM -0700, Ted Mittelstaedt wrote:
>
>
> > -Original Message-
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED] Behalf Of Grant Peel
> > Sent: Friday, May 11, 2007 5:51 PM
> > To: freebsd-questions@fre
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Grant Peel
> Sent: Friday, May 11, 2007 5:51 PM
> To: freebsd-questions@freebsd.org
> Subject: Re: camcontrol
>
>
> I have already set camcontrol to tell the system to sto
I have already set camcontrol to tell the system to stop using that part of the
drive per the FAQ and Handbook:
AWRE (Auto Write Reallocation Enbld): 1
ARRE (Auto Read Reallocation Enbld): 1
But, it still tries to read the block in question (3abd5c1). It is always that
same block, so the
"Grant Peel" <[EMAIL PROTECTED]> writes:
> I have a disk that may be going bad, SCSI.
>
> How do I tell camcontrol to stop using parts of the disk that show errors?
>
> such as:
>
> (da0:ahc0:0:1:0): READ(10). CDB: 28 0 3 ab d5 c1 0 0 e 0
> (da0:ahc0:0:
Hi all,
I have a disk that may be going bad, SCSI.
How do I tell camcontrol to stop using parts of the disk that show errors?
such as:
(da0:ahc0:0:1:0): READ(10). CDB: 28 0 3 ab d5 c1 0 0 e 0
(da0:ahc0:0:1:0): MEDIUM ERROR info:3abd5c1 asc:11,1
(da0:ahc0:0:1:0): Read retries exhausted sks
ete dumps (From may1),
> The machine is a vintage 2003 Dell SC1400
> HD = 1 Fujitsu SCSI that has never had problems before.
>
> Questions:
>
> Do the errors below TRUELY indicate pending doom?
>
> Can camcontrol be used to squash the errors?
>
> Should FSCK be used
never had problems before.
Questions:
Do the errors below TRUELY indicate pending doom?
Can camcontrol be used to squash the errors?
Should FSCK be used to fix?
Are these errors (the text below), formatted from the FreeBSD kernel or are
they shown as reported by the HD subsystem? i.e. where can I
d target or lun"
We seem to be missing this feature. "Stop" is just going to cause the
disk to spin down. So what is the equiviliant recommended procedure on
FreeBSD?
Current thinking:
- Umount the FS;
- Remove it from any geom(4) devices
- Physically pull the drive
- Rescan t
, the only way to adjust parameters on SCSI drives is
through camcontrol's modepage option. The output on one of the new disks
looks like:
$ sudo camcontrol modepage 0:2 -m 8
IC: 0
ABPF: 0
CAP: 0
DISC: 1
SIZE: 0
WCE: 1
MF: 0
RCD: 0
Demand Rete
How can I handle Compaq Smart Raid disks using camcontrol?
I've looked a lot around, and found sometimes the same question, but
no answers:
I've an internal Smart Raid card (on a DL360) handling a mirrored set of disks.
Boot says:
Aug 5 21:23:13 ia-srv01 kernel: idad0: on ida0
[EMAIL PROTECTED] writes:
> i have a problem with camcontrol (running FreeBSD 5.4-STABLE).
> Checking the defects on my drive will print out an error which i do not
> know:
>
> #camcontrol defects da0 -G -f bfi
> camcontrol: Error returned from read defect data command
>
Hi,
I want to find a way to run Lotus Notes 6.5.1 on my FreeBSD Workstation.
Is there anyone who has made this?
I have installed wine, but when I try to install or run the client nothing
happens. Later I've copied notes installation from a windows box but still
I can't run the application.
Ivai
Hi,
i have a problem with camcontrol (running FreeBSD 5.4-STABLE).
Checking the defects on my drive will print out an error which i do not
know:
#camcontrol defects da0 -G -f bfi
camcontrol: Error returned from read defect data command
#camcontrol defects da0 -f phys -G
camcontrol: Error
queue size to one.
As for whether it will help your specific problem, I don't know, but I can't
see how it would do any harm to test it.
Using the camcontrol utility, I found these drives were already set to "1"
blacklamb# camcontrol tags da2 -v
(pass3:sbp0:0:0:0): dev_open
What do these
errors mean? How can I correct them? Is the following section from the
sbp man page applicable to my situation?
Some (broken) HDDs don't work well with tagged queuing. If you have prob-
lems with such drives, try ``camcontrol [device id] tags -N 1'' to dis-
able ta
en) HDDs don't work well with tagged queuing. If you have prob-
> lems with such drives, try ``camcontrol [device id] tags -N 1'' to dis-
> able tagged queuing.
>
> Thanks for your help!
>
> Drew
>
___
freebsd-questions@fre
enclosure. These are also
the drives that come up "referenced" after restarting. What do these
errors mean? How can I correct them? Is the following section from the
sbp man page applicable to my situation?
Some (broken) HDDs don't work well with tagged queuing. If you have prob
In the last episode (Mar 07), Anthony Atkielski said:
> Dan Nelson writes:
> > Run "camcontrol devlist -v". That will print out which controller
> > each scbus is attached to. Maybe you have a dual-channel SCSI
> > card, or have added "device atapicam"
Dan Nelson writes:
> Run "camcontrol devlist -v". That will print out which controller each
> scbus is attached to. Maybe you have a dual-channel SCSI card, or have
> added "device atapicam" to your kernel config file?
Here's what I get:
freebie# camcontr
In the last episode (Mar 07), Anthony Atkielski said:
> Why does camcontrol say that I have two SCSI controllers, when in fact I
> have only one (on a PCI card I added to the machine). My SCSI devices
> show on controller 1, whereas there's nothing on controller 0. I don't
Why does camcontrol say that I have two SCSI controllers, when in fact I
have only one (on a PCI card I added to the machine). My SCSI devices
show on controller 1, whereas there's nothing on controller 0. I don't
have an on-board SCSI controller on the motherboard, so the only S
> $ camcontrol |& grep stop
> camcontrol stop [dev_id] [generic args]
>
> Works for me. There's also a 'start' command.
I'm blind as a bat (no offense to any bats out there). I have no
idea how I missed that.
Thanks!
_
In the last episode (Feb 04), Kevin A. Pieckiel said:
> I want to replace a 9 GB SCSI drive with an 18 GB SCSI drive. All
> the hardware supports hot-swapping. Just for kicks, I thought I'd
> try to turn the drive off via SCSI commands and replace it without
> rebooting.
&g
Hey, all.
I want to replace a 9 GB SCSI drive with an 18 GB SCSI drive. All the
hardware supports hot-swapping. Just for kicks, I thought I'd try to
turn the drive off via SCSI commands and replace it without rebooting.
The camcontrol utility doesn't have a disconnect command or a
At 01:19 PM 06/17/2004, Carl Reisinger wrote:
J.D. Bronson wrote:
I know the bus will slow down with the tape drive attached, but will it
come back to normal speeds once I remove the tape drive? - and/or do I
have to run the camcontrol command again?
Run the rescan again.
Just removing the
J.D. Bronson wrote:
I know the bus will slow down with the tape drive attached, but will it
come back to normal speeds once I remove the tape drive? - and/or do I
have to run the camcontrol command again?
Run the rescan again.
Just removing the device from the bus does not cause the kernel or
then boot
the machine, it is detected and runs fine :)
If I forget, I hook it up later and then run 'camcontrol rescan all'
and the tape drive is immediately picked up and works fine :)
My question is, since I start out w/o the tape drive connected, I am
running LVD with u160 speeds
In the last episode (Apr 07), Tadimeti Keshav said:
> HI,
> Is the following sequence to mount a firewire Hard
> disk correct?
> a. camcontrol devlist -v
> b. camcontrol start da0 (provided it is recognized)
> c. mount_msdosfs /dev/da0 /
>
> Is this all needed to mount
HI,
Is the following sequence to mount a firewire Hard
disk correct?
a. camcontrol devlist -v
b. camcontrol start da0 (provided it is recognized)
c. mount_msdosfs /dev/da0 /
Is this all needed to mount this HDD?
secondly, should I use camcontrol start or camcontrol
load?
Thx for any help
Tk
hurt sequential write access, so it's probably safe
to turn on. If you're paranoid about possibly getting damaged
filesystems during power outages, you might want to turn it back off,
although every year or so there's a thread that pops up debating its
merits.
> I've had
-e -P 2", and set
"WCE: 1"
I needed to modify your command slightly to:
camcontrol mode da0 -m 8 -e -P 0
I guess I don't have a page 2 for some reason... This will
probably cause this bit to be reset on reboot as well, because it
is the current page?
Is it prudent to attem
Hi,
With Nate Lawson's help, I have my FC/SCSI target mode operations working;
now I need to make things work on the initiator side.
A camcontrol rescan 1 causes the new target to become visible on the
initiator-side card. But the target is listed as
at scbus1 target 0 lun 0 (
36 matches
Mail list logo
