Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Location: Somewhere, over the rainbow, way up high
Distribution: Gentoo
Posts: 132
Original Poster
Rep:
ok
i consulted the manual, found the device (/dev/sda) and am attempting to mount it,
but:
[root@zeus mnt]# mount -t ext3 /dev/sda /mnt/usb_hd
mount: wrong fs type, bad option, bad superblock on /dev/sda,
or too many mounted file systems
[root@zeus mnt]#
i try do make a filesystem on /dev/sda but i cant, because mkfs isnt there:;
[root@zeus mnt]# mkfs -t ext3 /dev/sda
bash: mkfs: command not found
If your kernel is not compiled with SCSI support the device will not work.
The following shell session shows my setup. Note the device (/dev/sda1) may be different on your machine. /etc/sysconfig/hwconf theoretically should show the device name (sda1 or whatever it is). I think, however, it is only updated when you boot the machine with the device plugged in which I've never done before to find out if it works.
My device came with a preformatted 'vfat' partition, so you don't need to do mkfs. Your mkfs command only had failed because mkfs was not in your PATH. (try /sbin/mkfs). You probably want to stick with 'vfat' if you want to be able to use it in a windows machine.
FYI: I am running redhat linux 8.0, with 2.4.22-pre6 kernel, with SCSI supported.
I believe I only edited /etc/fstab to add /dev/sda1, and did mkdir /mnt/memstick as root
The disk size is reported correctly by df -k once the mounting is done.
The light flashes slowly after unmounting. I don't know what that means, please post if you find out what it is.
1 0 % cat /etc/fstab
LABEL=/ / ext3 defaults 1 1
LABEL=/boot /boot ext2 defaults 1 2
none /dev/pts devpts gid=5,mode=620 0 0
LABEL=/home /home ext3 defaults 1 2
none /proc proc defaults 0 0
none /dev/shm tmpfs defaults 0 0
LABEL=/usr/local /usr/local ext3 defaults 1 2
/dev/hda6 swap swap defaults 0 0
/dev/fd0 /mnt/floppy auto noauto,owner,kudzu 0 0
/dev/cdrom /mnt/cdrom iso9660 noauto,owner,kudzu,ro 0 0
/dev/sda1 /mnt/memstick auto noauto,owner,user 0 0
2 0 % ls -ld /mnt/memstick /dev/sda1
brw-rw---- 1 root disk 8, 1 Aug 30 2002 /dev/sda1
drwxr-xr-x 2 root disk 4096 Dec 1 17:02 /mnt/memstick
3 0 % mount
/dev/hda2 on / type ext3 (rw)
none on /proc type proc (rw)
usbdevfs on /proc/bus/usb type usbdevfs (rw)
/dev/hda1 on /boot type ext2 (rw)
none on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/hda3 on /home type ext3 (rw)
none on /dev/shm type tmpfs (rw)
/dev/hda5 on /usr/local type ext3 (rw)
/dev/cdrom on /mnt/cdrom type iso9660 (ro,nosuid,nodev,user=bob)
4 0 % whoami
bob
5 0 % mount /mnt/memstick/
6 0 % mount
/dev/hda2 on / type ext3 (rw)
none on /proc type proc (rw)
usbdevfs on /proc/bus/usb type usbdevfs (rw)
/dev/hda1 on /boot type ext2 (rw)
none on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/hda3 on /home type ext3 (rw)
none on /dev/shm type tmpfs (rw)
/dev/hda5 on /usr/local type ext3 (rw)
/dev/cdrom on /mnt/cdrom type iso9660 (ro,nosuid,nodev,user=bob)
/dev/sda1 on /mnt/memstick type vfat (rw,noexec,nosuid,nodev,user=bob)
7 0 % cp ~/data/data.fin /mnt/memstick/
8 0 % umount /mnt/memstick/
9 0 % mount
/dev/hda2 on / type ext3 (rw)
none on /proc type proc (rw)
usbdevfs on /proc/bus/usb type usbdevfs (rw)
/dev/hda1 on /boot type ext2 (rw)
none on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/hda3 on /home type ext3 (rw)
none on /dev/shm type tmpfs (rw)
/dev/hda5 on /usr/local type ext3 (rw)
/dev/cdrom on /mnt/cdrom type iso9660 (ro,nosuid,nodev,user=bob)
10 0 %
/var/log/messages shows:
Dec 1 17:47:34 smith kernel: hub.c: new USB device 00:03.3-3, assigned address 3
Dec 1 17:47:37 smith /etc/hotplug/usb.agent: Setup usb-storage for USB product ea0/2168/200
Dec 1 17:47:50 smith kernel: sda: Unit Not Ready, sense:
Dec 1 17:47:50 smith kernel: Current 00:00: sense key Unit Attention
Dec 1 17:47:50 smith kernel: Additional sense indicates Not ready to ready change,medium may have changed
Dec 1 17:47:50 smith kernel: sda : READ CAPACITY failed.
Dec 1 17:47:50 smith kernel: sda : status = 1, message = 00, host = 0, driver = 08
Dec 1 17:47:50 smith kernel: Current sd00:00: sense key Unit Attention
Dec 1 17:47:50 smith kernel: Additional sense indicates Not ready to ready change,medium may have changed
Dec 1 17:47:50 smith kernel: sda : block size assumed to be 512 bytes, disk size 1GB.
Dec 1 17:47:50 smith kernel: sda: Write Protect is off
Dec 1 17:47:50 smith kernel: sda: sda1
Dec 1 17:48:01 smith kernel: usb.c: USB disconnect on device 00:03.3-3 address 3
nb. i was able to get my QuickiDrive 128 working w/Redhat8.0 straight out of the box, by plugging in the drive and using the command 'mkdir /mnt/usb; mount /dev/sda1 /mnt/usb'
Originally posted by Spaz17
[root@zeus mnt]# mount -t ext3 /dev/sda /mnt/usb_hd
mount: wrong fs type, bad option, bad superblock on /dev/sda,
or too many mounted file systems
[root@zeus mnt]#
[root@zeus mnt]# mkfs -t ext3 /dev/sda
bash: mkfs: command not found
why?
how do i work around this?
I think it is because the drive is fat type , so if u try -t vfat would work, or just omit the -t and it will also work I got same thing and iot is working fine
As for the mkfs try /sbin/mkfs , or maybe locate mkfs
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.