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:<6>sd 4:0:0:0: SCSI error: return > code = 0x10070000 > 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 = > 0x10070000 > 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 = > 0x10070000 > 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 = > 0x10070000 > 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]
