My Kingston DT 101 II 2GB infected by autorun.inf & gi2ky.exe and becom read-only!!
Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
My Kingston DT 101 II 2GB infected by autorun.inf & gi2ky.exe and becom read-only!!
Hi,
Just like I said in the subject, and it isn't just in Linux, but in Windows XP too! I tried to turn off the write protection by "hdparm -r 0 /dev/sdc1" and "blockdev --setrw /dev/sdc1" but it still read-only file system, even if I try to format it...
for more information:
dmesg
Code:
usb 1-8: new high speed USB device using ehci_hcd and address 38
usb 1-8: configuration #1 chosen from 1 choice
scsi40 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 38
usb-storage: waiting for device to settle before scanning
usb-storage: device scan complete
scsi 40:0:0:0: Direct-Access Kingston DT 101 II PMAP PQ: 0 ANSI: 0 CCS
sd 40:0:0:0: [sdc] 3966976 512-byte hardware sectors: (2.03 GB/1.89 GiB)
sd 40:0:0:0: [sdc] Write Protect is on
sd 40:0:0:0: [sdc] Mode Sense: 23 00 80 00
sd 40:0:0:0: [sdc] Assuming drive cache: write through
sd 40:0:0:0: [sdc] 3966976 512-byte hardware sectors: (2.03 GB/1.89 GiB)
sd 40:0:0:0: [sdc] Write Protect is on
sd 40:0:0:0: [sdc] Mode Sense: 23 00 80 00
sd 40:0:0:0: [sdc] Assuming drive cache: write through
sdc: sdc1
sd 40:0:0:0: [sdc] Attached SCSI removable disk
sd 40:0:0:0: Attached scsi generic sg3 type 0
cat /etc/fstab
Code:
# /etc/fstab: static file system information.
#
# noatime turns off atimes for increased performance (atimes normally aren't
# needed; notail increases performance of ReiserFS (at the expense of storage
# efficiency). It's safe to drop the noatime options if you want and to
# switch between notail / tail freely.
#
# The root filesystem should have a pass number of either 0 or 1.
# All other filesystems should have a pass number of 0 or greater than 1.
#
# See the manpage fstab(5) for more information.
#
# <fs> <mountpoint> <type> <opts> <dump/pass>
# NOTE: If your BOOT partition is ReiserFS, add the notail option to opts.
/dev/sda1 /boot ext3 noauto,noatime 1 2
/dev/sda5 / ext3 noatime 0 1
/dev/sda6 none swap sw 0 0
/dev/sda2 /home ext3 defaults 0 2
/dev/sda7 /tmp ext3 defaults 0 2
/dev/sda8 /var ext3 defaults 0 2
/dev/sda9 /usr ext3 defaults 0 2
/dev/cdrom /mnt/cdrom auto noauto,ro 0 0
/dev/sdc1 /mnt/usbkey auto defaults,noauto,user 0 0
#/dev/fd0 /mnt/floppy auto noauto 0 0
# glibc 2.2 and above expects tmpfs to be mounted at /dev/shm for
# POSIX shared memory (shm_open, shm_unlink).
# (tmpfs is a dynamically expandable/shrinkable ramdisk, and will
# use almost no memory if not populated with files)
shm /dev/shm tmpfs nodev,nosuid,noexec 0 0
Hi, once the system has laoded and everything is settled, look in...
/etc/mtab this file lists the currently mounted filesystems/partitions.
You may find out more about the drive here.
I have tried msdos, fat16 and auto.
These have worked for me....
Code:
/etc/fstab entries (at some time, but not together)....
# Entry for /dev/sdd1 :
UUID=19B0-35D4 /media/NOKIA vfat umask=0,user,noatime,flush 0 0
#Entry for /dev/sdd1 :
UUID=19B0-35D4 /media/nokia vfat fat=16,defaults,user,nosuid,noauto 0 0
#Entry for /dev/sdd1 :
UUID=19B0-35D4 /media/nokia msdos defaults,fat=16,user,nosuid,noauto 0 0
Notice they all have "user" access.
Some of the args in fstab when changed may negate other args.
man fstab
Quote:
DESCRIPTION
The file fstab contains descriptive information about the various file systems.
fstab is only read by programs, and not written; it is the duty of the system admin‐
istrator to properly create and maintain this file. Each filesystem is described on
a separate line; fields on each line are separated by tabs or spaces. Lines starting
with '#' are comments. The order of records in fstab is important because fsck(8),
mount(8), and umount(8) sequentially iterate through fstab doing their thing.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.