I have a small scsi memory disk device that my computer claims is a /dev/sda mount type.. and I have mounted it in the past.. but I just recently reinstalled my whole system to check out a couple of things on my database. including the scsi device and now I can't get it to mount.. i tried to mount it in windows i get a com1 not available message.. I have windows mounted on my linux and niether seem to be working..
i tried this
mount -t vfat /dev/sda1 /usbdrive/
"no such device"
mount -t nfs /dev/sda /usbdrive/
"mount not mounted on host:dir"
i have alot of information on the device and need to download it to the system and then format it.. any ideas??
any feedback welcome
thanx moxxx68

__________________
moxxx68
http://www.estarinformado.com.ar/apicmaxmiel/bee-diez.gif

I think you need to have the scsi module built in the kernel.

Run 'dmesg|less' and see if your sda is actually recognized by your Linux box.

it says it recognizes it..
scsi sda mass storage device>>>
by the way
thanx for answering and welcome... to Unix.com

__________________
moxxx68
http://www.estarinformado.com.ar/apicmaxmiel/bee-diez.gif

Thanks.

With "scsi sda mass storage device>>>", does it tell any partition just after it?

You can always check with /proc/partitions to make sure.
fdisk -l would do too.

it says something about sectors... and 125mb storage capability but thats as far as I can make of it.. I am still a little new to unix in certain areas.. ..

__________________
moxxx68
http://www.estarinformado.com.ar/apicmaxmiel/bee-diez.gif

If you do an 'fdisk /dev/sda' and then type 'p' to display the partitions, what do you see?

Taking the answers from above, are you able to run fsck against the partitions?

unable to open /dev/sda ...
and if i fsck it
i get this:
/sbin/fsck /dev/sda
fsck 1.35 (28-Feb-2004)
e2fsck 1.35 (28-Feb-2004)
fsck.ext2: No such file or directory while trying to open /dev/sda

The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>

__________________
moxxx68
http://www.estarinformado.com.ar/apicmaxmiel/bee-diez.gif