Suse 9.1 personal vfat drive switches to read-only

  • marsman
  • Born
  • Born
  • marsman
  • Posts: 3

Post 3+ Months Ago

Cii on this forum previously had a similar problem. I'm running Suse 9.1 personal on a Dell Latitude C840 with two Windows partitions C and E. The other day I did my first command line cd burning (K3b broken, have a *plum* 24x UDJA360 CD-RW, in case its relevant), and the partition was working fine before this. On a fresh boot I can create and delete files and folders on C and E, but then either trying to delete particular folders or just randomly, it advises that E is a 'Read-only file system' (C still seems to write ok), in both cases as normal user and root. Its weird because they still seem to be mounted normally. I upgraded to KDE 3.3.2 a few months ago. Any help appreciated...

marsman

# mount
/dev/hda4 on / type reiserfs (rw,acl,user_xattr)
proc on /proc type proc (rw)
tmpfs on /dev/shm type tmpfs (rw)
devpts on /dev/pts type devpts (rw,mode=0620,gid=5)
/dev/hda6 on /linux1 type reiserfs (rw)
/dev/hda1 on /windows/C type vfat (rw,noexec,nosuid,nodev,umask=0000,dmask=0000,uid=0002,gid=100,iocharset=utf8)
/dev/hda2 on /windows/E type vfat (rw,noexec,nosuid,nodev,umask=0000,dmask=0000,uid=0002,gid=100,iocharset=utf8)
/dev/sr0 on /media/cdrecorder type subfs (ro,nosuid,nodev,fs=cdfss,procuid,iocharset=utf8)
/dev/fd0 on /media/floppy type subfs (rw,nosuid,nodev,sync,fs=floppyfss,procuid)
/dev/sr0 on /media/cdrom type subfs (ro,nosuid,nodev,fs=cdfss,procuid,iocharset=utf8)
usbfs on /proc/bus/usb type usbfs (rw)

> more /etc/fstab
/dev/hda4 / reiserfs acl,user_xattr 1 1
/dev/hda6 /linux1 reiserfs defaults 0 0
/dev/hda1 /windows/C vfat umask=0000,dmask=0000,uid=0002,gid=users,users,iocharset=utf8 0 0
/dev/hda2 /windows/E vfat umask=0000,dmask=0000,uid=0002,gid=users,users,iocharset=utf8 0 0
/dev/hda5 swap swap pri=42 0 0
devpts /dev/pts devpts mode=0620,gid=5 0 0
proc /proc proc defaults 0 0
usbfs /proc/bus/usb usbfs noauto 0 0
sysfs /sys sysfs noauto 0 0
/dev/cdrecorder /media/cdrecorder subfs fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0
/dev/fd0 /media/floppy subfs fs=floppyfss,procuid,nodev,nosuid,sync 0 0

/dev/cdrom /media/cdrom subfs fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0

/windows> ls -al
total 49
drwxr-xr-x 4 root root 144 2004-06-30 07:19 .
drwxr-xr-x 20 root root 536 2005-05-06 08:32 ..
lrwxrwxrwx 1 root root 1 2004-06-30 07:19 c -> C
drwxrwxrwx 30 daemon users 32768 2005-05-06 10:01 C
lrwxrwxrwx 1 root root 1 2004-06-29 09:28 e -> E
drwxrwxrwx 17 daemon users 16384 1970-01-01 10:00 E
  • Anonymous
  • Bot
  • No Avatar
  • Posts: ?
  • Loc: Ozzuland
  • Status: Online

Post 3+ Months Ago

  • marsman
  • Born
  • Born
  • marsman
  • Posts: 3

Post 3+ Months Ago

Sorry to post reply to my own message, but have some more information...

I'm wondering if SCSI emulation may be my related to my problem. I modified some settings according to:

http://www-106.ibm.com/developerworks/l ... dburn.html

and will now remove them and see if that makes a difference... here are the settings files with SCSI emulation:

> more /etc/modules.conf
ide-cd ignore=\"hdb\"
ide-scsi

(this file was previously empty)

# more /boot/grub/menu.lst
# Modified by YaST2. Last modification on Mon Jun 28 00:06:32 2004


color white/blue black/light-gray
default 0
timeout 8
gfxmenu (hd0,3)/boot/message

###Don't change this comment - YaST2 identifier: Original name: linux###
title Linux
kernel (hd0,3)/boot/vmlinuz root=/dev/hda4 vga=0x317 splash=silent desktop resume=/dev/hda5 showopts hdb=scsi
initrd (hd0,3)/boot/initrd

###Don't change this comment - YaST2 identifier: Original name: windows###
title Windows
root (hd0,0)
chainloader +1

###Don't change this comment - YaST2 identifier: Original name: floppy###
title Floppy
root (fd0)
chainloader +1

###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe
kernel (hd0,3)/boot/vmlinuz root=/dev/hda4 showopts ide=nodma apm=off acpi=off vga=normal noresume nosmp noapic maxcpus=0 3
initrd (hd0,3)/boot/initrd
  • pclovers
  • Graduate
  • Graduate
  • User avatar
  • Posts: 155
  • Loc: Nagpur, India

Post 3+ Months Ago

Have u unmount and mount these partition.

First unmount the partition then mount it again with read write option on another folder.
This will solve problem.
  • marsman
  • Born
  • Born
  • marsman
  • Posts: 3

Post 3+ Months Ago

Ok, thanks, I will try that
marsman

Post Information

  • Total Posts in this topic: 4 posts
  • Users browsing this forum: No registered users and 34 guests
  • You cannot post new topics in this forum
  • You cannot reply to topics in this forum
  • You cannot edit your posts in this forum
  • You cannot delete your posts in this forum
  • You cannot post attachments in this forum
 
 

© 1998-2014. Ozzu® is a registered trademark of Unmelted, LLC.