Re: [opensuse] Re: USB device error
On Mon, 2007-06-18 at 21:54 +0100, Philip Kisloff wrote: BTW what kind (make/model) of case is the drive mounted in? Ahem, I bought off ebay - it seems to be made in China. Search *NEW* 120 GB 2.5 External HDD Hard Disk Drive USB 2.0 I didn't honestly know it before now, but the housing seems to be rip-off of a SONY label. Unfortunate luck there. Investigating as far I can, the problem is not with the kernel, but it _is_ a hardware (or firmware) issue. The device reports incorrect residue values (?). This means that it violates the USB Mass Storage protocol specification (funny, it claims to be USB2.0 certified). Mac OS X and Windows ignore the bogus residue values but Linux doesn't. Patch submitted http://www.kernel.org/pub/linux/kernel/people/gregkh/usb/2.6/2.6.20-rc3/usb-storage-unusual_devs-add-supertop-drives.patch I should not expect that the device won't work with any earlier kernel. I guess I don't want to mess with a kernel upgrade until I do a full backup, so I'm looking for a new storgae device. About the kernel upgrade, keep an eye peeled for a new kernel in the on-line updates, and see if it matches the version numbers listed above, when that patch propagates through the various distros, you'll be in business. Do you know of a kind hearted person who can partition it for you in Windows? If so then at least it will be usable until you can do it yourself. And the moral of this story? Standards are only standards when they are adhered to. Even Logitech violates standards. :( -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] Re: USB device error
On 06/18/2007 04:20 PM, Mike McMullin wrote: On Mon, 2007-06-18 at 21:54 +0100, Philip Kisloff wrote: snip Patch submitted http://www.kernel.org/pub/linux/kernel/people/gregkh/usb/2.6/2.6.20-rc3/usb-storage-unusual_devs-add-supertop-drives.patch I should not expect that the device won't work with any earlier kernel. I guess I don't want to mess with a kernel upgrade until I do a full backup, so I'm looking for a new storgae device. About the kernel upgrade, keep an eye peeled for a new kernel in the on-line updates, and see if it matches the version numbers listed above, That is unlikely ever to happen. Opensuse 10.2 was distributed with 2.6.18, and the best that can be hoped for is that the patch will be backported to that kernel version -- maybe, but don't count on that either. Greg Kroah-Hartman signed off on the cited patch, and he's at suse.de. The current factory kernel is 2.6.22-rc4, which presumably has the patch applied. I would suggest fetching the src.rpm for that and seeing if it will compile in 10.2. -- Hypocrisy is the homage vice pays to virtue. -- François de La Rochefoucauld -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] Re: USB device error
On Sun, 2007-06-17 at 10:09 +0100, Philip Kisloff wrote: Firstly, thanks everyone for helpng me out here. I know now not to try to mount the disk before formatting it. Still having trouble. In yast, I select /dev/evms/sdb and _create_ it then pop ups with a window saying Create a Primary Partition on /dev/sda. I can't get it to to say /dev/sdb. What you need to do is click on create, in the pop-up widow select sdb by clicking on it's radio button. Ordinarilly I would have used fdisk, as I'm quite comfortable with its non-expert mode. fdisk /dev/sdb gives me Unable to read /dev/sdb. This isn't your Father's fdisk ;), after creating the partition you will need to set the file system type, 83 is normal for linux. There are a few extra steps to the cli method. -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] Re: USB device error
On Sunday 17 June 2007 04:09, Philip Kisloff wrote: Firstly, thanks everyone for helpng me out here. I know now not to try to mount the disk before formatting it. Still having trouble. In yast, I select /dev/evms/sdb and _create_ it then pop ups with a window saying Create a Primary Partition on /dev/sda. I can't get it to to say /dev/sdb. Ordinarilly I would have used fdisk, as I'm quite comfortable with its non-expert mode. fdisk /dev/sdb gives me Unable to read /dev/sdb. Phil Try to see what is available with ls command: ls /dev/evms/sd* and ls /dev/sd* Do that before you connect the drive and after. That way you will see what device is used for external drive. Than you can use that for fdisk (or you can try cfdisk) -- Regards, Rajko. -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] Re: USB device error
On Sun, 2007-06-17 at 18:52 +0100, Philip Kisloff wrote: This is the nub of the problem. I don't think my system is behaving as expected and although I doubted myself, I'm beginning to believe there is bug somewhere other than the user! That does happen. :) Before attach USB HDD ls /dev/evms/sd* ls: cannot access /dev/evms/sd*: No such file or directory ls /dev/sd* /dev/sda /dev/sda1 /dev/sda2 /dev/sda3 /dev/sda5 /dev/sda6 /dev/sda7 After attach USB HDD ls /dev/evms/sd* /dev/evms/sdb ls /dev/sd* /dev/sda /dev/sda1 /dev/sda2 /dev/sda3 /dev/sda5 /dev/sda6 /dev/sda7 /dev/sdb So the device used for external drive is /dev/sdb - but: fdisk /dev/sdb Unable to read /dev/sdb Curious did you try fdisk /dev/evms/sdb? In YAST, I can see a line /dev/evms/sdb. However, when click on create (with sdb line selected or not, it makes no difference), it does not give me an radio button option for /dev/sda or /dev/sdb, but goes straight to Create a Primary Partition on /dev/sda. Bummer. Both fdisk and YaST Partitioner require root permissions, so this should not actually be a permissions problem, and with the drive being seen you ought to be able to partition it. Now, the log says SCSI error: return code = 0x1007. When I google this string, its a known probelm that to me looks like a kernel error. It is clearly seen that the device is recognized and that it reads the basic information of the drive, but cannot access it further. Still puzzled... Yes, so am I. If you had a recent copy of either Knoppix or Ubuntu live disks, I'd suggest booting that and see if the partitioner worked any better, or to hook it up to a Win2k + system and see if you could get if partitioned that way. If you can choose fat32 for the format type and then you can use it between your linux systems and other peoples Windows systems, until such time as this error gets resolved. There apparently is an open ticket on the kernel site about this error, so it ought to get fixed, it's a question of whether or not you want to wait till then. BTW what kind (make/model) of case is the drive mounted in? -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] Re: USB device error
Philip Kisloff wrote: Before attach USB HDD ls /dev/evms/sd* ls: cannot access /dev/evms/sd*: No such file or directory ls /dev/sd* /dev/sda /dev/sda1 /dev/sda2 /dev/sda3 /dev/sda5 /dev/sda6 /dev/sda7 After attach USB HDD ls /dev/evms/sd* /dev/evms/sdb I don't understand why it is under evms. Was this disk a part of a logical volume disk at some time? I would suggest to use a disk utility and wipe the drive, then try again. -- Joe Morris Registered Linux user 231871 running openSUSE 10.2 x86_64 -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] Re: USB device error
On Sunday 17 June 2007 19:21, Joe Morris (NTM) wrote: Philip Kisloff wrote: Before attach USB HDD ls /dev/evms/sd* ls: cannot access /dev/evms/sd*: No such file or directory ls /dev/sd* /dev/sda /dev/sda1 /dev/sda2 /dev/sda3 /dev/sda5 /dev/sda6 /dev/sda7 After attach USB HDD ls /dev/evms/sd* /dev/evms/sdb I don't understand why it is under evms. Was this disk a part of a logical volume disk at some time? I would suggest to use a disk utility and wipe the drive, then try again. -- Joe Morris The /dev/evms is puzzle for me too. I don't use it so my knowledge is only from here: http://evms.sourceforge.net/ and I really don't want to learn much about it for single or double disk computers that I use at the moment. To wipe off the disk what has to be used: dd if=/dev/zero of=/dev/evms/sdb bs=512 count=1 that will take care of MBR or dd if=/dev/zero of=/dev/evms/sdb bs=1M that will take care of whole disk. -- Regards, Rajko. -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] Re: USB device error
On Sat, 2007-06-16 at 16:31 +0100, Philip Kisloff wrote: I guess you want to mount the first partition of your disk. Try mount /dev/sdb1 /mnt/usb Hi Herbet, Thanks for the reply. I hoped it was going to be a doh! moment there. mount /dev/sdb1 /mnt/usb mount: special device /dev/sdb1 does not exist Do you happen to have anything in your /dev directory for sda? However, you're right to assume I'm a newbie, because I am :(/. I've not been able to partition the external disk, but was thinking I had to mount it first for even that. You want the partition to mount, not the actual disk. What you are seeing here is that your system does not see the partitions on /dev/sdb, and seeing as /dev/sdb1 ought to exist on the partitioned drive, it is either not partitioned, or not connected in a way that the OS sees it. The first thing to iron out is having it connected and powered up properly. You will know your successful when you cycle the power on and the SuSE hardware detection window pops up, click cancel, do not mount it if you wish to partition it. I have an USB enclosure for a 200G drive. I did the partitioning on this from the command line the first time I set it up using fdisk. Fdisk is a great tool if you know your way around partitioning, but most folks do not, so gui tools are usually preferable. YaST has a disk partitioning tool that is relatively easy to figure out, it's on the system tab, partitioner. If you use that tool read the warning that pops up, then accept it. It should have a listing of all the drives that are attached and recognized, and a USB drive is normally (to my knowledge) appears as /dev/sb(letter) as it appears above. Once invoked you ought to see a description along the lines of /dev/sd(letter) and a description of the hardware (e.g. Maxtor model#..). The first letter used is a, the second b, etc. The two options in the partitioner that that will be of use to you the most, are Create, and Edit. Have a look at the tool, and if you have questions, ask. -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] Re: USB device error
On Sat, 2007-06-16 at 22:06 +0100, Philip Kisloff wrote: No luck yet, I'm afraid - Phil Do you happen to have anything in your /dev directory for sda? Yes, in /dev/disk, I have sda1, sda2, sda3, sda5, sda6, sda7 and sdb. Ok, so the new drive is /dev/sdb, and is being recognized as not being parittioned. You will know your successful when you cycle the power on and the SuSE hardware detection window pops up. Unfortunately, no hardware detection popped up. I got the following in /var/log/messages: Works just as well, just is more work. Jun 16 19:52:53 inspiron kernel: usb 6-1: new high speed USB device using ehci_hcd and address 2 Jun 16 19:52:53 inspiron kernel: usb 6-1: new device found, idVendor=14cd, idProduct=6600 Jun 16 19:52:53 inspiron kernel: usb 6-1: new device strings: Mfr=1, Product=3, SerialNumber=2 Jun 16 19:52:53 inspiron kernel: usb 6-1: Product: USB 2.0 IDE DEVICE Jun 16 19:52:53 inspiron kernel: usb 6-1: Manufacturer: Super Top Jun 16 19:52:53 inspiron kernel: usb 6-1: SerialNumber: ?? Jun 16 19:52:53 inspiron kernel: usb 6-1: configuration #1 chosen from 1 choice Jun 16 19:52:53 inspiron kernel: Initializing USB Mass Storage driver... Jun 16 19:52:53 inspiron kernel: scsi4 : SCSI emulation for USB Mass Storage devices Jun 16 19:52:53 inspiron kernel: usb-storage: device found at 2 Jun 16 19:52:53 inspiron kernel: usb-storage: waiting for device to settle before scanning Jun 16 19:52:53 inspiron kernel: usbcore: registered new driver usb-storage Jun 16 19:52:53 inspiron kernel: USB Mass Storage support registered. Jun 16 19:52:54 inspiron kernel: Vendor: Hitachi Model: HTS541210H9AT00 Rev: 0 0 Jun 16 19:52:54 inspiron kernel: Type: Direct-Access ANSI SCSI revision: 00 Jun 16 19:52:54 inspiron kernel: SCSI device sdb: 195371568 512-byte hdwr sectors (100030 MB) Jun 16 19:52:54 inspiron kernel: sdb: Write Protect is off Jun 16 19:52:54 inspiron kernel: sdb: Mode Sense: 03 00 00 00 Jun 16 19:52:54 inspiron kernel: sdb: assuming drive cache: write through Jun 16 19:52:54 inspiron kernel: SCSI device sdb: 195371568 512-byte hdwr sectors (100030 MB) Jun 16 19:52:54 inspiron kernel: sdb: Write Protect is off Jun 16 19:52:54 inspiron kernel: sdb: Mode Sense: 03 00 00 00 Jun 16 19:52:54 inspiron kernel: sdb: assuming drive cache: write through Jun 16 19:52:55 inspiron kernel: sdb:6sd 4:0:0:0: SCSI error: return code = 0x1007 Jun 16 19:52:55 inspiron kernel: end_request: I/O error, dev sdb, sector 0 Jun 16 19:52:55 inspiron kernel: Buffer I/O error on device sdb, logical block 0 Jun 16 19:52:55 inspiron kernel: sd 4:0:0:0: SCSI error: return code = 0x1007 Jun 16 19:52:55 inspiron kernel: end_request: I/O error, dev sdb, sector 0 Jun 16 19:52:55 inspiron kernel: Buffer I/O error on device sdb, logical block 0 Jun 16 19:52:55 inspiron kernel: sd 4:0:0:0: SCSI error: return code = 0x1007 Jun 16 19:52:55 inspiron kernel: end_request: I/O error, dev sdb, sector 0 Jun 16 19:52:55 inspiron kernel: Buffer I/O error on device sdb, logical block 0 Jun 16 19:52:55 inspiron kernel: unable to read partition table Jun 16 19:52:55 inspiron kernel: sd 4:0:0:0: Attached scsi disk sdb Jun 16 19:52:55 inspiron kernel: sd 4:0:0:0: Attached scsi generic sg1 type 0 Jun 16 19:52:55 inspiron kernel: usb-storage: device scan complete Jun 16 19:52:55 inspiron kernel: sd 4:0:0:0: SCSI error: return code = 0x1007 Jun 16 19:52:55 inspiron kernel: end_request: I/O error, dev sdb, sector 195371392 I'm not sure about the error, but I'd venture a guess that it relates to the partitioning. Using yast partitioner, it detected /dev/evms/sdb. Trying to partition it gives me the following error: ERROR Failure occured during the followng action: Mouting /dev/evms/sdb to /mnt/usb We do not want to try mounting it at this time, that will be done _after_ it's partitioned. Locate the /dev/evms/sdb in YaST partitioner and click on the Create button to create a partition. It's a good idea to think about how many partitions you want for this drive, based on what you want to do with it, as well as what kind of file system type. I'd use the same file system type as for your install, just to keep it simple for now. System error code was: -3003 mount-t auto /dev/evms/sdb to /mnt/usb: mount: /dev/evms/sdb: can't read superblock. Like I said earlier, partition first then mount, and then you will be using (assuming one partition on the disk): mount-t auto /dev/evms/sdb1 /mnt/usb no _to_ and sdb1 as opposed to sdb -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] Re: USB device error
On Saturday 16 June 2007 10:31, Philip Kisloff wrote: However, you're right to assume I'm a newbie, because I am :(/. I've not been able to partition the external disk, but was thinking I had to mount it first for even that. If you have no much experience and want to partition external HD you are good advised to use YaST -- System -- Partitioner. It is more verbose than command line tools and although it is in the moment designed for users that are familiar with Linux terminology, like /dev/sda, /dev/sda1, /dev/sda5 etc, it will help you to create partitions without knowing much more details. BTW, if you want to learn how to use command line tools, that can give you more of direct control you may look in the article: http://en.opensuse.org/Linux_Documentation and http://en.opensuse.org/Manual_Pages I started idea to describe various sources of information traditional to Linux that I found extremely useful when I was new user, but no one picked up since than :-( -- Regards, Rajko. -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
