FIle permissions changed after power surge..HELP!!
 

I'm running SUSE 9.0 update to KDE 3.2.2 , I recently had a power surge at my house and now when I access /windows/D drive and try to delete files it says I cannot delete or change permissions. I am logged in as root when attempting this. I have no idea how to fix this. It seems all folders on /windows/D drive cannot be deleted or changed permissions!

Is not about the user but about the permission on the drive. If the drive is mounted as read-only it shall be so :P
Is your drive been mounted at boot time? If so what is the content of your /etc/fstab file ?

Just occurred to me... Might your DOS partitions got corrupted?
You might want to run:
~#: dosfsck /dev/hda
Replace 'hda' for the corresponding HHD.

trying to get it to work still
 

weird thing is files I have been trying to delete somehow get deleted over time. What do I do now?
dosfsck 2.10, 22 Sep 2003, FAT32, LFN
There are differences between boot sector and its backup.
Differences: (offset:original/backup)
71:20/00, 72:20/00, 73:20/00, 74:20/00, 75:20/00, 76:20/00, 77:20/00
, 78:20/00, 79:20/00, 80:20/00, 81:20/00
1) Copy original to backup
2) Copy backup to original
3) No action
?

?what should I do??

fstab
 

/dev/hda2 / reiserfs acl,user_xattr 1 1
/dev/hdb1 /windows/C vfat users,gid=users,umask=0002,iocharset=utf8 0 0
/dev/hde1 /windows/D vfat users,gid=users,umask=0002,iocharset=utf8 0 0
/dev/hda1 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/dvd /media/dvd 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

dunno what to do... still learning myself after 2 years.

Re: FIle permissions changed after power surge..HELP!!
 

Seems to me that the first thing we want to know is what are the actual permissions on the files in question.

Who actually owns them? What permissions do they now have? Look at them in a file manager and see.

Also, do these files operate properly under Windows? You may need to run ScanDisk or something to fix this error on the Windows side first.

Hope this helps.