At 03:05:20 on Monday Monday 01 June 2009, "Carlos E. R." <robin.listas@telefonica.net> wrote:
On Monday, 2009-06-01 at 00:01 +0300, Stan Goodman wrote:
Ok, then try to umount, then mount - manually.
stan@poblano:~> umount /media/floppy stan@poblano:~> ls /media/floppy stan@poblano:~> mount /media/floppy mount: /dev/fd0 is not a valid block device stan@poblano:~> mount /media/floppy
Above, is the umount, which was effective, since ls returned nothing. It is unexpected (at least to me) that the mount command then gets the error message.
And that's the real error: your system thinks it does not have a floppy.
You could look at the end of the /var/log/messages file right after the mount command, to see if the kernel says anything. Also, eject and put the floppy and look up the log again. Another place is to look in /var/log/boot.msg anything relative to the floppy.
The file /var/log/boot.msg has nothing related to the floppy; the file's date stamp is older than yesterday's experiments with the drive. On the other hand, /var/log/messages contains great tracts resembling the following: ***** May 31 23:50:42 poblano kernel: [drm:i915_getparam] *ERROR* Unknown parameter 5 May 31 23:51:03 poblano kernel: floppy0: disk absent or changed during operation May 31 23:51:03 poblano kernel: end_request: I/O error, dev fd0, sector 724 May 31 23:51:03 poblano kernel: Buffer I/O error on device fd0, logical block 724 . . . May 31 23:51:03 poblano kernel: end_request: I/O error, dev fd0, sector 34 May 31 23:51:03 poblano kernel: Buffer I/O error on device fd0, logical block 34 May 31 23:52:07 poblano kernel: floppy0: disk absent or changed during operation May 31 23:52:07 poblano kernel: end_request: I/O error, dev fd0, sector 19 May 31 23:52:07 poblano kernel: Buffer I/O error on device fd0, logical block 19 May 31 23:52:07 poblano kernel: lost page write due to I/O error on fd0 May 31 23:56:15 poblano kernel: end_request: I/O error, dev fd0, sector 0 May 31 23:56:15 poblano kernel: end_request: I/O error, dev fd0, sector 0 ***** Sector/logical blocks are always one of the following: 724, 33, 34, 19. After browsing that file, I did some mount -- umount manipulation of the drive (using the same diskette as yesterday), and again inspected to <messages> file. There was nothing there like the above, related to these actions. Then I tried clicking on the <floppy drive> icon in the Konqueror drives list, with the drive mounted. To my surprise, the resulting window now shows the files that I know to be present on the diskette. If I have done anything to bring this about, I don't know what it is. Returning to the <messages> file, I find the following error messages, which are very different from the messages of yesterday, but they do not enlighten me. ***** Jun 1 19:52:35 poblano su: (to root) stan on /dev/pts/3 Jun 1 20:01:03 poblano kernel: [drm:i915_getparam] *ERROR* Unknown parameter 5 Jun 1 20:08:42 poblano kernel: VFS: busy inodes on changed media or resized disk fd0 Jun 1 20:10:11 poblano kernel: [drm:i915_getparam] *ERROR* Unknown parameter 5 Jun 1 20:13:06 poblano kernel: [drm:i915_getparam] *ERROR* Unknown parameter 5 Jun 1 20:13:40 poblano kernel: [drm:i915_getparam] *ERROR* Unknown parameter 5 Jun 1 20:19:34 poblano su: (to root) stan on /dev/pts/2 ***** I would appreciate any help in understanding what was wrong yesterday, and also what appears still to be wrong today. -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org