Folks, I've had to reinstall SuSE 10.0 on my Toshiba Satellite 1905-303S. Previously, the machine automatically picked up either the USB drive (Maxtor One Touch II 300 gb) or my iRiver mp3 player via usb without any prompting from me. Now, however, when I plug either in, SuSE doesn't see it. When I do an fdisk -l /de/sda, it returns: /dev/sda doesn't have a valid partition table. When I "hotplug" the drive and run dmesg, SuSE clearly registers the drive, but, again it shows an "unknown partition table," then some interesting entries: FAT: bogus logical sector size 48 VFS: Can't find a valid FAT filesystem on dev sda. VFS: Can't find an ext2 filesystem on dev sda. VFS: Can't find a Minix or Minix V2 filesystem on device sda. HFS+-fs: unable to find HFS+ superblock subfs: unsuccessful attempt to mount media (256) usb 1-2: USB disconnect, address 7 usb 1-2.4: USB disconnect, address 8 usb 1-2.7: USB disconnect, address 9 drivers/usb/class/usblp.c: usblp0: removed hub 1-0:1.0: over-current change on port 2 usb 1-2: new full speed USB device using uhci_hcd and address 10 hub 1-2:1.0: USB hub found hub 1-2:1.0: 7 ports detected usb 1-2.4: new full speed USB device using uhci_hcd and address 11 scsi3 : SCSI emulation for USB Mass Storage devices usb-storage: device found at 11 usb-storage: waiting for device to settle before scanning usb 1-2.7: new full speed USB device using uhci_hcd and address 12 drivers/usb/class/usblp.c: usblp0: USB Bidirectional printer dev 12 if 0 alt 0 proto 2 vid 0x03F0 pid 0x8204 Vendor: Maxtor Model: OneTouch II Rev: 023g Type: Direct-Access ANSI SCSI revision: 04 SCSI device sda: 586114704 512-byte hdwr sectors (300091 MB) sda: assuming drive cache: write through SCSI device sda: 586114704 512-byte hdwr sectors (300091 MB) sda: assuming drive cache: write through sda: unknown partition table Attached scsi disk sda at scsi3, channel 0, id 0, lun 0 Attached scsi generic sg0 at scsi3, channel 0, id 0, lun 0, type 0 usb-storage: device scan complete One final, gulp, observation. I used the Yast2 partitioner to see what it could tell me about what already may be existing on the two drives. When I aimed it at the Maxtor, the entire disk read, gulp, "free." The iRiver, by contrast, shows an existing FAT32. Why do I think I can guess the answer to this already? :-/ If I've inadvertantly trashed the Maxtor, any recommendations on the best file format to use to partition it? Sigh... With best regards, Pete
Peter N. Spotts wrote:
usb-storage: device found at 11 usb-storage: waiting for device to settle before scanning usb 1-2.7: new full speed USB device using uhci_hcd and address 12 drivers/usb/class/usblp.c: usblp0: USB Bidirectional printer dev 12 if 0 alt 0 proto 2 vid 0x03F0 pid 0x8204 Vendor: Maxtor Model: OneTouch II Rev: 023g Type: Direct-Access ANSI SCSI revision: 04 SCSI device sda: 586114704 512-byte hdwr sectors (300091 MB) sda: assuming drive cache: write through SCSI device sda: 586114704 512-byte hdwr sectors (300091 MB) sda: assuming drive cache: write through sda: unknown partition table Attached scsi disk sda at scsi3, channel 0, id 0, lun 0 Attached scsi generic sg0 at scsi3, channel 0, id 0, lun 0, type 0 usb-storage: device scan complete
So the disk is working fine and is available as /dev/sda.
One final, gulp, observation. I used the Yast2 partitioner to see what it could tell me about what already may be existing on the two drives. When I aimed it at the Maxtor, the entire disk read, gulp, "free." The iRiver, by contrast, shows an existing FAT32. Why do I think I can guess the answer to this already? :-/
If I've inadvertantly trashed the Maxtor, any recommendations on the best file format to use to partition it? Sigh...
If you know more or less what it's partition-format was, you could simply try to recreate it - i.e. if the entire stick was used for one partition, just use fdisk to recreate that. Then try to mount /dev/sda1. File-system - if you need to reformat - depends on what you use it for - if you need to exchange with multiple operating system, e.g. Linux and Windows, pick the lowest common denominator. Probably VFAT. /Per Jessen, Zürich
Thanks...my biggest concern with the "free" label is that somehow I inadvetantly wiped the disk clean...it was my backup while I was reintalling SuSE...So I guess I need someone else to confirm the bad news before I repartition the drive and (if I haven't already) lose everything on it... Pete
Peter N. Spotts wrote:
Thanks...my biggest concern with the "free" label is that somehow I inadvetantly wiped the disk clean...it was my backup while I was reintalling SuSE...
It's possible that it was only the partition-table that got wiped, hence my suggestion to try to repartition. As long as you don't reformat, repartitioning won't destroy anything. /Per Jessen, Zürich
On Wed, 12 Apr 2006 20:35:10 +0200 Per Jessen <per@computer.org> wrote:
Peter N. Spotts wrote:
Thanks...my biggest concern with the "free" label is that somehow I inadvetantly wiped the disk clean...it was my backup while I was reintalling SuSE...
It's possible that it was only the partition-table that got wiped, hence my suggestion to try to repartition. As long as you don't reformat, repartitioning won't destroy anything.
/Per Jessen, Zürich
Thanks! Pete
I had a similar problem. What I did was add the disk using the yast partitioner but without reformatting. Then I manually changed the entries in /etc/fstab to use the correct filesystem and use the proper options. It worked. I hope you haven't reformatted your drive yet. On Wednesday 12 April 2006 14:36, Peter N. Spotts wrote:
On Wed, 12 Apr 2006 20:35:10 +0200
Per Jessen <per@computer.org> wrote:
Peter N. Spotts wrote:
Thanks...my biggest concern with the "free" label is that somehow I inadvetantly wiped the disk clean...it was my backup while I was reintalling SuSE...
It's possible that it was only the partition-table that got wiped, hence my suggestion to try to repartition. As long as you don't reformat, repartitioning won't destroy anything.
/Per Jessen, Zürich
Thanks!
Pete
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Wednesday 2006-04-12 at 20:35 +0200, Per Jessen wrote:
It's possible that it was only the partition-table that got wiped, hence my suggestion to try to repartition. As long as you don't reformat, repartitioning won't destroy anything.
gpart can be used to "guess" what the partition table was, and recreate it later. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFEPZ5JtTMYHG2NR9URAtGJAJ97BE3O7qwWU33bw9m75B9HsQK1CACfT8Nv hBQMwxQngyWZ5PVa4sN8+hI= =mkdL -----END PGP SIGNATURE-----
participants (4)
-
Andres Mejia -
Carlos E. R. -
Per Jessen -
Peter N. Spotts