this post was submitted on 18 Aug 2024
19 points (100.0% liked)
linux4noobs
1340 readers
1 users here now
linux4noobs
Noob Friendly, Expert Enabling
Whether you're a seasoned pro or the noobiest of noobs, you've found the right place for Linux support and information. With a dedication to supporting free and open source software, this community aims to ensure Linux fits your needs and works for you. From troubleshooting to tutorials, practical tips, news and more, all aspects of Linux are warmly welcomed. Join a community of like-minded enthusiasts and professionals driving Linux's ongoing evolution.
Seeking Support?
- Mention your Linux distro and relevant system details.
- Describe what you've tried so far.
- Share your solution even if you found it yourself.
- Do not delete your post. This allows other people to see possible solutions if they have a similar problem.
- Properly format any scripts, code, logs, or error messages.
- Be mindful to omit any sensitive information such as usernames, passwords, IP addresses, etc.
Community Rules
- Keep discussions respectful and amiable. This community is a space where individuals may freely inquire, exchange thoughts, express viewpoints, and extend help without encountering belittlement. We were all a noob at one point. Differing opinions and ideas is a normal part of discourse, but it must remain civil. Offenders will be warned and/or removed.
- Posts must be Linux oriented
- Spam or affiliate links will not be tolerated.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
yeah, burning and saving is probably not the same. /dev/sr0 is just a so called device node. it is a special file with two numbers that are an interface to control the drive. if this file gets borked (eg. replaced by a disk image) you can recreate it using the numbers with mknod, or likely udev or something will recreate it at boot when all the hardware is detected, which triggers events to create them.
i remember vaguely there used to be links to the proper device nodes being created, usually called /dev/cdrw or /dev/cdrom maybe check for those, preferably rw and maybe yours is dvdrw or so.
good luck
I do see what appears to be a /dev/cdrom, but if I click it, it says "a file named cdrom already exists. Do you want to replace it? The file already exists in dev. Replacing it will overwrite it's contents." Just like it says with /dev/sr0. That can't be right. It's trying to save the image of this audio cd as "cdrom" under /dev/. Am I supposed to do /dev/cdrom/keasbynights or something?
no. no. that's correct. Linux is warning you that you're about to burn to the disk which will overwrite any files that are there (rewritable CD Roms are a thing and Linux doesn't necessarily know what kind it is). It's just warning you that in either case, you're writing to the disk.
It's also no uncommon to have two locations. for example, on my Ubuntu install, I have several /dev/sdX (replace X with a sequential number). One for each physical disc. Those also show up in a folder called /mnt/media but I'm not 100% why. There's probably some subtle difference that exists for security reasons that's documented.... somewhere.
Ah ok, that may be the ticket then, but it makes me really nervous to brick the drive itself or "sr1" itself. There used to be an /dev/cdrom but that is gone now.
Another user says that you're not going to brick the drive and that anything you do will probably be fixed by a reboot. If you want to be sure you're not writing to the main file system drive, the best method is to physically disconnect the device to see that the dev/srX disappears when you do so. At least, that's the method I've always used when burning SD cards for a raspberry pi.
I'll give it a shot when I'm back at it, thanks! I don't mean bricking my ssd though I mean bricking the liteon optical drive.
Look at the top level comment by the user, lurch. If I'm understating him correctly, a reboot should fix it in case that happens. Generally you need to run the
ddcommand to brick stuff in the way you're imagining. It's short for either disk duplicator or disk destroyer (if you fuck up). I suspect thecdrecordutility would prevent you from doing anything too stupid on accident.The dd command is exactly what scares me about it haha, I've bricked adapters before!
Cdrecord is going just fine with the command I'm using but the GUI for brasero is what is still confusing me. I got k3b though so once I'm back at that disk drive (likely tomorrow) I'll give that a shot, and try to just say "yes" to that overwrite of sr0 (or sr1 or whatever it is at the time) on brasero.
If in reading lurch's comment correctly, he says it's /dev/cdrom and not srX, but that the wrong thing won't break anything.
Well /dev/cdrom disappeared on me and hasn't come back, /dev/sr0 is the correct device (when using cdrecord) unless my charger is plugged in, then it's /dev/sr1.
But cool, as long as it won't break anything I'll try it!