[opensuse] Can't read mounted floppy disk
Only rarely anymore does one have to read of write diskettes, and I am having to do so now for the first time since I installed openSuSE. I have a floppy disk containing files. I can read these files in another OS using the same floppy drive on the same machine, but not in openSuSE. The Disk List in the Konqueror /sysinfo display shows that the available space on this diskette is much smaller than the total space, so it does see that there are files there. According to the Properties for fd0, the diskette is mounded on "/media/floppy". The following is the line in fstab that relates to the floppy drive: ***** /dev/fd0 /media/floppy auto noauto,user,sync 0 0 ***** When I click on the floppy-disk icon, Konqueror opens a window, showing the Location as: "media:/fd0", which doesn't look quite the same as the alleged mount point. The window is empty, although I know that there are files there. In the Konqueror view of directory "floppy", the status line at the bottom shows "No Items - No Files - No folders". The permissions for the floppy drive are RW for the owner (which is me), RO for group and others. It is not possible, even as root, to extend writing to group. Can someone help me see what is wrong here? -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2009-05-31 at 18:48 +0300, Stan Goodman wrote:
Only rarely anymore does one have to read of write diskettes, and I am having to do so now for the first time since I installed openSuSE.
I have a floppy disk containing files. I can read these files in another OS using the same floppy drive on the same machine, but not in openSuSE.
The Disk List in the Konqueror /sysinfo display shows that the available space on this diskette is much smaller than the total space, so it does see that there are files there. According to the Properties for fd0, the diskette is mounded on "/media/floppy".
The following is the line in fstab that relates to the floppy drive:
***** /dev/fd0 /media/floppy auto noauto,user,sync 0 0 *****
When I click on the floppy-disk icon, Konqueror opens a window, showing the Location as: "media:/fd0", which doesn't look quite the same as the alleged mount point. The window is empty, although I know that there are files there. In the Konqueror view of directory "floppy", the status line at the bottom shows "No Items - No Files - No folders".
The permissions for the floppy drive are RW for the owner (which is me), RO for group and others. It is not possible, even as root, to extend writing to group.
Can someone help me see what is wrong here?
Try on a konsole "ls /media/floppy". If it fails, try "mount /media/floppy". If it works, don't forget to umount. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkoi4WIACgkQtTMYHG2NR9XbMgCaAkq0KPh2ZlaCZY1uMEgVd/ww wXMAmgPOqCP4pth6YMkgOqYJ6Yn6EQIi =iSdz -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
At 22:58:16 on Sunday Sunday 31 May 2009, "Carlos E. R." <robin.listas@telefonica.net> wrote:
On Sunday, 2009-05-31 at 18:48 +0300, Stan Goodman wrote:
Only rarely anymore does one have to read of write diskettes, and I am having to do so now for the first time since I installed openSuSE.
I have a floppy disk containing files. I can read these files in another OS using the same floppy drive on the same machine, but not in openSuSE.
The Disk List in the Konqueror /sysinfo display shows that the available space on this diskette is much smaller than the total space, so it does see that there are files there. According to the Properties for fd0, the diskette is mounded on "/media/floppy".
The following is the line in fstab that relates to the floppy drive:
***** /dev/fd0 /media/floppy auto noauto,user,sync 0 0 *****
When I click on the floppy-disk icon, Konqueror opens a window, showing the Location as: "media:/fd0", which doesn't look quite the same as the alleged mount point. The window is empty, although I know that there are files there. In the Konqueror view of directory "floppy", the status line at the bottom shows "No Items - No Files - No folders".
The permissions for the floppy drive are RW for the owner (which is me), RO for group and others. It is not possible, even as root, to extend writing to group.
Can someone help me see what is wrong here?
Try on a konsole "ls /media/floppy". If it fails, try "mount /media/floppy". If it works, don't forget to umount.
The system, as you can see from the above, says that the floppy is already mounted. Here is the result of your suggestion: stan@poblano:~> ls /media/floppy stan@poblano:~> mount /media/floppy mount: /dev/fd0 already mounted or /media/floppy busy mount: according to mtab, /dev/fd0 is already mounted on /media/floppy stan@poblano:~> Which confirms that the drive was mounted. But if so, why does it not display the contents of the diskette that is in the drive? As I understand the fstab content, I don't need to umount explicitly; that should happen when the diskette is removed from the drive. Is that not so? -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2009-05-31 at 23:25 +0300, Stan Goodman wrote:
Can someone help me see what is wrong here?
Try on a konsole "ls /media/floppy". If it fails, try "mount /media/floppy". If it works, don't forget to umount.
The system, as you can see from the above, says that the floppy is already mounted.
Here is the result of your suggestion:
stan@poblano:~> ls /media/floppy stan@poblano:~> mount /media/floppy mount: /dev/fd0 already mounted or /media/floppy busy mount: according to mtab, /dev/fd0 is already mounted on /media/floppy stan@poblano:~>
Which confirms that the drive was mounted. But if so, why does it not display the contents of the diskette that is in the drive?
Ok, then try to umount, then mount - manually.
As I understand the fstab content, I don't need to umount explicitly; that should happen when the diskette is removed from the drive. Is that not so?
Certainly not! First you umount, which means that the memory structures the kernel maintains are removed, and the cache flushed. The, you can umount without loosing data. Unless your drive is special and has an eject button that transmits a request to the kernel, and the drive has a motor to eject the floppy - in cdrom fashion. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkoi7Q8ACgkQtTMYHG2NR9VBhACgjgwgGuIL9nyzpQuNtjl5Z2Oc ZesAn3ZY3Y+XKcGSBmLygFROT5kq3JFC =Bslu -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
At 23:48:08 on Sunday Sunday 31 May 2009, "Carlos E. R." <robin.listas@telefonica.net> wrote:
On Sunday, 2009-05-31 at 23:25 +0300, Stan Goodman wrote:
Can someone help me see what is wrong here?
Try on a konsole "ls /media/floppy". If it fails, try "mount /media/floppy". If it works, don't forget to umount.
The system, as you can see from the above, says that the floppy is already mounted.
Here is the result of your suggestion:
stan@poblano:~> ls /media/floppy stan@poblano:~> mount /media/floppy mount: /dev/fd0 already mounted or /media/floppy busy mount: according to mtab, /dev/fd0 is already mounted on /media/floppy stan@poblano:~>
Which confirms that the drive was mounted. But if so, why does it not display the contents of the diskette that is in the drive?
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. -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 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. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkojG08ACgkQtTMYHG2NR9UzigCeIDymFLAYbymm9+fOPqs0dfo2 X1kAnjF4//Q6lOOGeh44I6qSivZDAthR =9Jzy -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Stan, On Sunday May 31 2009, Carlos E. R. wrote:
...
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.
-- Cheers, Carlos E. R.
Have you checked your BIOS to make sure diskette access is enabled? Have you checked the connections on the signal and power cables to the drive? Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2009-05-31 at 17:20 -0700, Randall R Schulz wrote:
Have you checked your BIOS to make sure diskette access is enabled? Have you checked the connections on the signal and power cables to the drive?
As he said: ] I have a floppy disk containing files. I can read these files in another ] OS using the same floppy drive on the same machine, but not in openSuSE. ... it is obvious the disk and hardwre works. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkojI9UACgkQtTMYHG2NR9UM4QCfdNVbAE9XirHV6YcC6J1Tc+8y mQsAmwbjBzZDwzPUeSWuZPlrjUg0YTwP =okyg -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
At 03:41:43 on Monday Monday 01 June 2009, "Carlos E. R." <robin.listas@telefonica.net> wrote:
On Sunday, 2009-05-31 at 17:20 -0700, Randall R Schulz wrote:
Have you checked your BIOS to make sure diskette access is enabled? Have you checked the connections on the signal and power cables to the drive?
As he said:
] I have a floppy disk containing files. I can read these files in another ] OS using the same floppy drive on the same machine, but not in openSuSE.
... it is obvious the disk and hardwre works.
It is also obvious that there is no problem in the BIOS. The "other OS [OS/2] using the same floppy drive on the same machine" is seeing the same BIOS. -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
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
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.
-- Cheers, Carlos E. R.
I now see what it is that has to be done in order to get the floppy drive to be properly mounted; the WHY of it is still beyond me. Here is the sequence of actions: Before the diskette is inserted into the floppy drive, the Drive information list shows the floppy icon, but with no details. Inserting the diskette into the drive changes nothing, although <fstab> contains the line: /dev/fd0 /media/floppy auto noauto,user,sync 0 0 so apparently the drive is not mounted. I then did <mount /media/floppy>. This returns an error message saying that the apparently unmounted drive is already mounted. I did <umount/media/floppy>, to remove the evidently improperly mounted drive, followed by <mount/media/floppy. At no point have I removed the diskette from the drive. Now the Drive information list shows details of the floppy drive, and clicking on the floppy icon shows the files contained in the drive. The only conclusion that I can reach is that there is something wrong with the automatic mounting of the drive, per the above-quoted line in <fstab>. But to me, that line looks like what it should be. Viewing <var/log/messages> shows only the following lines relative to the sequence above: Jun 2 12:02:24 poblano su: (to root) stan on /dev/pts/3 Jun 2 12:10:24 poblano kernel: [drm:i915_getparam] *ERROR* Unknown parameter 5 Jun 2 12:12:33 poblano su: (to root) stan on /dev/pts/4 The two lines about /dev/pts are only about the console I was using, and so are irrelevant, as far as I understand. I have no clue what "parameter 5" has been found, nor how it got to wherever it is. It seems that this is the root of the problem of why the drive IS mounted, but isn't MOUNTED. Help! -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (3)
-
Carlos E. R. -
Randall R Schulz -
Stan Goodman