Re: Sony PRS-505 Reader and camcontrol load problem
I like to blame things like that on DRM. Proving it is the tricky part. http://en.wikipedia.org/wiki/MagicGate The Wikipedia article says the Sony Portable e-Reader PRS-500 did not support MagicGate, but future support is possible through a firmware update. Regards, James Date: Sun, 2 Aug 2009 16:52:31 +0400 From: Andrei Crivoi andrei.cri...@gmail.com 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 rescan all Re-scan of bus 0 was successful Re-scan of bus 1 was successful [r...@morbo /usr/home/andrei]# camcontrol devlist Sony PRS-505/UC 1000 at scbus1 target 0 lun 0 (pass0,da0) Sony PRS-505/UC:MS 1000 at scbus1 target 0 lun 1 (pass1,da1) Sony PRS-505/UC:SD 1000 at scbus1 target 0 lun 2 (pass2,da2) [r...@morbo /usr/home/andrei]# camcontrol load 1:0:1 Error received from start unit command The most interesting fact - 'camcontrol format' somehow saves the situation: __ Looking for the perfect gift? Give the gift of Flickr! http://www.flickr.com/gift/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Sony PRS-505 Reader and camcontrol load problem
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 rescan all Re-scan of bus 0 was successful Re-scan of bus 1 was successful [r...@morbo /usr/home/andrei]# camcontrol devlist Sony PRS-505/UC 1000 at scbus1 target 0 lun 0 (pass0,da0) Sony PRS-505/UC:MS 1000 at scbus1 target 0 lun 1 (pass1,da1) Sony PRS-505/UC:SD 1000 at scbus1 target 0 lun 2 (pass2,da2) [r...@morbo /usr/home/andrei]# camcontrol load 1:0:1 Error received from start unit command The most interesting fact - 'camcontrol format' somehow saves the situation: [r...@morbo /usr/home/andrei]# camcontrol format 1:0:1 You are about to REMOVE ALL DATA from the following device: pass1: Sony PRS-505/UC:MS 1000 Removable Direct Access SCSI-2 device 40.000MB/s transfers Are you SURE you want to do this? (yes/no) yes Current format timeout is 10800 seconds Enter new timeout in seconds or press return to keep the current timeout [10800] camcontrol: Unexpected SCSI error during format (pass1:umass-sim0:0:0:1): TEST UNIT READY. CDB: 0 20 0 0 0 0 (pass1:umass-sim0:0:0:1): CAM Status: SCSI Status Error (pass1:umass-sim0:0:0:1): SCSI Status: Check Condition (pass1:umass-sim0:0:0:1): UNIT ATTENTION asc:28,0 (pass1:umass-sim0:0:0:1): Not ready to ready change, medium may have changed [r...@morbo /usr/home/andrei]# camcontrol load 1:0:1 Unit started successfully, Media loaded And now i'm able to mount the device: [r...@morbo /usr/home/andrei]# sudo mount -t msdosfs /dev/da1 /media/ mount_msdosfs: /dev/da1: : Invalid argument [r...@morbo /usr/home/andrei]# sudo mount -t msdosfs /dev/da1s1 /media/ Somebody please explain what is going on and why can't i load the device without trying to format it first. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
camcontrol(8) - Unexpected busfree in Message-out phase
I cannot get my scsi scanner detected. I'm using FBSD 8.0-current on i386. I'm trying to connect a scsi scanner. I've the following card: ahc0: Adaptec 2940 Ultra SCSI adapter port 0xd800-0xd8ff mem 0xff8ff000-0xff8f irq 10 at device 0.0 on pci1 ahc0: [ITHREAD] aic7880: Ultra Wide Channel A, SCSI Id=7, 16/253 SCBs The scanner's SCSI ID is 6 and it is switched on at boot. I get the following in dmesg: Waiting 5 seconds for SCSI devices to settle (probe0:ahc0:0:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe1:ahc0:0:1:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe2:ahc0:0:2:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe3:ahc0:0:3:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe4:ahc0:0:4:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe5:ahc0:0:5:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe6:ahc0:0:6:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe7:ahc0:0:8:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe8:ahc0:0:9:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe9:ahc0:0:10:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe10:ahc0:0:11:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe11:ahc0:0:12:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe12:ahc0:0:13:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe13:ahc0:0:14:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe14:ahc0:0:15:0): INQUIRY. CDB: 12 0 0 0 24 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 SEQADDR == 0x170 and nothing is detected: I'm sure I miss something out, so I don't think this is a `currnet' issue. Any advice? many thanks anton -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 928 8233 Fax: +44 (0)117 929 4423 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Questions about camcontrol, hot-swapping, ciss and Compaq SmartArray
Hello, Today I saw that one of my disks seems to be dead/dying in a RAID 5 array I have: http://pastebin.ca/937249 snip loki.domain.int ciss0: *** Fatal drive error, SCSI port 1 ID 0 loki.domain.int (da1:ciss0:0:1:0): WRITE(10). CDB: 2a 0 c ae 3f d0 0 0 20 0 loki.domain.int (da1:ciss0:0:1:0): CAM Status: SCSI Status Error loki.domain.int (da1:ciss0:0:1:0): SCSI Status: Check Condition loki.domain.int (da1:ciss0:0:1:0): MEDIUM ERROR asc:11,0 loki.domain.int (da1:ciss0:0:1:0): Unrecovered read error loki.domain.int (da1:ciss0:0:1:0): Retrying Command (per Sense Data) /snip I see messages for port 0 only, but varying ID 0-3, and I'm not sure what that means (partition?). After a while the error messages went away, though the disks were/are still being used. I found cciss_vol_status online but it says the volume is OK (not degraded), which doesn't really make sense to me: # cciss_vol_status /dev/ciss0 /dev/ciss0: (Smart Array 642) RAID 0 Volume 0(?) status: OK. /dev/ciss0: (Smart Array 642) RAID 5 Volume 1(?) status: OK. Is there a way I can tell which port/disk is bad from these messages? Assuming I can determine which disk it is, do I need to do anything 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/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: camcontrol
-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 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). Then you are screwed. The drive is using some sort of remapping and the actual block with the problem is somewhere else. It is always that same block, so the badness does not seem to be growing.Is there a way to diagnose what file it is trying to read? (perhaps I could remove that inode?) No and no. What you need to do is backup the disk, then boot into MS-DOS and run the disk drive manufacturer's software that forces the SCSI disk to update it's bad sector list and remap the bad block. A modern SCSI disk should NEVER show an error because it is always silently remapping bad sectors. All disks lose a sector now and then, that is why they have spare sectors and a bad sector list. You will never see a report of a bad sector until the day comes that the disk has had so many sectors fail that it's used up it's spare sectors. Years ago there were some disks that while they had this capability it was disabled by default - I have no idea why - and when a bad sector did develop the disk would report it until you sent the device a scsi format command, then the remapping would happen. There are some disk programs on the Internet that can do this as well. Ted -Grant- Original Message - From: Lowell Gilbert To: Grant Peel Cc: freebsd-questions@freebsd.org Sent: Friday, May 11, 2007 10:51 AM Subject: Re: camcontrol 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:1:0): MEDIUM ERROR info:3abd5c1 asc:11,1 (da0:ahc0:0:1:0): Read retries exhausted sks:80,3f Please see the FAQ entry on this topic. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Total Control Panel Login To: [EMAIL PROTECTED] Block messages from this sender (blacklist) From: [EMAIL PROTECTED] Remove this sender from my whitelist You received this message because the sender is on your whitelist. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: camcontrol
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@freebsd.org Subject: Re: camcontrol 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). Then you are screwed. The drive is using some sort of remapping and the actual block with the problem is somewhere else. It is always that same block, so the badness does not seem to be growing.Is there a way to diagnose what file it is trying to read? (perhaps I could remove that inode?) No and no. What you need to do is backup the disk, then boot into MS-DOS and run the disk drive manufacturer's software that forces the SCSI disk to update it's bad sector list and remap the bad block. A modern SCSI disk should NEVER show an error because it is always silently remapping bad sectors. There is one situation where it is not possible to do silent remapping of sectors. That situation is where the bad block is discovered when trying to read from it. If the disk cannot read the block it does not know what data was supposed to be there and thus cannot rewrite it to another block. (A good RAID setup can handle that situation too, since then the controller can find out from the other disks in the array what the data in that block should have been.) All disks lose a sector now and then, that is why they have spare sectors and a bad sector list. You will never see a report of a bad sector until the day comes that the disk has had so many sectors fail that it's used up it's spare sectors. Years ago there were some disks that while they had this capability it was disabled by default - I have no idea why - and when a bad sector did develop the disk would report it until you sent the device a scsi format command, then the remapping would happen. There are some disk programs on the Internet that can do this as well. -- Insert your favourite quote here. Erik Trulsson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: camcontrol
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:1:0): MEDIUM ERROR info:3abd5c1 asc:11,1 (da0:ahc0:0:1:0): Read retries exhausted sks:80,3f Please see the FAQ entry on this topic. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: camcontrol
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 badness does not seem to be growing.Is there a way to diagnose what file it is trying to read? (perhaps I could remove that inode?)-Grant- Original Message - From: Lowell Gilbert To: Grant Peel Cc: freebsd-questions@freebsd.org Sent: Friday, May 11, 2007 10:51 AM Subject: Re: camcontrol 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:1:0): MEDIUM ERROR info:3abd5c1 asc:11,1 (da0:ahc0:0:1:0): Read retries exhausted sks:80,3f Please see the FAQ entry on this topic. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Total Control Panel Login To: [EMAIL PROTECTED] Block messages from this sender (blacklist) From: [EMAIL PROTECTED] Remove this sender from my whitelist You received this message because the sender is on your whitelist. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
camcontrol
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:80,3f ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
SCSI + camcontrol
Hello all, A few weeks back, I turned on mod_gzip in apache and as a result, the /tmp directory filled up with .wrk files causing the root filesystem to fill to capacity. When we noticed what was happening, on May 1 we had no choice but to cold boot the machine as it was, for all purposes locked up. In the security run, for May 1 and May 3 I am seeing the SCSI errors below. FreeBSD 4.7 (yes we are going to upgrade soon (migrating to a newly setup machine)), Apache 1.3.26 We do have complete 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 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 go to read what the errors actually mean? THanks all, -Grant May 3: May 3 03:59:13 excelsior /kernel: (da0:ahc0:0:1:0): READ(10). CDB: 28 0 4 21 7a df 0 0 80 0 May 3 03:59:13 excelsior /kernel: (da0:ahc0:0:1:0): MEDIUM ERROR info:4217b55 asc:11,1 May 3 03:59:14 excelsior /kernel: (da0:ahc0:0:1:0): Read retries exhausted sks:80,3f May 3 03:59:16 excelsior /kernel: (da0:ahc0:0:1:0): READ(10). CDB: 28 0 4 21 7a ef 0 0 70 0 May 3 03:59:18 excelsior /kernel: (da0:ahc0:0:1:0): MEDIUM ERROR info:4217b55 asc:11,1 May 3 03:59:18 excelsior /kernel: (da0:ahc0:0:1:0): Read retries exhausted sks:80,3f May 3 03:59:20 excelsior /kernel: (da0:ahc0:0:1:0): READ(10). CDB: 28 0 4 21 7a ff 0 0 60 0 May 3 03:59:21 excelsior /kernel: (da0:ahc0:0:1:0): MEDIUM ERROR info:4217b55 asc:11,1 May 3 03:59:22 excelsior /kernel: (da0:ahc0:0:1:0): Read retries exhausted sks:80,3f May 3 03:59:24 excelsior /kernel: (da0:ahc0:0:1:0): READ(10). CDB: 28 0 4 21 7b f 0 0 50 0 May 3 03:59:27 excelsior /kernel: (da0:ahc0:0:1:0): MEDIUM ERROR info:4217b55 asc:11,1 May 3 03:59:28 excelsior /kernel: (da0:ahc0:0:1:0): Read retries exhausted sks:80,3f May 3 03:59:29 excelsior /kernel: (da0:ahc0:0:1:0): READ(10). CDB: 28 0 4 21 7b 1f 0 0 40 0 May 3 03:59:29 excelsior /kernel: (da0:ahc0:0:1:0): MEDIUM ERROR info:4217b55 asc:11,1 May 3 03:59:29 excelsior /kernel: (da0:ahc0:0:1:0): Read retries exhausted sks:80,3f May 3 03:59:32 excelsior /kernel: (da0:ahc0:0:1:0): READ(10). CDB: 28 0 4 21 7b 2f 0 0 30 0 May 3 03:59:33 excelsior /kernel: (da0:ahc0:0:1:0): MEDIUM ERROR info:4217b55 asc:11,1 May 3 03:59:35 excelsior /kernel: (da0:ahc0:0:1:0): Read retries exhausted sks:80,3f May 3 03:59:36 excelsior /kernel: (da0:ahc0:0:1:0): READ(10). CDB: 28 0 4 21 7b 3f 0 0 20 0 May 3 03:59:36 excelsior /kernel: (da0:ahc0:0:1:0): MEDIUM ERROR info:4217b55 asc:11,1 May 3 03:59:36 excelsior /kernel: (da0:ahc0:0:1:0): Read retries exhausted sks:80,3f May 3 03:59:42 excelsior /kernel: (da0:ahc0:0:1:0): READ(10). CDB: 28 0 4 21 7b 4f 0 0 10 0 May 3 03:59:42 excelsior /kernel: (da0:ahc0:0:1:0): MEDIUM ERROR info:4217b55 asc:11,1 May 3 03:59:43 excelsior /kernel: (da0:ahc0:0:1:0): Read retries exhausted sks:80,3f May 3 03:59:45 excelsior /kernel: (da0:ahc0:0:1:0): READ(10). CDB: 28 0 4 21 7b 4f 0 0 10 0 May 3 03:59:47 excelsior /kernel: (da0:ahc0:0:1:0): MEDIUM ERROR info:4217b55 asc:11,1 May 3 03:59:48 excelsior /kernel: (da0:ahc0:0:1:0): Read retries exhausted sks:80,3f May 3 03:59:49 excelsior /kernel: (da0:ahc0:0:1:0): READ(10). CDB: 28 0 4 21 7b 4f 0 0 10 0 May 3 03:59:49 excelsior /kernel: (da0:ahc0:0:1:0): MEDIUM ERROR info:4217b55 asc:11,1 May 3 03:59:49 excelsior /kernel: (da0:ahc0:0:1:0): Read retries exhausted sks:80,3f May 1: May 1 03:29:28 excelsior /kernel: (da0:ahc0:0:1:0): READ(10). CDB: 28 0 3 ab d5 c1 0 0 e 0 May 1 03:29:31 excelsior /kernel: (da0:ahc0:0:1:0): MEDIUM ERROR info:3abd5c1 asc:11,1 May 1 03:29:31 excelsior /kernel: (da0:ahc0:0:1:0): Read retries exhausted sks:80,3f May 1 03:29:32 excelsior /kernel: (da0:ahc0:0:1:0): READ(10). CDB: 28 0 3 ab d5 c1 0 0 1 0 May 1 03:29:32 excelsior /kernel: (da0:ahc0:0:1:0): MEDIUM ERROR info:3abd5c1 asc:11,1 May 1 03:29:32 excelsior /kernel: (da0:ahc0:0:1:0): Read retries exhausted sks:80,3f ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SCSI + camcontrol
In the last episode (May 04), Grant Peel said: A few weeks back, I turned on mod_gzip in apache and as a result, the /tmp directory filled up with .wrk files causing the root filesystem to fill to capacity. When we noticed what was happening, on May 1 we had no choice but to cold boot the machine as it was, for all purposes locked up. In the security run, for May 1 and May 3 I am seeing the SCSI errors below. FreeBSD 4.7 (yes we are going to upgrade soon (migrating to a newly setup machine)), Apache 1.3.26 We do have complete 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 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 go to read what the errors actually mean? Those are errors reported by the drive: May 3 03:59:13 excelsior /kernel: (da0:ahc0:0:1:0): READ(10). CDB: 28 0 4 21 7a df 0 0 80 0 May 3 03:59:13 excelsior /kernel: (da0:ahc0:0:1:0): MEDIUM ERROR info:4217b55 asc:11,1 May 3 03:59:14 excelsior /kernel: (da0:ahc0:0:1:0): Read retries exhausted sks:80,3f May 1 03:29:28 excelsior /kernel: (da0:ahc0:0:1:0): READ(10). CDB: 28 0 3 ab d5 c1 0 0 e 0 May 1 03:29:31 excelsior /kernel: (da0:ahc0:0:1:0): MEDIUM ERROR info:3abd5c1 asc:11,1 May 1 03:29:31 excelsior /kernel: (da0:ahc0:0:1:0): Read retries exhausted sks:80,3f The drive has tried to read the indicated block number (0x4217b55 and 0x3abd5c1), and couldn't, even after multiple retries. If it was able to recover the data after retrying, it would have reallocated the block to a spare sector. There isn't an easy way to map a raw block number to a filename, but if you can determine that the files belonging to the blocks were old, your drive is probably still okay, and you happened to trip over some weak spots on the disk that lost their data over time. If they were recently-generated files, then I'd start worrying about getting that new system up as soon as possible. One thing to try would be dd if=/dev/da0 of=/dev/null bs=64k, and see how many more errors get generated. Installing smartmontools and comparing the output of smartctl -a /dev/da0 before and after will also tell you how many ECC recoveries and rereads were done. -- Dan Nelson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
scsictl(8) 'detach' equiv in camcontrol(8) ?
NBSD provides a safe way to detach the kernel data structures of a disk, 'scsictl detach [target] [lun]' From scsictl(8) man page: Commands pertaining to scsi busses: reset scan target lun detach target lun Use `any' or `all' to wildcard 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 the bus w/ camcontrol and let it discover that the disk is no longer there - Insert the new drive - Rescan the bus and let it discover the new drive Presumably instead of rescanning the whole bus, you could scan a specific bus[:target:lun]. Thoughts? ~BAS l8* -lava (Brian A. Seklecki - Pittsburgh, PA, USA) http://www.spiritual-machines.org/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Deciphering camcontrol - is prefetch enabled?
I have a new set of SCSI drives, all like: da2 at mpt0 bus 0 target 3 lun 0 da2: SEAGATE ST336754LW 0005 Fixed Direct Access SCSI-3 device da2: 320.000MB/s transfers (160.000MHz, offset 63, 16bit), Tagged Queueing Enabled da2: 35003MB (71687372 512 byte sectors: 255H 63S/T 4462C) From what I can tell, 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 Retention Priority: 0 Write Retention Priority: 0 Disable Pre-fetch Transfer Length: 65535 Minimum Pre-fetch: 0 Maximum Pre-fetch: 65535 Maximum Pre-fetch Ceiling: 65535 I'm pretty sure that WCE means write cache enabled, which is what we want. However, I'm pretty sure I want to enable prefetching, too, since data access on them will often involve a set of concurrent long streaming reads. In that case, wouldn't prefetch reduce contention among the read processes? If so, from looking at the above output, does it seem to be enabled? Since I left my handy Cryptic SCSI Acronym Dictionary elsewhere, I don't have any idea what the above is actually trying to tell me. -- Kirk Strauser pgpidQtb95hvA.pgp Description: PGP signature
camcontrol and IDAD0
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: Compaq Logical Drive on ida0 Aug 5 21:23:13 ia-srv01 kernel: idad0: 17359MB (35553120 sectors), blocksize=512 RAID is working properly, but I have no way (apparently) to check it within FreeBSD. Command camcontrol devlist -v returns scbus-1 on xpt0 bus 0: at scbus-1 target -1 lun -1 (xpt0) atacontrol does not says anything about this disk. What can I do? Is there any other resource/command available in order to solve this problem? Thanks, Tonino ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: camcontrol error
[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 #camcontrol defects da0 -f phys -G camcontrol: Error returned from read defect data command So, what could be the problem? Probably just that the drive doesn't support the READ DEFECT DATA command. Try the block format, but some drives just don't support it at all. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
camcontrol error
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 returned from read defect data command So, what could be the problem? Thanks in advance. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: camcontrol error
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. Ivailo Tanusheff Senior System administrator ProCredit Bank (Bulgaria) AD tel. +359 2 921 7161 fax +359 2 921 7110 http://www.procreditbank.bg Disclaimer: The information contained in this message is intended solely for the use of individual or entity to whom it is addressed and other authorized to receive it. It may contain confidential or legally privileged information. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this message is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by responding to this email and then delete it from your system. ProCredit Bank is neither liable for the proper and complete transmission of the information contained in this message nor for any delay in its receipt. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sbp, camcontrol, and Tagged Queuing
On 3/17/2005 8:23 PM Bob Johnson wrote: On Thursday 17 March 2005 10:08 pm, Drew Tomlinson wrote: I posted this a while back and am still having the same problem. Can anyone offer any insight as to if the sbp man page suggestion about tagged queuing is something I should try? Is there any risk of screwing up my drives by trying this? Tagged queueing queues up multiple instructions for the drive simultaneously. The drive then attempts to sort them out and execute them in optimum order. Some drives that claim to support tagged queueing do not correctly do so, and don't perform well when it is used (and may lose data). If you set the queue size to one, as recommended in the passage you reference, then only one instruction will be issued to the drive at time, and it will behave like a drive without tagged queueing. It will do no harm to the drive. If the drive correctly implements tagged queueing, this will slow down the drive, but if it does not correctly implement it, then this may dramatically speed up the drive (and make it more stable). I have an external drive that manages 1.3 MBps transfers with queueing enabled, and 25 MBps transfers when I set the 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_openings 1 (pass3:sbp0:0:0:0): dev_active0 (pass3:sbp0:0:0:0): devq_openings 1 (pass3:sbp0:0:0:0): devq_queued 0 (pass3:sbp0:0:0:0): held 0 (pass3:sbp0:0:0:0): mintags 2 (pass3:sbp0:0:0:0): maxtags 255 blacklamb# camcontrol tags da3 -v (pass4:sbp0:0:0:1): dev_openings 1 (pass4:sbp0:0:0:1): dev_active0 (pass4:sbp0:0:0:1): devq_openings 1 (pass4:sbp0:0:0:1): devq_queued 0 (pass4:sbp0:0:0:1): held 0 (pass4:sbp0:0:0:1): mintags 2 (pass4:sbp0:0:0:1): maxtags 255 Thus setting tagged queuing to 1 had no effect. Thanks again for your explanation. I sure wish I could solve this issue! Thanks, Drew This issue is not specific to FreeBSD. Any OS that supports tagged queuing has problems with some drives. - Bob [...] da2 and da3 are two IDE drives in a firewire 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- lems with such drives, try ``camcontrol [device id] tags -N 1'' to dis- able tagged queuing. Thanks for your help! Drew ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sbp, camcontrol, and Tagged Queuing
On 3/17/2005 8:23 PM Bob Johnson wrote: On Thursday 17 March 2005 10:08 pm, Drew Tomlinson wrote: I posted this a while back and am still having the same problem. Can anyone offer any insight as to if the sbp man page suggestion about tagged queuing is something I should try? Is there any risk of screwing up my drives by trying this? Tagged queueing queues up multiple instructions for the drive simultaneously. The drive then attempts to sort them out and execute them in optimum order. Some drives that claim to support tagged queueing do not correctly do so, and don't perform well when it is used (and may lose data). If you set the queue size to one, as recommended in the passage you reference, then only one instruction will be issued to the drive at time, and it will behave like a drive without tagged queueing. It will do no harm to the drive. If the drive correctly implements tagged queueing, this will slow down the drive, but if it does not correctly implement it, then this may dramatically speed up the drive (and make it more stable). I have an external drive that manages 1.3 MBps transfers with queueing enabled, and 25 MBps transfers when I set the 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. This issue is not specific to FreeBSD. Any OS that supports tagged queuing has problems with some drives. - Bob Thank you for your explanation. I will try this later today when I am close to the console and post my results for anyone else that may experience this problem. Cheers, Drew [...] da2 and da3 are two IDE drives in a firewire 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- lems with such drives, try ``camcontrol [device id] tags -N 1'' to dis- able tagged queuing. Thanks for your help! Drew ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
sbp, camcontrol, and Tagged Queuing
I posted this a while back and am still having the same problem. Can anyone offer any insight as to if the sbp man page suggestion about tagged queuing is something I should try? Is there any risk of screwing up my drives by trying this? Thanks, Drew Original Message Subject: Help Interpreting sbp0 Errors Date: Mon, 24 Jan 2005 11:43:21 -0800 From: Drew Tomlinson [EMAIL PROTECTED] I've been having problems with vinum volumes since an upgrade from 4.9 to 4.10 which I posted about here: http://docs.freebsd.org/cgi/mid.cgi?41D748F0.1000303 However maybe that is the *symptom* instead of the *problem*. I shut down my system from the console and saw this output: --- BEGIN --- boot() called on cpu#0 Waiting (max 60 seconds) for system process `vnlru' to stop...stopped Waiting (max 60 seconds) for system process `bufdaemon' to stop...stopped Waiting (max 60 seconds) for system process `syncer' to stop...stopped syncing disks... 4 done Uptime: 28d20h48m39s sbp0:0:0 request timeout(mgm orb:0x0a550b14) ... reset start sbp0:0:0 request timeout(cmd orb:0x0a550c4c) ... agent reset (da2:sbp0:0:0:0): Synchronize cache failed, status == 0xb, scsi status == 0x0 sbp0:0:1 request timeout(cmd orb:0x0a5528a4) ... agent reset (da3:sbp0:0:0:1): Synchronize cache failed, status == 0xb, scsi status == 0x0 The operating system has halted. Please press any key to reboot. --- END --- da2 and da3 are two IDE drives in a firewire 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- lems with such drives, try ``camcontrol [device id] tags -N 1'' to dis- able tagged queuing. Thanks for your help! Drew ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sbp, camcontrol, and Tagged Queuing
On Thursday 17 March 2005 10:08 pm, Drew Tomlinson wrote: I posted this a while back and am still having the same problem. Can anyone offer any insight as to if the sbp man page suggestion about tagged queuing is something I should try? Is there any risk of screwing up my drives by trying this? Tagged queueing queues up multiple instructions for the drive simultaneously. The drive then attempts to sort them out and execute them in optimum order. Some drives that claim to support tagged queueing do not correctly do so, and don't perform well when it is used (and may lose data). If you set the queue size to one, as recommended in the passage you reference, then only one instruction will be issued to the drive at time, and it will behave like a drive without tagged queueing. It will do no harm to the drive. If the drive correctly implements tagged queueing, this will slow down the drive, but if it does not correctly implement it, then this may dramatically speed up the drive (and make it more stable). I have an external drive that manages 1.3 MBps transfers with queueing enabled, and 25 MBps transfers when I set the 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. This issue is not specific to FreeBSD. Any OS that supports tagged queuing has problems with some drives. - Bob Thanks, Drew [...] da2 and da3 are two IDE drives in a firewire 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- lems with such drives, try ``camcontrol [device id] tags -N 1'' to dis- able tagged queuing. Thanks for your help! Drew ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Question on SCSI controllers and camcontrol
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 SCSI on the machine should be the one PCI card. Why does FreeBSD say that there are two? -- Anthony ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Question on SCSI controllers and camcontrol
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 have an on-board SCSI controller on the motherboard, so the only SCSI on the machine should be the one PCI card. Why does FreeBSD say that there are two? 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? -- Dan Nelson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Question on SCSI controllers and camcontrol
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# camcontrol devlist -v scbus0 on sbp0 bus 0: at scbus0 target -1 lun -1 () scbus1 on ahc0 bus 0: HP C1533A 9503 at scbus1 target 3 lun 0 (pass0,sa0) HP C1537A L708 at scbus1 target 4 lun 0 (pass1,sa1) at scbus1 target -1 lun -1 () scbus-1 on xpt0 bus 0: at scbus-1 target -1 lun -1 (xpt0) freebie# grep sbp0 /var/log/* /var/log/dmesg.today:sbp0: SBP-2/SCSI over FireWire on firewire0 /var/log/dmesg.yesterday:sbp0: SBP-2/SCSI over FireWire on firewire0 /var/log/old.messages.2:Feb 22 05:22:45 freebie kernel: sbp0: SBP-2/SCSI over FireWire on firewire0 freebie# What's the connection between firewire and SCSI? -- Anthony ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Question on SCSI controllers and camcontrol
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 to your kernel config file? Here's what I get: freebie# camcontrol devlist -v scbus0 on sbp0 bus 0: at scbus0 target -1 lun -1 () scbus1 on ahc0 bus 0: HP C1533A 9503 at scbus1 target 3 lun 0 (pass0,sa0) HP C1537A L708 at scbus1 target 4 lun 0 (pass1,sa1) at scbus1 target -1 lun -1 () scbus-1 on xpt0 bus 0: at scbus-1 target -1 lun -1 (xpt0) freebie# grep sbp0 /var/log/* /var/log/dmesg.today:sbp0: SBP-2/SCSI over FireWire on firewire0 /var/log/dmesg.yesterday:sbp0: SBP-2/SCSI over FireWire on firewire0 /var/log/old.messages.2:Feb 22 05:22:45 freebie kernel: sbp0: SBP-2/SCSI over FireWire on firewire0 freebie# What's the connection between firewire and SCSI? My guess is that firewire disks use SCSI. If you don't have any firewire storage devices, you can probably remove device sbp from your kernel config. -- Dan Nelson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
camcontrol cdb to disconnect drive
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 stop unit command (that I can find), so I was going to try to use 'camcontrol cdb' to send a stop unit command to the drive. Has anyone done anything similar? Can someone help me locate the necessary parameters to use for this command? All I can seem to find with Google is a quick reference for SCSI commands. It tells me the command to use is 1B, but I don't know what other details are needed to fill out the CDB command. I need to fill 6, 10, 12, or 16 bytes, and I only have the first. Help? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: camcontrol cdb to disconnect drive
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. The camcontrol utility doesn't have a disconnect command or a stop unit command (that I can find), so I was going to try to use 'camcontrol cdb' $ camcontrol | grep stop camcontrol stop [dev_id] [generic args] Works for me. There's also a 'start' command. -- Dan Nelson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: camcontrol cdb to disconnect drive
$ 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! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Adaptec 29160 Scsi card / camcontrol rescan
I have a machine running 5.2.1 with DUAL Adaptec 29160LP scsi cards. In the machine there are 2 U160 LVD scsi drives...one attached to each drive... I have an external SE tape drive that I have a cable for that I can attach to the 'extra' 29160 card port. If I hook it up to the card and 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. Then I hook up the tape drive (run the command) and then want to disconnect the tape drive. 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? Thanks in advance!! -- J.D. Bronson Aurora Health Care // Information Services // Milwaukee, WI USA Office: 414.978.8282 // Email: [EMAIL PROTECTED] // Pager: 414.314.8282 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Adaptec 29160 Scsi card / camcontrol rescan
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 the hba to perform any action. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Adaptec 29160 Scsi card / camcontrol rescan
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 device from the bus does not cause the kernel or the hba to perform any action. Please excuse my ignorance here Once I disconnect my tape drive and run camcontrol rescan all, I should expect the bus speed to once again return to 160? thanks! -- J.D. Bronson Aurora Health Care // Information Services // Milwaukee, WI USA Office: 414.978.8282 // Email: [EMAIL PROTECTED] // Pager: 414.314.8282 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
camcontrol start vs load
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 /my_mount_point Is this all needed to mount this HDD? secondly, should I use camcontrol start or camcontrol load? Thx for any help Tk Yahoo! Messenger - Communicate instantly...Ping your friends today! Download Messenger Now http://uk.messenger.yahoo.com/download/index.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: camcontrol start vs load
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 /my_mount_point Is this all needed to mount this HDD? secondly, should I use camcontrol start or camcontrol load? start tells the drive to spin up, so if it's already running you don't need it. load is more for things like tape drives or CD-ROMs where you have a magazine or tray that can be loaded/ejected. -- Dan Nelson [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Poor SCSI disk preformance [more on camcontrol please!]
Aha. Check the WCE bit to see if your write cache is enabled on the disk Bingo: # dd if=/dev/zero of=/dev/da0 bs=64k [1] 2253 # iostat -K -w 1 da0 tty da0 cpu tin tout KB/t tps MB/s us ni sy in id 2 38 0.00 0 0.00 1 0 1 0 98 0 43 64.00 223 13.91 0 0 8 1 91 0 43 64.00 223 13.92 0 0 5 0 95 0 43 64.00 223 13.92 0 0 8 1 91 0 43 64.00 223 13.92 0 0 6 0 94 0 42 64.00 223 13.92 0 0 5 1 94 0 43 64.00 223 13.92 1 0 6 1 92 Set it by running cmcontrol mode da0 -m 8 -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 attempt to set the WCE:1 on all drives that get attached? I will be formatting a large number of greatly varying drives, including ATA converted to SCSI type drives, and really old, and really new drive types. I've had a look at man camcontrol earlier, but I don't know enough about the inner workings of SCSI for this to mean much to me. It seems to be pretty obscure (like how would I know to enable features/specs to edit a modepage?), but extremely powerful. Where can I read more about this, is there a good camcontrol FAQ/tutorial out there that explains what these details actually mean/do? Thanks for the help! Derek ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Poor SCSI disk preformance [more on camcontrol please!]
In the last episode (Jan 06), Derek Marcotte said: Aha. Check the WCE bit to see if your write cache is enabled on the disk Bingo: # dd if=/dev/zero of=/dev/da0 bs=64k # iostat -K -w 1 da0 tty da0 cpu tin tout KB/t tps MB/s us ni sy in id 0 43 64.00 223 13.92 1 0 6 1 92 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? Possibly. Power the drive off and see if the change sticks. :) Is it prudent to attempt to set the WCE:1 on all drives that get attached? I will be formatting a large number of greatly varying drives, including ATA converted to SCSI type drives, and really old, and really new drive types. I've never seen WCE 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 a look at man camcontrol earlier, but I don't know enough about the inner workings of SCSI for this to mean much to me. It seems to be pretty obscure (like how would I know to enable features/specs to edit a modepage?), but extremely powerful. Where can I read more about this, is there a good camcontrol FAQ/tutorial out there that explains what these details actually mean/do? Everything under camcontrol modepage and cmd is pretty much straight from the SCSI spec. You can buy copies of it from ANSI (I think you can download draft copies from www.t10.org somewhere), and sometimes disk vendors will ship copies with vendor-specific info. About 15 years ago, I bought a Maxtor disk that didn't include the little sheet saying which jumpers were which SCSI id. I called up and asked them to send me a copy, and they sent me the whole reference manual for the drive, detailing every SCSI command and modepage. -- Dan Nelson [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
In 5.2: camcontrol = devfs = GEOM ? How?
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 FreeBSD Emulated Disk 0.1 at scbus1 target 0 lun 0 (pass1) which is to say that it is represented only by /dev/pass1 . How, on 5.2, do I nake devfs and (if necessary) GEOM recognize it and create the /dev/da0 , /dev/da0s1 . /dev/da0s1a , /dev/da0s1b , and so forth? Mark Terribile [EMAIL PROTECTED] Ruthlessly pricking our gonfalon bubble, Making a Giant hit into a double -- Words that are heavy with nothing but trouble: Tinkers to Evers to Chance. __ Do you Yahoo!? Find out what made the Top Yahoo! Searches of 2003 http://search.yahoo.com/top2003 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
