(OLD) (ARCHIVED) Puppy Linux Discussion Forum

[totolanio]

Hello,

Everytime I use my USB stick on puppy, it's read only.
It wasn't the case months ago.

Very annoying.

What can I do ?

[MochiMoppel]

File system is FAT32? Happened to me twice.

You could try to repair the corrupt fs with Puppy (I tried with command fsck /dev/sdb1, but never succeeded), or you could try to use the stick on a Windows machine. I think in XP it was Right-click - Properties - Tools -Scan for bad sectors. This did the trick for me. After all MS should know best how to repair its own creation

[totolanio]

Yes its fat32 (i thought it was ntfs but no).

I also read on this forum that I can simply move all files and reformat it. Would it happen with NTFS ?

[MochiMoppel]

[totolanio]

is ntfs more prone to corruption than fat32 or less?

[drunkjedi]

NTFS being a journaling FS is better than fat32.
But if you use that usb stick to connect to music system or TV etc, then they will not probably recognize NTFS.
So better keep it Fat32.

I think fsck also has options to detect and repair bad sectors.
Got to search...

[drunkjedi]

http://ubuntuforums.org/showthread.php?t=1203357
http://askubuntu.com/questions/147228/how-to-repair-a-corrupted-fat32-file-system
So we need fsck.vfat command for fat32 fs.
Or testdisk is also recommended.

[Burn_IT]

It depends very much on your use and requirements.
If you are transferring a lot of data to none known devices - then FAT32 or FATExt are better since they are more widely read - though this is less a problem nowadays.
If you are repeatedly writing to the USB Fat32 and FATExt will use up the write cycles more slowly since each NTFS write uses extra cycles for the journal as well.
If You are writing seldom, but reading a lot then NTFS is the way to go especially with many small files.
Of course none of this explains why it has suddenly become read only, though there IS a bit (flag) than can be set to make it do this. on some sticks.

[Flash]

I had some kind of problem with a couple of FAT-32 flash drives, I can't remember if Puppy said they were "read-only" or what, but Gparted found that the boot flag was set, which I didn't need, and the problem went away after removing the boot flag with Gparted.

[Burn_IT]

The boot flag/bit and the read/write bit are different bits - though they may well exist within the same byte so if either is set using the wrong technique, the other could easily be affected.

[nic007]

I have an mmc card stuck in read only. Also FAT32, not even Windows can fix it. Even tried some "registry trick" I found on the internet, zilts, nothing works.

[nic007]

[Burn_IT]

Quite likely!!

[Mike Walsh]

Hi, totolanio.

May have nothing at all to do with this, but.....your 'stick' isn't a SanDisk Cruzer 'Blade', by any chance?

The reason I ask is because SanDisk had a major manufacturing upset with the 'Blades' a couple or three years ago.....and their advice was that 'there is no 'fix'.' Send it back to them, and get a replacement.

It turned out they'd purchased a huge 'duff' batch of flash controller chips from Hynix, who refused to take them back.....especially since the problem only appeared totally at random. Once the chips went into 'read-only' mode, that was it. There was no solution. The SanDisk forums, at the time, were snowed under with complaints from people with exactly this problem; the outcome being, of course, that there are still hundreds of thousands of these sticks floating around out there in the marketplace.

It seemed to specifically concern the 16 GB models.....although there were reports of some 8 GB models being affected, too.


Mike.

[Flash]