Re: cdrom mount problem

2004-03-19 Thread anubis
On Fri, 19 Mar 2004 1:35 am, Chris wrote:
 *This message was transferred with a trial version of
 CommuniGate(tm) Pro*




 In summary: the only way to mount my cdrom after burning an ISO is
 to reboot first.


 Prior to 5.2.1-RC1, I was able to burn ISO imaged onto a CDRW using
 burncd, then later mount /cdrom to access the files I burned. With
 RC1 and now with 5.2.1-RELEASE, a strange thing happens:

 After a reboot, I can mount /cdrom and access files on the disc.
 But if I re-burn the ISO file, then try to mount /cdrom, I get
 this:

 cd9660: /dev/acd0: Input/output error

 BUT... if I reboot THEN try to access that same disk, it works
 fine.

I had a problem with burncd where I couldnt access the disk after 
burning.  I couldnt eject or mount it.  It required a reboot to get 
it.  I couldnt solve it but I was able to work around it by using 
cdcontrol.  See the man page for all options but breifly you can 
eject and then close the disk by
cdcontrol -f /dev/acd0 eject
cdcontrol -f /dev/acd0 close
I cant remember exactly what I did but I am sure I just ejected by 
software then put back in and it worked fine.  It was as if somehow 
something was holding onto the disk.  I thought it was maybe my 
windows partition getting lonely.






___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re[2]: cdrom mount problem

2004-03-19 Thread Chris
*This message was transferred with a trial version of CommuniGate(tm) Pro*



I had a problem with burncd where I couldnt access the disk after
burning.  I couldnt eject or mount it.  It required a reboot to get
it.  I couldnt solve it but I was able to work around it by using
cdcontrol.  See the man page for all options but breifly you can
eject and then close the disk by
cdcontrol -f /dev/acd0 eject
cdcontrol -f /dev/acd0 close
I cant remember exactly what I did but I am sure I just ejected by
software then put back in and it worked fine.  It was as if somehow
something was holding onto the disk.  I thought it was maybe my
windows partition getting lonely.


Thanks for the advice, but it's not working:

cdcontrol eject
cdcontrol close
cdcontrol: Input/output error
cdcontrol stop
cdcontrol: Device busy
cdcontrol reset
cdcontrol: Device busy
cdcontrol close
cdcontrol: Input/output error

I better call someone to peek at it, so see if the tray is open now but it was 
worth a shot!

Thanks,
Chris
_
Email harvesters eat this: [EMAIL PROTECTED]

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


cdrom mount problem

2004-03-18 Thread Chris
*This message was transferred with a trial version of CommuniGate(tm) Pro*




In summary: the only way to mount my cdrom after burning an ISO is to reboot first.


Prior to 5.2.1-RC1, I was able to burn ISO imaged onto a CDRW using burncd, then later 
mount /cdrom to access the files I burned. With RC1 and now with 5.2.1-RELEASE, a 
strange thing happens:

After a reboot, I can mount /cdrom and access files on the disc. But if I re-burn the 
ISO file, then try to mount /cdrom, I get this:

cd9660: /dev/acd0: Input/output error

BUT... if I reboot THEN try to access that same disk, it works fine.

Thanks,
Chris


_
Email harvesters eat this: [EMAIL PROTECTED]

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: cdrom mount problem

2004-03-18 Thread Martijn
Hi chris,

You first have to unmount the cdrom before you can mount
a new cd, you can do that by typing:
umount /cdrom

greets, Martijn

On Thursday 18 March 2004 16:35, Chris wrote:
 *This message was transferred with a trial version of CommuniGate(tm) Pro*




 In summary: the only way to mount my cdrom after burning an ISO is to
 reboot first.


 Prior to 5.2.1-RC1, I was able to burn ISO imaged onto a CDRW using burncd,
 then later mount /cdrom to access the files I burned. With RC1 and now with
 5.2.1-RELEASE, a strange thing happens:

 After a reboot, I can mount /cdrom and access files on the disc. But if I
 re-burn the ISO file, then try to mount /cdrom, I get this:

 cd9660: /dev/acd0: Input/output error

 BUT... if I reboot THEN try to access that same disk, it works fine.

 Thanks,
 Chris


 _
 Email harvesters eat this: [EMAIL PROTECTED]

 ___
 [EMAIL PROTECTED] mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to
 [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: cdrom mount problem

2004-03-18 Thread Lowell Gilbert
Chris [EMAIL PROTECTED] writes:

 *This message was transferred with a trial version of CommuniGate(tm) Pro*
 
 
 
 
 In summary: the only way to mount my cdrom after burning an ISO is to reboot first.
 
 
 Prior to 5.2.1-RC1, I was able to burn ISO imaged onto a CDRW using burncd, then 
 later mount /cdrom to access the files I burned. With RC1 and now with 
 5.2.1-RELEASE, a strange thing happens:
 
 After a reboot, I can mount /cdrom and access files on the disc. But if I re-burn 
 the ISO file, then try to mount /cdrom, I get this: 
 
 cd9660: /dev/acd0: Input/output error
 
 BUT... if I reboot THEN try to access that same disk, it works fine.

Try ejecting and re-loading the disk. 
I've seen some firmware that gets confused easily in these cases...
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: cdrom mount problem

2004-03-18 Thread Joshua Lokken
* Martijn [EMAIL PROTECTED] [2004-03-18 08:14]:
 Hi chris,
 
 You first have to unmount the cdrom before you can mount
 a new cd, you can do that by typing:
 umount /cdrom
 
 greets, Martijn
 
 On Thursday 18 March 2004 16:35, Chris wrote:
  *This message was transferred with a trial version of CommuniGate(tm) Pro*
 
 
 
 
  In summary: the only way to mount my cdrom after burning an ISO is to
  reboot first.
 
 
  Prior to 5.2.1-RC1, I was able to burn ISO imaged onto a CDRW using burncd,
  then later mount /cdrom to access the files I burned. With RC1 and now with
  5.2.1-RELEASE, a strange thing happens:
 
  After a reboot, I can mount /cdrom and access files on the disc. But if I
  re-burn the ISO file, then try to mount /cdrom, I get this:
 
  cd9660: /dev/acd0: Input/output error
 
  BUT... if I reboot THEN try to access that same disk, it works fine.
 
  Thanks,
  Chris


Please don't top-post.  I have used burncd since 4.5, and I have
never mounted a CD-R to burn it.  I'm sorry, I have no light to
shed on your problem, just wanted to keep your confusion to a
minimum.  Again, burning a CD-R under FreeBSD with burncd does
NOT involve mounting the drive first.

-- 
Joshua

Beauty is transitory.
Beauty survives.
-- Spock and Kirk, That Which Survives, stardate unknown
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re[2]: cdrom mount problem

2004-03-18 Thread Chris
*This message was transferred with a trial version of CommuniGate(tm) Pro*



 In summary: the only way to mount my cdrom after burning an ISO
 is to reboot first.


Try ejecting and re-loading the disk.
I've seen some firmware that gets confused easily in these cases...

I use the CDRW to burn backup files every night via cron, so driving to the machine 
(45 min away) and cycling the drive is not feasible. Further, this was never an issue 
with 4.x releases, and if I'm not mistaken, 5.1 either. I think this started somewhere 
with 5.2 and beyond.



You first have to unmount the cdrom before you can mount
a new cd, you can do that by typing:
umount /cdrom

Normally it's not in a mounted state after burning, as best I recall. But I've tried 
that several times anyway, to no avail. Thanks for the suggestion.



Looks like bug. Submit problem report on it, is only way it will be
looked at and fixed by 5.x development team.

This is possible, I guess. Makes since, as this problem cropped up after upgrading. I 
could be wrong, but it seems that since mount does not do anything different from the 
point just before reboot and just after reboot, perhaps it's more likely the burncd 
command not releasing the cdrw drive properly, or something like that...

Thanks,
Chris


_
Email harvesters eat this: [EMAIL PROTECTED]

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]