how to erase tinycorepure64 iso off of cd-rw disc?

[lovegate]

i was part way through installing tinycorepure64 (all i had done was put the two .gz files in their own partition and burned the iso to a cd) before realizing i didn't wanna go through with the process. i deleted the .gz files and their respective partition, so all i have left is this disc. i tried blanking it using both xfburn and cdrdao and both returned errors; cdrdao specifically said that the disc was in use, so i can't blank it. how do i make the disc... not in use so that i can blank it and put it away? ELI5 please, i'm not very experienced with computers UnU

[Rich]

Hi lovegate
Welcome to the forum.

... how do i make the disc... not in use so that i can blank it and put it away? ...

Make sure you don't have a terminal or file manager pointed at any files or
directories on the disc.

You may also need to unmount the disc.

If you booted the machine from the disc, boot from a different device, and then
blank the disc.

[lovegate]

i tried unmounting the disc but couldn't find an option to do so, so maybe i had already unmounted it and didn't notice among all the other things. i booted the system normally, so i'll give a look at your first suggestion. i think i did have my file manager open while trying to blank the disc... i'll give that a retry rq

edit: after messing around some more, i realized it's a permissions issue. the whole "disc in use" deal was a warning rather than an error. my problem is that the disc is read-only now and i'm unable to remove that setting, despite the fact that it's an rw disc

[Rich]

Hi lovegate
While the disc may be RW, once it's written to, the ISO9660 file system
makes it RO. That's because ISO9660 is a read only file system.
As long as it's still mounted, the operating system will be aware of that
and likely block you from blanking it.
Your CD is likely sr0 or sr1. To unmount:

Code: [Select]

sudo umount /dev/sr0With it unmounted, your program should be able to blank the disc.

[lovegate]

i used that command and the disc is still unable to be blanked and the device is still set to read only- same results as when i went through this same process in the file manager disc menu last night. i tried unmounting and blanking both sr1 and sr0 just in case i had the device name wrong, but neither worked (

[lovegate]

after doing a little more tinkering out of desparation (and somehow messing my whole system up??? even though i only edited disc drive settings?? :/ this is why i don't try to solve computer problems on my own...) i've realized that both of my disc drives (the one built into the computer and a usb disc drive) are r/o. is that preventing me from blanking the disc? i can't see that being the problem since i was able to burn the image onto the disc just fine, but i'm looking for any potential solutions atp. i'm almost to the point where i'm ready to just give up and store the disc as unusable, but i hate wasting things.

[Rich]

Hi lovegate
If you look at the face on the drawer of the units, you should see
either  RW  or  Writer  on it if it is capable of burning discs.

[lovegate]

oh, i never paid much attention to the writing on them! yes, they're r/w capable, so idk why they're showing up as r/o i'll have to see if they still show up as r/o tomorrow when i finish re-installing my operating system because it is 1:00am here and i have just messed up the installation process for the fifth time by picking up my external drive to check the text on it LOLLL tysm for dealing with my nonsense- i hope i can fix this problem by tomorrow and be out of your hair soon U_U

[lovegate]

i'm giving up. i've been at it for the past six or seven hours trying every possible solution i can find and nothing's worked. i think i messed the situation up further by initiating processes i didn't fully understand. oh well.

thank you again for trying as best as you could to help i wish y'all luck with the ongoing tinycore development

[scdbackup]

Hi,

maybe a command line tool which is nearer to the drive can give insight.

Get a list of recognizable optical drives:

Code: [Select]

xorriso -devices

Insert medium and inspect drive /dev/sr0 for its relation to this medium:

Code: [Select]

xorriso -outdev /dev/sr0 -list_profiles
If it recognizes the CD-RW and claims to be able to blank and write,
then you should see among others the line

Code: [Select]

Profile      : 0x000A (CD-RW) (current)
The text "(current)" indicates that the medium was recognized as CD-RW.
The text "(CD-RW)" announces that the drive can blank and write the
medium. There will also be a line with "(CD-ROM)", which announces that
the medium type can be read (if it was written and not blanked since).

If you get the complaint:

Code: [Select]

libburn : SORRY : Cannot open busy device '/dev/sr0' : Device or resource busy
then add an expert command to the xorriso run, before the -outdev command:

Code: [Select]

xorriso -drive_access shared:unrestricted -outdev /dev/sr0 -list_profiles

If the drive states that it can handle profile "CD-RW", then it would be
time to let it blank the medium.

Code: [Select]

xorriso -outdev /dev/sr0 -blank as_needed -eject all
or in case of obstinatly being busy:

Code: [Select]

xorriso -drive_access shared:unrestricted -outdev /dev/sr0 -blank as_needed -eject all
Thie latter might confuse the process which holds the drive occupied or
the Linux kernel which will not know about the new blank state of the
medium. The xorriso run at its end tries to eject the medium in order to
bring any user of the drive to the same perception of the medium state.
(If the drive has no tray motor, please eject manually.)

Burning a new ISO could then be done by:

Code: [Select]

xorriso -as cdrecord -v dev=/dev/sr0 -eject your_image_file.iso
But your usual burn program is supposed to be able to use that CD-RW
on its own.

Have a nice day

Thomas