Any boot code to ignore cd/dvd's ?

[coreplayer2]

Since 3.7.1  I get 1000's of file system errors during the boot process anytime a cd or dvd is in the tray

Maybe I need to burn a different tinycore cd but these errors occur so far on any machine I boot tinycore 3.7.1, additionally when booting to an installed tinycore.  on the hdd installed bootup these errors occur no matter the type of cd but not all dvd's in the tray.

??

[curaga]

Please post an example of the message, and when exactly do they appear.

[chattrhand]

Hi coreplayer2,

I sometimes encounter lots of error messages when trying to boot a from slightly damaged live linux CD. My old Knoppix3.1 professionally burned by Heise Verlag is just working fine, but most of my self-burned Knoppix versions have the same problems as you described here.

Check your CD/DVD burner and check whether your blank CDs are not too old or aged by storing under critical conditions.

 chattrhand

[nickjf20]

I'd be interested to know if there are any bootcodes for this function as well but for other reasons.

[coreplayer2]

Please post an example of the message, and when exactly do they appear.

Sure thing



I managed to catch this screen whilst the echo paused momentarily


Also , this occurs with every data and store purchased production music cd I have, but only with some DVD video.   To sum up, this happens with a cd or dvd (but not all) in the cd/dvd drive tray.

[Rich]

Hi coreplayer2

I think I read on the forum that the ide module was removed and that libata is now being used
exclusively. This question has come up before and to best of my knowledge there is no way to
tell libata not to probe for a drive.
It could be that your DVD drive doesn't handle CDs very well or possibly an incorrect driver.

[maro]

The reported errors remind me of my "fun & games" (mentioned here and in the other posts referenced from there) with an old CD-ROM where ejecting the CD after the boot loader phase helped me as a (limited) work-around.

In the end using the boot code of 'ide-core.nodma=X.Y' (with appropriate values for X and Y like X=1 and Y=0 for '/dev/hdc') appeared to be the proper solution. As the values for 'status' and 'error' that I can read in the picture are different to the ones I've observed I'm not certain that using said boot code will remedy the situation. But it should be nevertheless worth a shot.

[coreplayer2]

Thanks, will give that a try