durbnpoisn

Group: Members
Posts: 47
Joined: Dec. 2004 |
 |
Posted: Mar. 20 2007,16:33 |
 |
Status on this issue...
Where /dev/sda1 used to be the location of my USB, now that I'm running from the hard drive, evidently /dev/uba1 is where the device resides now.
I edited the /ect/fstab file, added in an entry like so: /dev/uba1 /mnt/usbhd usbfs noauto,users,exec,0 0
Mounting using either the mount app, or from Bash has the same effect. Basically, ls /mnt/usbhd returns two things: 001 devices
Clearly the mount command is doing something. But, it's not mounting the USB key.
I've tried a few variations on the filesystem, like vfat or auto. Anything like that causes mount to return that /dev/uba1 is not a valid block device.
So... I'm at a loss... And what really baffles me is that mounting /dev/sda1 worked just fine when running from the CD. I guess that has something to do with running from a RAM drive as opposed to an actual HD installation.
Any help here would be hot.
|