OpenSuse 10.0 and external usb hdd
Hi, I hope I have the correct forum, and apologize in advance if I don't !!! I have installed OpenSuse 10.0 (64bit) and things seem to be working ok. However, I have the following query vis the external usb-2 connection. I have 2 identical 200GB Seagate drives - one connected internally (/dev/hda) and another externally (for backup/rsync). When I do a hdparm on /dev/hda it works normally: rentsch-asia:/var/log # hdparm /dev/hda /dev/hda: multcount = 16 (on) IO_support = 1 (32-bit) unmaskirq = 1 (on) using_dma = 1 (on) keepsettings = 0 (off) readonly = 0 (off) readahead = 256 (on) geometry = 24321/255/63, sectors = 390721968, start = 0 However if I do the same command on the exact same drive but connected via usb2 I get this: rentsch-asia:/var/log # hdparm /dev/sda /dev/sda: HDIO_GET_32BIT failed: Invalid argument HDIO_GET_UNMASKINTR failed: Invalid argument HDIO_GET_DMA failed: Invalid argument HDIO_GET_KEEPSETTINGS failed: Invalid argument readonly = 0 (off) readahead = 256 (on) geometry = 24321/255/63, sectors = 390721967, start = 0 Any idea how to get the correct params so I can set them to my requirement?? Thanks and rgds.
On 4/11/06, Otto Rodusek (AP-SGP) <otto@applied.com.sg> wrote:
Hi,
I hope I have the correct forum, and apologize in advance if I don't !!!
I have installed OpenSuse 10.0 (64bit) and things seem to be working ok. However, I have the following query vis the external usb-2 connection. I have 2 identical 200GB Seagate drives - one connected internally (/dev/hda) and another externally (for backup/rsync).
When I do a hdparm on /dev/hda it works normally:
rentsch-asia:/var/log # hdparm /dev/hda
/dev/hda: multcount = 16 (on) IO_support = 1 (32-bit) unmaskirq = 1 (on) using_dma = 1 (on) keepsettings = 0 (off) readonly = 0 (off) readahead = 256 (on) geometry = 24321/255/63, sectors = 390721968, start = 0
However if I do the same command on the exact same drive but connected via usb2 I get this:
rentsch-asia:/var/log # hdparm /dev/sda
/dev/sda: HDIO_GET_32BIT failed: Invalid argument HDIO_GET_UNMASKINTR failed: Invalid argument HDIO_GET_DMA failed: Invalid argument HDIO_GET_KEEPSETTINGS failed: Invalid argument readonly = 0 (off) readahead = 256 (on) geometry = 24321/255/63, sectors = 390721967, start = 0
Any idea how to get the correct params so I can set them to my requirement??
Thanks and rgds.
Don't know if it will work but try: hdparm -d ata /dev/sda Greg -- Greg Freemyer The Norcross Group Forensics for the 21st Century
Otto Rodusek (AP-SGP) wrote:
Hi,
I hope I have the correct forum, and apologize in advance if I don't !!!
I have installed OpenSuse 10.0 (64bit) and things seem to be working ok. However, I have the following query vis the external usb-2 connection. I have 2 identical 200GB Seagate drives - one connected internally (/dev/hda) and another externally (for backup/rsync).
When I do a hdparm on /dev/hda it works normally:
rentsch-asia:/var/log # hdparm /dev/hda
/dev/hda: multcount = 16 (on) IO_support = 1 (32-bit) unmaskirq = 1 (on) using_dma = 1 (on) keepsettings = 0 (off) readonly = 0 (off) readahead = 256 (on) geometry = 24321/255/63, sectors = 390721968, start = 0
However if I do the same command on the exact same drive but connected via usb2 I get this:
rentsch-asia:/var/log # hdparm /dev/sda
/dev/sda: HDIO_GET_32BIT failed: Invalid argument HDIO_GET_UNMASKINTR failed: Invalid argument HDIO_GET_DMA failed: Invalid argument HDIO_GET_KEEPSETTINGS failed: Invalid argument readonly = 0 (off) readahead = 256 (on) geometry = 24321/255/63, sectors = 390721967, start = 0
Any idea how to get the correct params so I can set them to my requirement??
Thanks and rgds.
If you look carefully how the drive is mounte, you will discover it probably will be mounted as a scsi drive. As a result, the hdparam will not work. -- Joseph Loo jloo@acm.org
[Suse 10.0 - how to stop kernel logging for usb-storage??] Hi, I got a problem with suse 10.0 logging mechanism. It works properly in most instances except when I connect an external usb-2 device (ie. a hard disk). The external usb works fine BUT /var/log/messages becomes VERY huge VERY fast with tons of data from kernel - see below. Does anyone have any idea how to reduce the amount of output from the kernel for usb-storage. Thanks for any help and/or advice. Rgds. Apr 12 22:20:01 rentsch-asia /usr/sbin/cron[21890]: (root) CMD (/usr/appbin/getmail.sh 1>/dev/null 2>&1) Apr 12 22:24:13 rentsch-asia kernel: usb-storage: queuecommand called Apr 12 22:24:13 rentsch-asia kernel: usb-storage: *** thread awakened. Apr 12 22:24:13 rentsch-asia kernel: usb-storage: Command READ_10 (10 bytes) Apr 12 22:24:13 rentsch-asia kernel: usb-storage: 28 00 00 00 00 00 00 00 01 00 Apr 12 22:24:13 rentsch-asia kernel: usb-storage: Bulk Command S 0x43425355 T 0x616 L 512 F 128 Trg 0 LUN 0 CL 10 Apr 12 22:24:13 rentsch-asia kernel: usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes Apr 12 22:24:13 rentsch-asia kernel: usb-storage: Status code 0; transferred 31/31 Apr 12 22:24:13 rentsch-asia kernel: usb-storage: -- transfer complete Apr 12 22:24:13 rentsch-asia kernel: usb-storage: Bulk command transfer result=0 Apr 12 22:24:13 rentsch-asia kernel: usb-storage: usb_stor_bulk_transfer_sglist: xfer 512 bytes, 1 entries Apr 12 22:24:13 rentsch-asia kernel: usb-storage: Status code 0; transferred 512/512 Apr 12 22:24:13 rentsch-asia kernel: usb-storage: -- transfer complete Apr 12 22:24:13 rentsch-asia kernel: usb-storage: Bulk data transfer result 0x0 Apr 12 22:24:13 rentsch-asia kernel: usb-storage: Attempting to get CSW... Apr 12 22:24:13 rentsch-asia kernel: usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes Apr 12 22:24:13 rentsch-asia kernel: usb-storage: Status code 0; transferred 13/13 Apr 12 22:24:13 rentsch-asia kernel: usb-storage: -- transfer complete Apr 12 22:24:13 rentsch-asia kernel: usb-storage: Bulk status result = 0 Apr 12 22:24:13 rentsch-asia kernel: usb-storage: Bulk Status S 0x53425355 T 0x616 R 0 Stat 0x0 Apr 12 22:24:13 rentsch-asia kernel: usb-storage: scsi cmd done, result=0x0 Apr 12 22:24:13 rentsch-asia kernel: usb-storage: *** thread sleeping. Apr 12 22:24:13 rentsch-asia kernel: usb-storage: queuecommand called Apr 12 22:24:13 rentsch-asia kernel: usb-storage: *** thread awakened. Apr 12 22:24:13 rentsch-asia kernel: usb-storage: Command READ_10 (10 bytes) Apr 12 22:24:13 rentsch-asia kernel: usb-storage: 28 00 00 00 00 01 00 00 29 00 Apr 12 22:24:13 rentsch-asia kernel: usb-storage: Bulk Command S 0x43425355 T 0x617 L 20992 F 128 Trg 0 LUN 0 CL 10 Apr 12 22:24:13 rentsch-asia kernel: usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes Apr 12 22:24:13 rentsch-asia kernel: usb-storage: Status code 0; transferred 31/31 Apr 12 22:24:13 rentsch-asia kernel: usb-storage: -- transfer complete Apr 12 22:24:13 rentsch-asia kernel: usb-storage: Bulk command transfer result=0 Apr 12 22:24:13 rentsch-asia kernel: usb-storage: usb_stor_bulk_transfer_sglist: xfer 20992 bytes, 6 entries Apr 12 22:24:13 rentsch-asia kernel: usb-storage: Status code 0; transferred 20992/20992 Apr 12 22:24:13 rentsch-asia kernel: usb-storage: -- transfer complete Apr 12 22:24:13 rentsch-asia kernel: usb-storage: Bulk data transfer result 0x0 Apr 12 22:24:13 rentsch-asia kernel: usb-storage: Attempting to get CSW... [Same stuff contnues for thousands of lines!!!!!!]
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Wednesday 2006-04-12 at 22:46 +0800, Otto Rodusek (AP-SGP) wrote: Note: you may have hijacked the thread "OpenSuse 10.0 and external usb hdd".
I got a problem with suse 10.0 logging mechanism. It works properly in most instances except when I connect an external usb-2 device (ie. a hard disk). The external usb works fine BUT /var/log/messages becomes VERY huge VERY fast with tons of data from kernel - see below. Does anyone have any idea how to reduce the amount of output from the kernel for usb-storage. Thanks for any help and/or advice. Rgds.
Maybe it is set to "debug" mode somewhere. I don't know about that, but I know you could log all kernel messages to another file and rotate it faster - or even dump it without loging. That would be done in the syslog or syslog-ng config. With the later, you can instead filter out all usb-storage messages. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFEPT5btTMYHG2NR9URAifmAKCR2iAYTxzHTygcUNFyVnF60MK7rACfX8j3 9XF2IrL5wbpgifOiQ6hhxiY= =SFV3 -----END PGP SIGNATURE-----
participants (4)
-
Carlos E. R. -
Greg Freemyer -
Joseph Loo -
Otto Rodusek (AP-SGP)