I just bought a 1GB Memorex Travelstick and am having difficulty using it.
I'm running testing and everything seems OK at first: I get the
kernel messages telling me that the stick is recognised, gives me the
vendor and suchlike, tells me that SCSI device sda has 2007040 51-12
byte hdwr sectors
On 7/16/05, Steffen Waldherr <[EMAIL PROTECTED]> wrote:
> the correct format to call mkfs is
> mkfs -t
> You were trying to create an ext2 file system, which
> is the default if no type is specified.
Whoops! Sorry. I'll blame the hot weather we are having...
--cjc
Hi,
> critter:~# mkfs vfat /dev/sda1
> mke2fs 1.37 (21-Mar-2005)
> mkfs.ext2: bad blocks count - /dev/sda1
the correct format to call mkfs is
mkfs -t
You were trying to create an ext2 file system, which
is the default if no type is specified.
Check man mkfs for more options. Due to the error
m
I attempted formatting and got:
critter:~# mkfs vfat /dev/sda1
mke2fs 1.37 (21-Mar-2005)
mkfs.ext2: bad blocks count - /dev/sda1
Does anybody recognise what this means?
all the best
--Colin
On 7/16/05, L.V.Gandhi <[EMAIL PROTECTED]> wrote:
> On 7/14/05, s. keeling <[EMAIL PROTECTED]> wrote:
>
On 7/14/05, s. keeling <[EMAIL PROTECTED]> wrote:
> Beware, however, others have reported that once reformatted, the stick
> became a paperweight.
Not correct. I have reformatted a few times. Still working OK.
--
L.V.Gandhi
http://lvgandhi.tripod.com/
linux user No.205042
t; also it worked on my colleague's RedHat machine. It is a fairly
>> standard USB memory stick as far as I can see...
>
> Have not read the whole thread in detail, but I just can't imagine, why
> creating a new filesystem (the correct phrase for reformating :) on a
N
s RedHat machine. It is a fairly
> standard USB memory stick as far as I can see...
Have not read the whole thread in detail, but I just can't imagine, why
creating a new filesystem (the correct phrase for reformating :) on a
memory stick should bork it. To the system, after being handled by
> For what it's worth, I have run ``mkfs -t vfat'' on a memory stick once,
> after it had accumulated some weird and (as far as I recall) undeletable
> files (due to a sequence of events involving unplugging without dismounting,
> Windows or Macintosh system freezes, a
(google for HPUSBFW.exe) that seems to work to fix up
> memory sticks, if you run into that problem. Been there, done that. :-)
For what it's worth, I have run ``mkfs -t vfat'' on a memory stick once,
after it had accumulated some weird and (as far as I recall) undeletable
files (d
s. keeling wrote:
> Colin Cotter <[EMAIL PROTECTED]>:
>> On 7/12/05, Steffen Waldherr <[EMAIL PROTECTED]> wrote:
>>
>> > If this doesn't work, you might
>> > want to try "fdisk /dev/sda" to see the partition
>> > table of the stick and maybe repartition and/or
>> > reformat it to your needs.
>
On Wed, Jul 13, 2005 at 11:29:24PM +0200, Colin Cotter wrote:
} I ran hwinfo and got some information which is at the bottom of this
} email. Is the problem something to do with the partition (#42?).
}
} all the best
}
Colin,
I can't help you too much with the partition type, but if you do choo
I ran hwinfo and got some information which is at the bottom of this
email. Is the problem something to do with the partition (#42?).
all the best
--Colin
41: SCSI 00.0: 10600 Disk
[Created at block.190]
Unique ID: PYMB.55V0VYyfGp9
Parent ID: 5YuN.GgZpSc+hxAA
SysFS ID: /block/sda
SysFS
On Tue, Jul 12, 2005 at 07:42:18PM +0200, Colin Cotter wrote:
> On 7/12/05, Steffen Waldherr <[EMAIL PROTECTED]> wrote:
>
> > If this doesn't work, you might
> > want to try "fdisk /dev/sda" to see the partition
> > table of the stick and maybe repartition and/or
> > reformat it to your needs.
> >
On 7/12/05, Steffen Waldherr <[EMAIL PROTECTED]> wrote:
> If this doesn't work, you might
> want to try "fdisk /dev/sda" to see the partition
> table of the stick and maybe repartition and/or
> reformat it to your needs.
>
> Steffen
>
Thanks. My partition table says:
Disk /dev/sda: 252 MB, 252
Hi,
Am Tue, 12 Jul 2005 14:37:41 +0100 schrieb Colin
Cotter <[EMAIL PROTECTED]>:
> critter:/home/colin# mount -t vfat /dev/sda1 /mnt/
>
> mount: wrong fs type, bad option, bad superblock
> on /dev/sda1,
> missing codepage or other error
> In some cases useful info is found in
> mount: wrong fs type, bad option, bad superblock on /dev/sda1,
> missing codepage or other error
> In some cases useful info is found in syslog - try
> dmesg | tail or so
> */
>
> The memory stick works fine under Linux, must be a config problem I think.
>
> --Colin
>
>
esg | tail or so
*/
The memory stick works fine under Linux, must be a config problem I think.
--Colin
On Tue, Jul 12, 2005 at 12:10:03PM +0200, Colin Cotter wrote:
> Dear list,
>
> How do I use a memory stick with Debian? I connected my stick and
> the following appeared in "dmesg". Is it working? How do I access it?
>
> cheers
>
> --cjc
>
>
Dear list,
How do I use a memory stick with Debian? I connected my stick and
the following appeared in "dmesg". Is it working? How do I access it?
cheers
--cjc
usb 4-1: new high speed USB device using address 4
scsi1 : SCSI emulation for USB Mass Storage devices
Vendor:
On Sat, 30 Oct 2004, Curt Howland wrote:
> Hi.
>
> I'm running a Vaio with a memory stick myself. It shows up as a USB
> device in the KDE Infocenter. Make sure that the usb_storage kernel
> module is loaded, at least.
>
> I thought it would show up in dmesg, but I just
the module ehci_hcd... but this
is another discussion, but be aware that this might happen...
>= Original Message From Curt Howland <[EMAIL PROTECTED]> =
>Hi.
>
>I'm running a Vaio with a memory stick myself. It shows up as a USB
>device in the KDE Infocenter. M
Hi.
I'm running a Vaio with a memory stick myself. It shows up as a USB
device in the KDE Infocenter. Make sure that the usb_storage kernel
module is loaded, at least.
I thought it would show up in dmesg, but I just inserted a memory
stick and it didn't show up. However, I have it
Greetings,
does anyone know what kind of device is the memory stick slot on Sony Vaio
PCG-FRV35? it does not seem to be neither usb nor pci; I have Debian unstable
installed, kernel 2.6.7; everything works fine except for the memstick slot,
from which I can see no sign at all.
Thanks,
Antonio
23 matches
Mail list logo
