Mandriva 2006 & Usb Drives

[tazno1]

Hello,
I'm a newbie to the linux world
I tried Looking for my ansewer on your site but i have not fount it.

I have two Usb Drives both Maxtors
80.Gig and a 120 Gig Drive.
they both show in the devices folder, both show as mounted but when I try to look inside them it gives me the follow errors

"could not enter folder /mnt/" then it gives the name of the drive I try to enter

i try to edit the permissions on the drives but when trying to apply the chages it gives me the sam error

"could not enter folder /mnt/" then it gives the name of the drive I try to enter

So if any of you almighty Linux People can help me out.

[slider_609]

Hello,
I'm a newbie to the linux world
I tried Looking for my ansewer on your site but i have not fount it.

I have two Usb Drives both Maxtors
80.Gig and a 120 Gig Drive.
they both show in the devices folder, both show as mounted but when I try to look inside them it gives me the follow errors

"could not enter folder /mnt/" then it gives the name of the drive I try to enter

i try to edit the permissions on the drives but when trying to apply the chages it gives me the sam error

"could not enter folder /mnt/" then it gives the name of the drive I try to enter

So if any of you almighty Linux People can help me out.

Post your /etc/fstab file for us to have a look at.

Randy

[tazno1]

Hi Randy
Here is that log you asked for

# This file is edited by fstab-sync - see 'man fstab-sync' for details
/dev/hdb1 / ext3 defaults 1 1
/dev/hdb6 /home ext3 defaults 1 2
/dev/hdc /mnt/cdrom auto umask=0,user,iocharset=iso8859-1,codepage=850,noauto,ro,exec,users 0 0
none /mnt/floppy supermount dev=/dev/fd0,fs=ext2:vfat,--,umask=0,iocharset=iso8859-1,sync,codepage=850 0 0
/dev/hda1 /mnt/windows ntfs umask=0,nls=iso8859-1,ro 0 0
none /proc proc defaults 0 0
/dev/hdb5 swap swap defaults 0 0
/dev/sda1 /mnt/80_GIG ntfs pamconsole,exec,noauto,utf8,iocharset=iso8859-1,managed 0 0
/dev/sdb1 /mnt/BACKUPS ntfs pamconsole,exec,noauto,utf8,iocharset=iso8859-1,managed 0 0

[bigtomrodney]

Two things I there - Have you tried to see the drives as root? I don't see 'users' in the config for those drives. Also - you have those drives formatted as NTFS, which will be read only under linux. IF you instend using them for storage I would recommend formatting them in FAT32 if you will be swapping them between Windows/Linux, or if you think they'll only ever be used under linux maybe ext3 or ResierFS (though never say never, FAT32 is nice and neutral).

[tazno1]

How would i see the the files as root?

lol i cant even see inside the drive in linux,
And i have some large files on them over 4 gigs(like DVD ISOs files) and sorting lage files is not possible in fat32.
and i do plan on using them in both linux and windows xp
any other ideas?

thanks in advace

[bigtomrodney]

Yep I can see how 4GB files would be a problem. To see the files as root just login as root, or launch konqueror/nautilus from a root console and then open those drives. With NTFS the best you can hope for is read only access, as far as I know captive-ntfs doesn't work anymore with current kernels though read-write support is on the way in a later kernel.

[tazno1]

Thanks I would love to try that but....

I tried doing a update with the Mandriva Update options
i only updated the critical updates and resarted the pc

then it only booted in the Bash Command line
I tried Using the
load x command

It tells me that there is some kind of log it tells me to check ,
I would like to post it so you can view but how would I make a copy of it and save it on a floppy so then I can send it to you when I login to windows?

LOL I know I’m a linux newbie!!
I’m sorry if I seem needy
-------------------------------------------------
Thanks you in advance
Fatal server errors:
No screens found
Please consult the x.org foundation support
Htttp://wiki.x.org for help

Please also check the log file at “/var/log/xorg.o.log
For additional information

XIO: Fatal IO error 104 (connection reset by peer)
On x server :0.0 after 0 requested (know processed with events remaining



critical updates