On 26/12/2007, Tod Merley <todbot88(a)gmail.com> wrote:
As Ed Greshko points out my dyslexia has soured the soup. I saw
1255
but typed 1225 (twice!). That little change may well fix it.
I tried both 1225 and 1255. No change in situation, ie, the drive
would not mount with the same error.
The mount command you used kind of scares me. What I think you
wanted
to do is to unmount your device located at /dev/sdb1. What you told
your system to do was to unmount ALL file systems found in fstab!! It
is good that the system will not unmount devices in use, you would
have lost it all.
To unmount /dev/sdb1 issue: umount /dev/sdb1.
That did not work either, so I tried the -a flag as the mount manpage
says that it will unmount everything in /etc/mtab. I thought that mtab
was for things added to the filesystem that are not in fstab, ie,
removable media. I just cat'ed the file and I see that I was mistaken.
You know, the best way to learn is to break something! However, this
is my workstation and I really should be more careful.
Actually I used to contribute to both the Ubuntu and the Fedora
lists.
I have both on this machine. I tend to use Fedora when connected to
the Internet since I believe that it's pretty good implementation of
SELinux makes me a bit more secure in this more hostile world. I am
glad to see this thread here since many languages are used by those
using Fedora.
SELinux is the reason that I also stay with Fedora for everyday work.
The other reason is that I really like the Fedora philosophy. I
usually stick with N-1, however, as the most current version is always
to broken for me.
The "messages" are a bit differant though. Here is what happens when
I plug in my flash drive:
[root@localhost dev]# tail /var/log/messages
Dec 25 19:34:35 localhost kernel: sd 2:0:0:0: [sdb] 2013184 512-byte
hardware sectors (1031 MB)
Dec 25 19:34:35 localhost kernel: sd 2:0:0:0: [sdb] Write Protect is off
Dec 25 19:34:35 localhost kernel: sd 2:0:0:0: [sdb] Assuming drive
cache: write through
Dec 25 19:34:35 localhost kernel: sd 2:0:0:0: [sdb] 2013184 512-byte
hardware sectors (1031 MB)
Dec 25 19:34:35 localhost kernel: sd 2:0:0:0: [sdb] Write Protect is off
Dec 25 19:34:35 localhost kernel: sd 2:0:0:0: [sdb] Assuming drive
cache: write through
Dec 25 19:34:35 localhost kernel: sdb: sdb1
Dec 25 19:34:35 localhost kernel: sd 2:0:0:0: [sdb] Attached SCSI removable disk
Dec 25 19:34:35 localhost kernel: sd 2:0:0:0: Attached scsi generic sg2 type 0
Dec 25 19:34:38 localhost hald: mounted /dev/sdb1 on behalf of uid 500
The last line is hald doing the automount.
You may find the command lsusb -v useful. Also (from /dev before and
after inserting the flash drive):
[root@localhost dev]# ls -l sd*
brw-r----- 1 root disk 8, 0 2007-12-25 07:20 sda
brw-r----- 1 root disk 8, 1 2007-12-25 07:20 sda1
brw-r----- 1 root disk 8, 2 2007-12-25 07:20 sda2
brw-r----- 1 root disk 8, 3 2007-12-25 15:20 sda3
[root@localhost dev]# ls -l sd*
brw-r----- 1 root disk 8, 0 2007-12-25 07:20 sda
brw-r----- 1 root disk 8, 1 2007-12-25 07:20 sda1
brw-r----- 1 root disk 8, 2 2007-12-25 07:20 sda2
brw-r----- 1 root disk 8, 3 2007-12-25 15:20 sda3
brw-r----- 1 root disk 8, 16 2007-12-25 19:34 sdb
brw-r----- 1 root disk 8, 17 2007-12-25 19:34 sdb1
Thank you, I know about this, this is how I find where things got stuck in /dev.
Well, I am rambling! Did not sleep well last night.
Does anyone? My one-year old is pushing her teeth out now, nobody sleeps!
As using copepage 1255 did not work, is there anything else that I
could try? I tried using flag -t msdos instead of -t vfat but that did
not help either.
Dotan Cohen
http://what-is-what.com
http://gibberish.co.il
א-ב-ג-ד-ה-ו-ז-ח-ט-י-ך-כ-ל-ם-מ-ן-נ-ס-ע-ף-פ-ץ-צ-ק-ר-ש-ת
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?