LinuxQuestions.org

LinuxQuestions.org (http://www.linuxquestions.org/questions/index.php)
-   Linux - Hardware (http://www.linuxquestions.org/questions/forumdisplay.php?f=18)
-   -   Optical disks won't be mounted if drive has not finished acknowledgment. (http://www.linuxquestions.org/questions/showthread.php?t=4175447352)

stf92 01-26-2013 01:59 PM

Optical disks won't be mounted if drive has not finished acknowledgment.
 
O.S.: Slackware 14.0
Kernel: 3.2.29

Hi: When I mount an optical disk in my LG GH24NS90 drive, mount will not see the media unless the drive has finished sparkling its LED. But with my old machine and drive, there was no need to wait for the drive to accept the disk.

Present motherboard is Gigabyte GA-H61M-S1 and the bus is SATA, which I for the first time use.

TobiSGD 01-28-2013 07:19 AM

I can't see a question here, so do you have an issue or did you just want to make a statement?

My personal opinion: I can't see anything wrong with this behavior.

stf92 01-28-2013 07:35 AM

If I put the disk on the tray and push the unit button to close it, then issuing a mount command should mount. In my case, you must wait until the LED turns off to issue this command, or the mount will fail. Do you think this is normal behavior?

EDIT: it's true several things changed since my last machine, in which the disk was instantly mounted: PATA to SATA, new drive and new O.S. But I do not thing Slack 14.0 has anything to do with the change.

TobiSGD 01-28-2013 08:16 AM

Quote:

Originally Posted by stf92 (Post 4879001)
If I put the disk on the tray and push the unit button to close it, then issuing a mount command should mount. In my case, you must wait until the LED turns off to issue this command, or the mount will fail. Do you think this is normal behavior?

Actually yes, I do think that. The mount command mounts filesystems, not DVD/CD-drives or the CDs/DVDs themselves. It can't complete its work until the drive makes the actual filesystem available to the system. So your new drive takes longer to do that then your old one. Changes like that happen, it can be the hardware, it can be the kernel or even the userspace software.

What would be really interesting to me is: Did only the mount command return immediately (and maybe delayed the actual mount until the filesystem was available) or was immediate access of the filesystem possible on your old system?

stf92 01-28-2013 08:22 AM

No, once issued the mount command, mount waited a time until returning the prompt. depending on things like is it a pressed disk or a burned disk? But on my new machine, if you have the machine proper (the machine cabinet) out of sight, you are forced to make an script that issues mounts until it returns with error code=0? Somewhat upsetting.

TobiSGD 01-28-2013 09:10 AM

If the disk is already in the drive the mount command behaves like you describe it (it will wait until the disk spins up and then mount the filesystem, not returning an error-code). It seems that your older drive reported to the OS that the disk is ready (too?) early.
The waiting time you complain about should only occur when you newly insert a disk, which is hard to imagine with the machine out of sight.

stf92 01-28-2013 12:06 PM

I simply tell you I've used more than four machines with optical drives and this is quite new and upsetting to me. I'm almost sure it's due to the drive or the SATA thing, which has made all my hard disks and optical drives unusable in my this new machine.


All times are GMT -5. The time now is 01:31 PM.