Re: [Cooker] Supermount Problem: Serious?
I have the same problem with No such file or directory errors when copying
or just reading from my DVD-ROM drive.
Reading or copying files from my CD writer, which is using the ide-scsi
kernel module, seems to work fine. However, I have not fully tested this
theory.
I also receive an error:
kernel: hdc: cdrom_decode_status: status=0x51 { DriveReady SeekComplete
Error }
kernel: hdc: cdrom_decode_status: error=0x40
I assume /dev/hdc (my DVD-ROM drive) is using the ide-cd module.
I might try making /dev/hdc use the ide-scsi module.
Hope this helps,
Tim
_
MSN Photos is the easiest way to share and print your photos:
http://photos.msn.com/support/worldwide.aspx
Re: [Cooker] Supermount Problem: Serious?
James Sparenberg wrote on Tue, Oct 01, 2002 at 12:00:29AM -0700 : Cd /mnt/cdrom/some_directory as a user su to root do some work. eject the cdrom put in a new one. Quite often the new one is unreadable. ie Understandable. The problem is that the eject should fail with an unable to unmount, IMHO. If you want to see what I mean, open a terminal right now, su to root, and then type 'umount /home': [root@trip todd]# umount /home umount: /home: device is busy That's what supermount should report since the regular user you su'd from is still in that directory. directory Mandrake not found. Yes, everything in memory at this point is fubar'd because the media got removed out from under it. Obvious question is since I only did an ls why or rather how did it know about a directory mandrake. Now i exit the su ... it immediately drops back to by user. IN a directory on the previously removed CD.(even though that tree no longer exists.) In fact sometimes if I do an ls it has even given me the files in the directory of the removed CD. (Not always repeatable) A similar scenario is if I do: [todd@trip todd]$ mkdir test1 [todd@trip todd]$ cd test1 [todd@trip test1]$ mkdir test2 [todd@trip test1]$ cd test2 [todd@trip test2]$ pwd /home/todd/test1/test2 [todd@trip test2]$ su Password: [root@trip test2]# cd ../.. [root@trip todd]# rm -rf test1 [root@trip todd]# exit exit [todd@trip test2]$ pwd /home/todd/test1/test2 [todd@trip test2]$ ls [todd@trip test2]$ cd .. cd: could not get current directory: getcwd: cannot access parent directories: No such file or directory cd: could not get current directory: getcwd: cannot access parent directories: No such file or directory [todd@trip .]$ pwd pwd: could not get current directory: getcwd: cannot access parent directories: No such file or directory [todd@trip .]$ cd .. chdir: could not get current directory: getcwd: cannot access parent directories: No such file or directory [todd@trip ..]$ cd .. [todd@trip ..]$ ls bin/ dev/ home/lib/ opt/ root/ tmp/ var/ boot/ etc/ initrd/ mnt/ proc/ sbin/ usr/ [todd@trip ..]$ ls bin/ dev/ home/lib/ opt/ root/ tmp/ var/ boot/ etc/ initrd/ mnt/ proc/ sbin/ usr/ [todd@trip ..]$ pwd ../.. [todd@trip ..]$ cd / [todd@trip /]$ ls So removing the media out from under the user is similar to removing directories out from under the user (but not identical). It's pretty much fatal. Luckily in the above example, I could always just cd / and it took care of the issues that bash was having. But it's not that simple with supermount. Keep in mind that I know very little about supermount. Saying that I'm studying it is a lot like saying I'm studying the Theory of Relativity to make enhancements. It sounds really impressive, but it doesn't mean that it will ever happen (by my hand at least :) Rather, I'm looking at the code, trying to understand what it does. Someone like Juan knows that code much better and is able to read into the errors. Blue skies... Todd -- Todd Lyons -- MandrakeSoft, Inc. http://www.mandrakesoft.com/ UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things. -- Doug Gwyn Cooker Version mandrake-release-9.0-0.3mdk Kernel 2.4.19-16mdk msg77824/pgp0.pgp Description: PGP signature
Re: [Cooker] Supermount Problem: Serious?
On Sun, 2002-09-29 at 13:24, John Allen wrote: [EMAIL PROTECTED] wrote: On Sun, 29 Sep 2002, Steven Spears wrote: Mandrake start ther is an error message: Fault: mount device not found. I think you need to remove 'auto' and set 'noauto' in the responsible fstab line. Otherwise system will try to mount the empty drive, which will fail ofcourse. It is not a real bad problem is it? Ran the test and sure enough, I get the same error as well. I opened the and hope this helps. As anyone mentioned this on the cooker list? I think I saw it before. But IMHO (and others) supermount is just hopeless. And it has more problems than only the above. Anyone with a bit C experience should throw himself on improving Alan Cox' volumagic, so that we can do automounting in userspace. Hopefully I will try during Xmas holidays. But I never did something more serious than some easy gui programs, so do not hold your breath:) Danny I have a really serious problem with supermount. I have created a DVD of 9.0, which I cannot copy to my hard disk if /mnt/cdrom is supermounted. It manages to copy maybe 20% then cannot open (stat) any files on the DVD, not even from the command line. If I disable supermount and manually mount the DVD it all works OK. (The option to manually mount/unmount is gone from the CD-ROM popup menu in KDE so had to use the mount comamnd directly) PS: This does not just hapen on one machine. Don't know if this will help but I found one thing Scenario Cd /mnt/cdrom/some_directory as a user su to root do some work. eject the cdrom put in a new one. Quite often the new one is unreadable. ie cd /mnt/cdrom ls directory Mandrake not found. Obvious question is since I only did an ls why or rather how did it know about a directory mandrake. Now i exit the su ... it immediately drops back to by user. IN a directory on the previously removed CD.(even though that tree no longer exists.) In fact sometimes if I do an ls it has even given me the files in the directory of the removed CD. (Not always repeatable) Don't know if any of this will help... hope it does. James
RE: Re: [Cooker] Supermount Problem: Serious?
Luis, Could you be so kind as explains us in detail how do you have setuped autofs? Thanks so much in advance Francisco Alcaraz Murcia (Spain) - Mensaje Original - Remitente: Luis M [EMAIL PROTECTED] Fecha: Martes, Octubre 1, 2002 2:59 am Asunto: Re: [Cooker] Supermount Problem: Serious? Just in case, I disable supermount for both of my cdroms... instead I setup autofs in /misc . Thus now, ls /misc/cdrom brings my CDs just fine. I always wonder why the need for supermount if autofs does the same ... In any case, maybe it's because of supermount that I cannot restart my computer. Everytime I do it says something about mount2 trying to umount something else and then the init says something about no more processes left in this run level and it stays there forever... I saw this error before with 8.2, I just don't remember what I did to fix it. And this happens to me on two completely different boxes. My workstation at work and the one I use at home. I reported this before but, nobody ever said anything; thus I assume that either no body ever reboots their computers or this is an isolated case and it only happens to me... @#$@#% I'm sure supermount or autofs have something to do with it... let me start the rebooting tests now :-) ... From: John Allen [EMAIL PROTECTED] This is definitely a supermount problem. Manually mounting works perfect.. I have this problem on all my cooker, and 9.0 machines. Tried 2.4.19-12mdk and it fails also. Luis M wrote: That usually means a bad burn. Do this: make sure that your ISO's have the right md5sum: f7a093af34b8cbe1abc165213fea9deb Mandrake90-cd1-inst.i586.iso 05a3ccafaacc37d6d1e2f260fc274549 Mandrake90-cd2-ext.i586.iso 1a2fd731fb6e30d39b0b99f504b231b3 Mandrake90-cd3-i18n.i586.iso To check the md5sum: $ md5sum FILE.iso After you do that, then mount the ISO's to a directory (as root do this for the CD's you are having problems with): # mount -t iso9660 -o loop FILE.iso /mnt/test Then go to /mnt/test/Mandrake/RPMS2 and do the same you tried before... if this works fine (it should if the md5sum matched and your loop devices and hard drive work fine...), then try burning your disk at a lower speed than your burner supports -- burning at 8x is better than at any other speed if you have the time to wait until it finishes and use cheap blank disks. I have seen that problem you mentioned before and I'm sure is just a bad burn because after burning the disks at two steps slower than my writer supports, the disks worked fine. Sample session here: $ du -s /mnt/iso2/Mandrake/RPMS2/ 698M/mnt/iso2/Mandrake/RPMS2 $ mkdir /mnt/backup/test $ cp -a /mnt/iso2/Mandrake/RPMS2/*.rpm /mnt/backup/test $ You can see that the iso's are fine... From the CarshTesters List: Date 29 Sep 2002 12:25 Subject Re: [CrashTesters] 9.0 Supermount nightmare On 29 Sep 2002 12:09 CDT you wrote: On 29 Sep 2002 06:24 CDT you wrote: Dear friends, I am having lot of problems with supermount in 9.0: 1- With supermount enabled, when I try to copy several files sometimes, after few minutes, some of the files in the cdrom are not recognized (the file Toshiba... is not valid). 2. I have dissabled supermount in my dvd-drive; now I can mount and umount as a user, the problem of files dissapearing is solved, but when Mandrake start ther is an error message: Fault: mount device not found. To eliminate the message is enought activating again supermount to that drive. There you have my fstab file; I have to harddisks (hda with two vfat partitions and two xfs partitions; and hdb with the main linux paritions /dev/hdb5 / ext3 defaults 1 1 /dev/hdb1 /boot ext3 defaults 1 2 none /dev/pts devpts mode=0620 0 0 /dev/hdb7 /disk xfs defaults 1 2 /dev/hdb8 /home xfs defaults 1 2 /dev/hdd /mnt/cdrom2 auto user,iocharset=iso8859-15,codepage=850,ro,umask=0 0 0 none /mnt/floppy supermount dev=/dev/fd0,fs=auto,--,iocharset=iso8859- 15,sync,codepage=850,umask=0 0 0 /dev/hda1 /mnt/win_c vfat iocharset=iso8859- 15,codepage=850,umask=0 0 0 /dev/hda5 /mnt/win_d vfat iocharset=iso8859- 15,codepage=850,umask=0 0 0 /dev/hdb13 /object xfs defaults 1 2 /dev/hda7 /otros xfs defaults 1 2 /dev/hda6 /pelis xfs defaults 1 2 none /proc proc defaults 0 0 /dev/hdb11 /tmp xfs defaults 1 2 /dev/hdb6 /usr xfs defaults 1 2 /dev/hdb9 /usr/share ext3 defaults 1 2 /dev/hdb10 /var xfs defaults 1 2 none mnt/cdrom supermount dev=/dev/scd0,fs=auto,ro,--,iocharset=iso8859- 15,codepage=850,umask=0 0 0 /dev/hdb12 swap swap defaults 0 0 Ah!; in my laptop the problem also appears. Any idea about where the problem arises and how can it bee solved? Thanks so much
Re: [Cooker] Supermount Problem: Serious?
Just in case, I disable supermount for both of my cdroms... instead I setup autofs in /misc . Thus now, ls /misc/cdrom brings my CDs just fine. I always wonder why the need for supermount if autofs does the same ... In any case, maybe it's because of supermount that I cannot restart my computer. Everytime I do it says something about mount2 trying to umount something else and then the init says something about no more processes left in this run level and it stays there forever... I saw this error before with 8.2, I just don't remember what I did to fix it. And this happens to me on two completely different boxes. My workstation at work and the one I use at home. I reported this before but, nobody ever said anything; thus I assume that either no body ever reboots their computers or this is an isolated case and it only happens to me... @#$@#% I'm sure supermount or autofs have something to do with it... let me start the rebooting tests now :-) ... From: John Allen [EMAIL PROTECTED] This is definitely a supermount problem. Manually mounting works perfect.. I have this problem on all my cooker, and 9.0 machines. Tried 2.4.19-12mdk and it fails also. Luis M wrote: That usually means a bad burn. Do this: make sure that your ISO's have the right md5sum: f7a093af34b8cbe1abc165213fea9deb Mandrake90-cd1-inst.i586.iso 05a3ccafaacc37d6d1e2f260fc274549 Mandrake90-cd2-ext.i586.iso 1a2fd731fb6e30d39b0b99f504b231b3 Mandrake90-cd3-i18n.i586.iso To check the md5sum: $ md5sum FILE.iso After you do that, then mount the ISO's to a directory (as root do this for the CD's you are having problems with): # mount -t iso9660 -o loop FILE.iso /mnt/test Then go to /mnt/test/Mandrake/RPMS2 and do the same you tried before... if this works fine (it should if the md5sum matched and your loop devices and hard drive work fine...), then try burning your disk at a lower speed than your burner supports -- burning at 8x is better than at any other speed if you have the time to wait until it finishes and use cheap blank disks. I have seen that problem you mentioned before and I'm sure is just a bad burn because after burning the disks at two steps slower than my writer supports, the disks worked fine. Sample session here: $ du -s /mnt/iso2/Mandrake/RPMS2/ 698M/mnt/iso2/Mandrake/RPMS2 $ mkdir /mnt/backup/test $ cp -a /mnt/iso2/Mandrake/RPMS2/*.rpm /mnt/backup/test $ You can see that the iso's are fine... From the CarshTesters List: Date 29 Sep 2002 12:25 Subject Re: [CrashTesters] 9.0 Supermount nightmare On 29 Sep 2002 12:09 CDT you wrote: On 29 Sep 2002 06:24 CDT you wrote: Dear friends, I am having lot of problems with supermount in 9.0: 1- With supermount enabled, when I try to copy several files sometimes, after few minutes, some of the files in the cdrom are not recognized (the file Toshiba... is not valid). 2. I have dissabled supermount in my dvd-drive; now I can mount and umount as a user, the problem of files dissapearing is solved, but when Mandrake start ther is an error message: Fault: mount device not found. To eliminate the message is enought activating again supermount to that drive. There you have my fstab file; I have to harddisks (hda with two vfat partitions and two xfs partitions; and hdb with the main linux paritions /dev/hdb5 / ext3 defaults 1 1 /dev/hdb1 /boot ext3 defaults 1 2 none /dev/pts devpts mode=0620 0 0 /dev/hdb7 /disk xfs defaults 1 2 /dev/hdb8 /home xfs defaults 1 2 /dev/hdd /mnt/cdrom2 auto user,iocharset=iso8859-15,codepage=850,ro,umask=0 0 0 none /mnt/floppy supermount dev=/dev/fd0,fs=auto,--,iocharset=iso8859-15,sync,codepage=850,umask=0 0 0 /dev/hda1 /mnt/win_c vfat iocharset=iso8859-15,codepage=850,umask=0 0 0 /dev/hda5 /mnt/win_d vfat iocharset=iso8859-15,codepage=850,umask=0 0 0 /dev/hdb13 /object xfs defaults 1 2 /dev/hda7 /otros xfs defaults 1 2 /dev/hda6 /pelis xfs defaults 1 2 none /proc proc defaults 0 0 /dev/hdb11 /tmp xfs defaults 1 2 /dev/hdb6 /usr xfs defaults 1 2 /dev/hdb9 /usr/share ext3 defaults 1 2 /dev/hdb10 /var xfs defaults 1 2 none mnt/cdrom supermount dev=/dev/scd0,fs=auto,ro,--,iocharset=iso8859-15,codepage=850,umask=0 0 0 /dev/hdb12 swap swap defaults 0 0 Ah!; in my laptop the problem also appears. Any idea about where the problem arises and how can it bee solved? Thanks so much in advance Francisco Alcaraz Murcia (Spain) I will run a test on this now and see what my results are. Steve Spears Ran the test and sure enough, I get the same error as well. I opened the CD-ROM with 9.0 CD-ROM #2 and created a directory and opened it. Then I did a mass select in the RPMS2 directory and drug them into the new test directory. The copy started off fine but then cam up with the error that certain files didn't exist. I clicked auto skip to see
Re: [Cooker] Supermount Problem: Serious?
Steven Spears wrote: Ran the test and sure enough, I get the same error as well. I opened the CD-ROM with 9.0 CD-ROM #2 and created a directory and opened it. Then I did a mass select in the RPMS2 directory and drug them into the new test directory. The copy started off fine but then cam up with the error that certain files didn't exist. I clicked auto skip to see what would happened. It went on for a little bit and then just stopped. I looked in the test directory that I created and there were only a few files in there. When I went back into the CD-ROM/Mandrake/RPMS2 via Konqueror it was showing only one file. enlightenment. Being curious, I went to a konsole and did the followign: [wriker@riker wriker]$ cd /mnt/cdrom [wriker@riker cdrom]$ ls ls: Boot: No such file or directory Mandrake/ [wriker@riker cdrom]$ cd Mandrake/ [wriker@riker Mandrake]$ ls RPMS2/ [wriker@riker Mandrake]$ cd RPMS2/ [wriker@riker RPMS2]$ ls ls: a2ps-devel-4.13-14mdk.i586.rpm: No such file or directory ls: adjtimex-1.12-6mdk.i586.rpm: No such file or directory ls: am-utils-6.0.7-2mdk.i586.rpm: No such file or directory ls: apache-manual-1.3.26-6mdk.i586.rpm: No such file or directory ls: apache-suexec-1.3.26-2mdk.i586.rpm: No such file or directory ls: fonts-type1-baltic-1.0-6mdk.noarch.rpm: No such file or directory ls: freeciv-1.13.0-6mdk.i586.rpm: No such file or directory ls: freetype-devel-1.3.1-17mdk.i586.rpm: No such file or directory ls: fribidi-0.10.1-3mdk.i586.rpm: No such file or directory ls: frozen-bubble-0.9.3-6mdk.i586.rpm: No such file or directory ls: fwlogwatch-0.6-3mdk.i586.rpm: No such file or directory ls: gabber-0.8.7-7mdk.i586.rpm: No such file or directory ls: gaddr-1.1.4-2mdk.i586.rpm: No such file or directory ls: gaim-0.59.1-2mdk.i586.rpm: No such file or directory ls: gated-3.6-2mdk.i586.rpm: No such file or directory ls: gatos-0.0.6-0.20010216.11mdk.i586.rpm: No such file or directory ls: gawk-doc-3.1.1-3mdk.i586.rpm: No such file or directory ls: gcc-c -3.2-1mdk.i586.rpm: No such file or directory ls: gcc-g77-3.2-1mdk.i586.rpm: No such file or directory ls: gcc-java-3.2-1mdk.i586.rpm: No such file or directory ls: gcc-objc-3.2-1mdk.i586.rpm: No such file or directory ls: gcj-tools-3.2-1mdk.i586.rpm: No such file or directory ls: gcombust-0.1.52-1mdk.i586.rpm: No such file or directory ls: gconf-editor-0.3-1mdk.i586.rpm: No such file or directory ls: gd-utils-1.8.4-6mdk.i586.rpm: No such file or directory ls: gedit-2.0.2-1mdk.i586.rpm: No such file or directory ls: gettext-devel-0.11.2-8mdk.i586.rpm: No such file or directory ls: gettext-0.11.2-8mdk.i586.rpm: No such file or directory ls: xfce-3.8.16-2mdk.i586.rpm: No such file or directory ls: xfig-3.2.3d-6mdk.i586.rpm: No such file or directory ls: xfishtank-2.1tp-6mdk.i586.rpm: No such file or directory ls: XFree86-static-libs-4.2.1-3mdk.i586.rpm: No such file or directory ls: XFree86-Xnest-4.2.1-3mdk.i586.rpm: No such file or directory ls: XFree86-Xvfb-4.2.1-3mdk.i586.rpm: No such file or directory ls: XFree86-cyrillic-fonts-4.2.1-3mdk.i586.rpm: No such file or directory ls: xine-aa-0.9.13-3mdk.i586.rpm: No such file or directory ls: xine-oss-0.9.13-3mdk.i586.rpm: No such file or directory ls: xine-plugins-0.9.13-3mdk.i586.rpm: No such file or directory ls: xine-ui-0.9.13-2mdk.i586.rpm: No such file or directory ls: xinput-1.2-5mdk.i586.rpm: No such file or directory ls: xli-1.17.0-4mdk.i586.rpm: No such file or directory ls: xlockmore-5.04-4mdk.i586.rpm: No such file or directory ls: xmailbox-2.5-15mdk.i586.rpm: No such file or directory ls: xmms-arts-0.4-8mdk.i586.rpm: No such file or directory ls: xmms-esd-1.2.7-13mdk.i586.rpm: No such file or directory ls: xmms-kjofol-skins-1.2.0-5mdk.i586.rpm: No such file or directory ls: xmms-mesa-1.2.7-13mdk.i586.rpm: No such file or directory ls: xmms-mikmod-1.2.7-13mdk.i586.rpm: No such file or directory ls: xmms-more-vis-plugins-1.6.0-2mdk.i586.rpm: No such file or directory ls: xmms-skins-1.0.0-13mdk.noarch.rpm: No such file or directory ls: xmms-smpeg-0.3.4-7mdk.i586.rpm: No such file or directory ls: xmovie-1.9-12mdk.i586.rpm: No such file or directory ls: xpat2-1.07-12mdk.i586.rpm: No such file or directory ls: xpcd-2.08-17mdk.i586.rpm: No such file or directory ls: xpcd-gimp-2.08-17mdk.i586.rpm: No such file or directory ls: xsysinfo-1.7-12mdk.i586.rpm: No such file or directory ls: Xtart-1.0-7mdk.noarch.rpm: No such file or directory ls: xterm-166-1mdk.i586.rpm: No such file or directory ls: xtoolwait-1.3-5mdk.i586.rpm: No such file or directory ls: xtraceroute-0.9.0-9mdk.i586.rpm: No such file or directory ls: xwpick-2.20-10mdk.i586.rpm: No such file or directory ls: xxgdb-1.12-19mdk.i586.rpm: No such file or directory ls: ypserv-2.4-1mdk.i586.rpm: No such file or directory ls: ytalk-3.1.1-7mdk.i586.rpm: No such file or
Re: [Cooker] Supermount Problem: Serious?
On Sun, 29 Sep 2002, Steven Spears wrote: Mandrake start ther is an error message: Fault: mount device not found. I think you need to remove 'auto' and set 'noauto' in the responsible fstab line. Otherwise system will try to mount the empty drive, which will fail ofcourse. It is not a real bad problem is it? Ran the test and sure enough, I get the same error as well. I opened the and hope this helps. As anyone mentioned this on the cooker list? I think I saw it before. But IMHO (and others) supermount is just hopeless. And it has more problems than only the above. Anyone with a bit C experience should throw himself on improving Alan Cox' volumagic, so that we can do automounting in userspace. Hopefully I will try during Xmas holidays. But I never did something more serious than some easy gui programs, so do not hold your breath:) Danny
Re: [Cooker] Supermount Problem: Serious?
[EMAIL PROTECTED] wrote: On Sun, 29 Sep 2002, Steven Spears wrote: Mandrake start ther is an error message: Fault: mount device not found. I think you need to remove 'auto' and set 'noauto' in the responsible fstab line. Otherwise system will try to mount the empty drive, which will fail ofcourse. It is not a real bad problem is it? Ran the test and sure enough, I get the same error as well. I opened the and hope this helps. As anyone mentioned this on the cooker list? I think I saw it before. But IMHO (and others) supermount is just hopeless. And it has more problems than only the above. Anyone with a bit C experience should throw himself on improving Alan Cox' volumagic, so that we can do automounting in userspace. Hopefully I will try during Xmas holidays. But I never did something more serious than some easy gui programs, so do not hold your breath:) Danny I have a really serious problem with supermount. I have created a DVD of 9.0, which I cannot copy to my hard disk if /mnt/cdrom is supermounted. It manages to copy maybe 20% then cannot open (stat) any files on the DVD, not even from the command line. If I disable supermount and manually mount the DVD it all works OK. (The option to manually mount/unmount is gone from the CD-ROM popup menu in KDE so had to use the mount comamnd directly) PS: This does not just hapen on one machine.
Re: [Cooker] Supermount Problem: Serious?
That usually means a bad burn. Do this: make sure that your ISO's have the right md5sum: f7a093af34b8cbe1abc165213fea9deb Mandrake90-cd1-inst.i586.iso 05a3ccafaacc37d6d1e2f260fc274549 Mandrake90-cd2-ext.i586.iso 1a2fd731fb6e30d39b0b99f504b231b3 Mandrake90-cd3-i18n.i586.iso To check the md5sum: $ md5sum FILE.iso After you do that, then mount the ISO's to a directory (as root do this for the CD's you are having problems with): # mount -t iso9660 -o loop FILE.iso /mnt/test Then go to /mnt/test/Mandrake/RPMS2 and do the same you tried before... if this works fine (it should if the md5sum matched and your loop devices and hard drive work fine...), then try burning your disk at a lower speed than your burner supports -- burning at 8x is better than at any other speed if you have the time to wait until it finishes and use cheap blank disks. I have seen that problem you mentioned before and I'm sure is just a bad burn because after burning the disks at two steps slower than my writer supports, the disks worked fine. Sample session here: $ du -s /mnt/iso2/Mandrake/RPMS2/ 698M/mnt/iso2/Mandrake/RPMS2 $ mkdir /mnt/backup/test $ cp -a /mnt/iso2/Mandrake/RPMS2/*.rpm /mnt/backup/test $ You can see that the iso's are fine... From the CarshTesters List: Date 29 Sep 2002 12:25 Subject Re: [CrashTesters] 9.0 Supermount nightmare On 29 Sep 2002 12:09 CDT you wrote: On 29 Sep 2002 06:24 CDT you wrote: Dear friends, I am having lot of problems with supermount in 9.0: 1- With supermount enabled, when I try to copy several files sometimes, after few minutes, some of the files in the cdrom are not recognized (the file Toshiba... is not valid). 2. I have dissabled supermount in my dvd-drive; now I can mount and umount as a user, the problem of files dissapearing is solved, but when Mandrake start ther is an error message: Fault: mount device not found. To eliminate the message is enought activating again supermount to that drive. There you have my fstab file; I have to harddisks (hda with two vfat partitions and two xfs partitions; and hdb with the main linux paritions /dev/hdb5 / ext3 defaults 1 1 /dev/hdb1 /boot ext3 defaults 1 2 none /dev/pts devpts mode=0620 0 0 /dev/hdb7 /disk xfs defaults 1 2 /dev/hdb8 /home xfs defaults 1 2 /dev/hdd /mnt/cdrom2 auto user,iocharset=iso8859-15,codepage=850,ro,umask=0 0 0 none /mnt/floppy supermount dev=/dev/fd0,fs=auto,--,iocharset=iso8859-15,sync,codepage=850,umask=0 0 0 /dev/hda1 /mnt/win_c vfat iocharset=iso8859-15,codepage=850,umask=0 0 0 /dev/hda5 /mnt/win_d vfat iocharset=iso8859-15,codepage=850,umask=0 0 0 /dev/hdb13 /object xfs defaults 1 2 /dev/hda7 /otros xfs defaults 1 2 /dev/hda6 /pelis xfs defaults 1 2 none /proc proc defaults 0 0 /dev/hdb11 /tmp xfs defaults 1 2 /dev/hdb6 /usr xfs defaults 1 2 /dev/hdb9 /usr/share ext3 defaults 1 2 /dev/hdb10 /var xfs defaults 1 2 none mnt/cdrom supermount dev=/dev/scd0,fs=auto,ro,--,iocharset=iso8859-15,codepage=850,umask=0 0 0 /dev/hdb12 swap swap defaults 0 0 Ah!; in my laptop the problem also appears. Any idea about where the problem arises and how can it bee solved? Thanks so much in advance Francisco Alcaraz Murcia (Spain) I will run a test on this now and see what my results are. Steve Spears Ran the test and sure enough, I get the same error as well. I opened the CD-ROM with 9.0 CD-ROM #2 and created a directory and opened it. Then I did a mass select in the RPMS2 directory and drug them into the new test directory. The copy started off fine but then cam up with the error that certain files didn't exist. I clicked auto skip to see what would happened. It went on for a little bit and then just stopped. I looked in the test directory that I created and there were only a few files in there. When I went back into the CD-ROM/Mandrake/RPMS2 via Konqueror it was showing only one file. enlightenment. Being curious, I went to a konsole and did the followign: [wriker@riker wriker]$ cd /mnt/cdrom [wriker@riker cdrom]$ ls ls: Boot: No such file or directory Mandrake/ [wriker@riker cdrom]$ cd Mandrake/ [wriker@riker Mandrake]$ ls RPMS2/ [wriker@riker Mandrake]$ cd RPMS2/ [wriker@riker RPMS2]$ ls ls: a2ps-devel-4.13-14mdk.i586.rpm: No such file or directory ls: adjtimex-1.12-6mdk.i586.rpm: No such file or directory ls: am-utils-6.0.7-2mdk.i586.rpm: No such file or directory ls: apache-manual-1.3.26-6mdk.i586.rpm: No such file or directory ls: apache-suexec-1.3.26-2mdk.i586.rpm: No such file or directory ls: fonts-type1-baltic-1.0-6mdk.noarch.rpm: No such file or directory ls: freeciv-1.13.0-6mdk.i586.rpm: No such file or directory ls: freetype-devel-1.3.1-17mdk.i586.rpm: No such file or directory ls: fribidi-0.10.1-3mdk.i586.rpm: No such file or directory ls: frozen-bubble-0.9.3-6mdk.i586.rpm: No such file or
Re: [Cooker] Supermount Problem: Serious?
I have the same problem on my Laptops (seems to work ok on my desktop systems so far). I have to disable supermount to be able to properly mount/unmount/use CD's. Plus, once disabled, I have to shut down and restart the system for the change to take effect, rebooting isn't enough. Supermount seems to bite the big one and for newbies it is very important to have working. I think adding in Alan Cox's fix would be a good idea. Cheers, Jason P.S. I am running a bone stock 9.0 install. John Allen wrote: [EMAIL PROTECTED] wrote: On Sun, 29 Sep 2002, Steven Spears wrote: Mandrake start ther is an error message: Fault: mount device not found. I think you need to remove 'auto' and set 'noauto' in the responsible fstab line. Otherwise system will try to mount the empty drive, which will fail ofcourse. It is not a real bad problem is it? Ran the test and sure enough, I get the same error as well. I opened the and hope this helps. As anyone mentioned this on the cooker list? I think I saw it before. But IMHO (and others) supermount is just hopeless. And it has more problems than only the above. Anyone with a bit C experience should throw himself on improving Alan Cox' volumagic, so that we can do automounting in userspace. Hopefully I will try during Xmas holidays. But I never did something more serious than some easy gui programs, so do not hold your breath:) Danny I have a really serious problem with supermount. I have created a DVD of 9.0, which I cannot copy to my hard disk if /mnt/cdrom is supermounted. It manages to copy maybe 20% then cannot open (stat) any files on the DVD, not even from the command line. If I disable supermount and manually mount the DVD it all works OK. (The option to manually mount/unmount is gone from the CD-ROM popup menu in KDE so had to use the mount comamnd directly) PS: This does not just hapen on one machine.
Re: [Cooker] Supermount Problem: Serious?
On Sun, 29 Sep 2002, Luis M wrote: That usually means a bad burn. Do this: How is this a bad burn, we are talking about things working with manual mount, but not with supermount. To be even more specific, sometimes I see half of the dirs, somethimes the other half. Even on commercial CDs. It is just utterly broken. But not on all machines it seems (because I never noticed it on my cooker box, but I could have been lucky.) Read the mails again, it has nothing to do with bad burns. Danny
Re: [Cooker] Supermount Problem: Serious?
On Mon, 30 Sep 2002, Jason wrote: important to have working. I think adding in Alan Cox's fix would be a good idea. It is not a real fix, it is a different program. It already works for CDs, but no floppies AFAIK. I might try to build an rpm and put it into contrib. But it is still very alpha. Danny
Re: [Cooker] Supermount Problem: Serious?
I understand. My point is that either we get SOMETHING that works or IMHO take out Supermount (or other like programs) altogether and setup Kwikdisk to start automatically so newbies can mount/unmount CD's easily. This is getting tedious. I have been running ML (all major releases and cooker) for a long time and Supermount is just a beast, it is so flakey!! I have good luck on my Cooker home box but elsewhere it just seems to fall over way too often. Newbies would quickly become frustrated with something that should work so simply (and has worked in Winblows for as long as I can remember). I have read that the code for supermount is pretty horrid but I couldn't say as I don't code. I test and submit bug reports though!! =) The OSS community is S talented, I am very surprised this has not been properly dealt with long before now.sigh. Cheers, Jason [EMAIL PROTECTED] wrote: On Mon, 30 Sep 2002, Jason wrote: important to have working. I think adding in Alan Cox's fix would be a good idea. It is not a real fix, it is a different program. It already works for CDs, but no floppies AFAIK. I might try to build an rpm and put it into contrib. But it is still very alpha. Danny
Re: [Cooker] Supermount Problem: Serious?
All md5sums check out perfect and it doesn't just happen with burnt CDs. It happens with any, and my installs with these CDs were flawless over four+ computers so far. Don't think it's the CDs. Steve On Sunday 29 September 2002 3:51 pm, Luis M wrote: That usually means a bad burn. Do this: make sure that your ISO's have the right md5sum: f7a093af34b8cbe1abc165213fea9deb Mandrake90-cd1-inst.i586.iso 05a3ccafaacc37d6d1e2f260fc274549 Mandrake90-cd2-ext.i586.iso 1a2fd731fb6e30d39b0b99f504b231b3 Mandrake90-cd3-i18n.i586.iso To check the md5sum: $ md5sum FILE.iso After you do that, then mount the ISO's to a directory (as root do this for the CD's you are having problems with): # mount -t iso9660 -o loop FILE.iso /mnt/test Then go to /mnt/test/Mandrake/RPMS2 and do the same you tried before... if this works fine (it should if the md5sum matched and your loop devices and hard drive work fine...), then try burning your disk at a lower speed than your burner supports -- burning at 8x is better than at any other speed if you have the time to wait until it finishes and use cheap blank disks. I have seen that problem you mentioned before and I'm sure is just a bad burn because after burning the disks at two steps slower than my writer supports, the disks worked fine. Sample session here: $ du -s /mnt/iso2/Mandrake/RPMS2/ 698M /mnt/iso2/Mandrake/RPMS2 $ mkdir /mnt/backup/test $ cp -a /mnt/iso2/Mandrake/RPMS2/*.rpm /mnt/backup/test $ You can see that the iso's are fine... From the CarshTesters List: Date 29 Sep 2002 12:25 Subject Re: [CrashTesters] 9.0 Supermount nightmare On 29 Sep 2002 12:09 CDT you wrote: On 29 Sep 2002 06:24 CDT you wrote: Dear friends, I am having lot of problems with supermount in 9.0: 1- With supermount enabled, when I try to copy several files sometimes, after few minutes, some of the files in the cdrom are not recognized (the file Toshiba... is not valid). 2. I have dissabled supermount in my dvd-drive; now I can mount and umount as a user, the problem of files dissapearing is solved, but when Mandrake start ther is an error message: Fault: mount device not found. To eliminate the message is enought activating again supermount to that drive. There you have my fstab file; I have to harddisks (hda with two vfat partitions and two xfs partitions; and hdb with the main linux paritions /dev/hdb5 / ext3 defaults 1 1 /dev/hdb1 /boot ext3 defaults 1 2 none /dev/pts devpts mode=0620 0 0 /dev/hdb7 /disk xfs defaults 1 2 /dev/hdb8 /home xfs defaults 1 2 /dev/hdd /mnt/cdrom2 auto user,iocharset=iso8859-15,codepage=850,ro,umask=0 0 0 none /mnt/floppy supermount dev=/dev/fd0,fs=auto,--,iocharset=iso8859-15,sync,codepage=850,umask= 0 0 0 /dev/hda1 /mnt/win_c vfat iocharset=iso8859-15,codepage=850,umask=0 0 0 /dev/hda5 /mnt/win_d vfat iocharset=iso8859-15,codepage=850,umask=0 0 0 /dev/hdb13 /object xfs defaults 1 2 /dev/hda7 /otros xfs defaults 1 2 /dev/hda6 /pelis xfs defaults 1 2 none /proc proc defaults 0 0 /dev/hdb11 /tmp xfs defaults 1 2 /dev/hdb6 /usr xfs defaults 1 2 /dev/hdb9 /usr/share ext3 defaults 1 2 /dev/hdb10 /var xfs defaults 1 2 none mnt/cdrom supermount dev=/dev/scd0,fs=auto,ro,--,iocharset=iso8859-15,codepage=850,umask=0 0 0 /dev/hdb12 swap swap defaults 0 0 Ah!; in my laptop the problem also appears. Any idea about where the problem arises and how can it bee solved? Thanks so much in advance Francisco Alcaraz Murcia (Spain) I will run a test on this now and see what my results are. Steve Spears Ran the test and sure enough, I get the same error as well. I opened the CD-ROM with 9.0 CD-ROM #2 and created a directory and opened it. Then I did a mass select in the RPMS2 directory and drug them into the new test directory. The copy started off fine but then cam up with the error that certain files didn't exist. I clicked auto skip to see what would happened. It went on for a little bit and then just stopped. I looked in the test directory that I created and there were only a few files in there. When I went back into the CD-ROM/Mandrake/RPMS2 via Konqueror it was showing only one file. enlightenment. Being curious, I went to a konsole and did the followign: [wriker@riker wriker]$ cd /mnt/cdrom [wriker@riker cdrom]$ ls ls: Boot: No such file or directory Mandrake/ [wriker@riker cdrom]$ cd Mandrake/ [wriker@riker Mandrake]$ ls RPMS2/ [wriker@riker Mandrake]$ cd RPMS2/ [wriker@riker RPMS2]$ ls ls: a2ps-devel-4.13-14mdk.i586.rpm: No such file or directory ls: adjtimex-1.12-6mdk.i586.rpm: No such file or directory ls: am-utils-6.0.7-2mdk.i586.rpm: No such file or directory ls: apache-manual-1.3.26-6mdk.i586.rpm: No such file or directory ls:
