On Saturday 23 December 2006 23:02, Mike Noble wrote:
> On Saturday 23 December 2006 13:23, Primm wrote:
> > On Saturday 23 December 2006 22:00, Mike Noble wrote:
> > > On Saturday 23 December 2006 09:27, Primm wrote:
> > > > On Saturday 23 December 2006 18:04, Hans du Plooy wrote:
> > > > > On Sat, 2006-12-23 at 16:42 +0100, Primm wrote:
> > > > > > I have a zaapa usb external drive. I thought I could simply plug
> > > > > > it in and write to it. It does not show up under the kde 'my
> > > > > > computer' as I expected it would. Running evmsgui it shows as
> > > > > > /dev/evms/sda but I've no idea how to write to it. Why doesn't it
> > > > > > simply show as /dev/sda? How can I get to use it?
> > > > >
> > > > > Open a console as root and type:
> > > > >
> > > > > # fdisk -l
> > > > >
> > > > > Does it only show /dev/sda or is there a /dev/sda1 too?  If there
> > > > > is only /dev/sda it means that there are no partitions on the disc.
> > > > > You can use fdisk to create a partition, then format ti with the
> > > > > filesystem of your choice.
> > > > >
> > > > > Hans
> > > >
> > > > it gives me this:
> > > >
> > > >  fdisk -l
> > > >
> > > > Disk /dev/hda: 100.0 GB, 100030242816 bytes
> > > > 255 heads, 63 sectors/track, 12161 cylinders
> > > > Units = cylinders of 16065 * 512 = 8225280 bytes
> > > >
> > > >    Device Boot      Start         End      Blocks   Id  System
> > > > /dev/hda1               1         383     3076416   12  Compaq
> > > > diagnostics /dev/hda2   *         384        6258    47190937+   c 
> > > > W95 FAT32 (LBA) /dev/hda3            6259       12161    47415847+  
> > > > f  W95 Ext'd (LBA) /dev/hda5            6259        8228    15823993+
> > > >   b  W95 FAT32 /dev/hda6            8229        8356     1028128+  82
> > > >  Linux swap / Solaris /dev/hda7            8357       12161   
> > > > 30563631   83 Linux
> > > >
> > > > Disk /dev/dm-0: 3150 MB, 3150249984 bytes
> > > > 255 heads, 63 sectors/track, 382 cylinders
> > > > Units = cylinders of 16065 * 512 = 8225280 bytes
> > > >
> > > > This doesn't look like a partition table
> > > > Probably you selected the wrong device.
> > > >
> > > >      Device Boot      Start         End      Blocks   Id  System
> > > > /dev/dm-0p1   ?      120513      235786   925929529+  68  Unknown
> > > > Partition 1 has different physical/logical beginnings (non-Linux?):
> > > >      phys=(116, 100, 32) logical=(120512, 47, 32)
> > > > Partition 1 has different physical/logical endings:
> > > >      phys=(288, 101, 46) logical=(235785, 20, 46)
> > > > Partition 1 does not end on cylinder boundary.
> > > > /dev/dm-0p2   ?       82801      116350   269488144   79  Unknown
> > > > Partition 2 has different physical/logical beginnings (non-Linux?):
> > > >      phys=(357, 32, 43) logical=(82800, 34, 51)
> > > > Partition 2 has different physical/logical endings:
> > > >      phys=(0, 13, 10) logical=(116349, 218, 61)
> > > > Partition 2 does not end on cylinder boundary.
> > > > /dev/dm-0p3   ?       33551      120595   699181456   53  OnTrack DM6
> > > > Aux3 Partition 3 has different physical/logical beginnings
> > > > (non-Linux?): phys=(345, 32, 19) logical=(33550, 137, 11)
> > > > Partition 3 has different physical/logical endings:
> > > >      phys=(324, 77, 19) logical=(120594, 153, 54)
> > > > Partition 3 does not end on cylinder boundary.
> > > > /dev/dm-0p4   ?       86812       86813       10668+  49  Unknown
> > > > Partition 4 has different physical/logical beginnings (non-Linux?):
> > > >      phys=(87, 1, 0) logical=(86811, 142, 3)
> > > > Partition 4 has different physical/logical endings:
> > > >      phys=(335, 78, 2) logical=(86812, 225, 45)
> > > > Partition 4 does not end on cylinder boundary.
> > > >
> > > > Partition table entries are not in disk order
> > > >
> > > > Disk /dev/dm-1: 48.3 GB, 48323520000 bytes
> > > > 255 heads, 63 sectors/track, 5875 cylinders
> > > > Units = cylinders of 16065 * 512 = 8225280 bytes
> > > >
> > > > This doesn't look like a partition table
> > > > Probably you selected the wrong device.
> > > >
> > > >      Device Boot      Start         End      Blocks   Id  System
> > > > /dev/dm-1p1   ?      116388      126889    84344761   69  Unknown
> > > > Partition 1 does not end on cylinder boundary.
> > > > /dev/dm-1p2   ?      105915      222310   934940732+  73  Unknown
> > > > Partition 2 does not end on cylinder boundary.
> > > > /dev/dm-1p3   ?           1           1           0   74  Unknown
> > > > Partition 3 does not end on cylinder boundary.
> > > > /dev/dm-1p4          179626      179629       26207+   0  Empty
> > > > Partition 4 does not end on cylinder boundary.
> > > >
> > > > Partition table entries are not in disk order
> > > >
> > > > Any ideas?
> > > > Thanks Steve.
> > >
> > > I have a drive that connects with usb (use it for backups).  This is a
> > > stanard drive in a usb enclosure, and here is the output of my
> > > fdisk -l:
> > >
> > > fdisk -l
> > >
> > > Disk /dev/hda: 200.0 GB, 200049647616 bytes
> > > 255 heads, 63 sectors/track, 24321 cylinders
> > > Units = cylinders of 16065 * 512 = 8225280 bytes
> > >
> > >    Device Boot      Start         End      Blocks   Id  System
> > > /dev/hda1   *           1        2611    20972826   83  Linux
> > > /dev/hda2            2612        3917    10490445   82  Linux swap /
> > > Solaris /dev/hda3            3918       24321   163895130   83  Linux
> > >
> > > Disk /dev/sda: 400.0 GB, 400088457216 bytes
> > > 255 heads, 63 sectors/track, 48641 cylinders
> > > Units = cylinders of 16065 * 512 = 8225280 bytes
> > >
> > >    Device Boot      Start         End      Blocks   Id  System
> > > /dev/sda1               1       48641   390708801   83  Linux
> > >
> > > Your system sees the drive as /dev/dm-0px, where x is the partition
> > > on the drive.  You also show a /dev/dm-1px.  This really looks like the
> > > disk was setup by some kind of disk manager.  If you are able to run
> > > fdisk on /dev/dm-0 and /dev/dm-1 then you can probably delete the
> > > partitions and create one big one in each of the virtual drives.  Word
> > > of warning if you do this the drive will most likely not be able to be
> > > returned.  If you are already at that point, then there is no harm in
> > > trying.
> > >
> > > Mike
> >
> > Unfortunately not:
> >
> > fdisk /dev/dm-0
> >
> > Unable to read /dev/dm-0
> > Still no joy.
> > Steve.
>
> Are you able to return the drive and get a different one?
>
> Mike

Yes. That's what I've decided to do.

Thanks to all for helping me come to this decision.
Steve

-- 
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to