You are not logged in.
Yeah, those were the instructions I was following. I haven't interacted much with devices in Linux, whereas I frequently cp files using "/media/user/drive" as the target. So, I read "device" in the broader sense (to include "drive"), thought "/media/etc..." and it never occurred to me to try the other, even though it did occur to me to try just about everything else. ... But, I also tanked one of my backup drives by using dd without my glasses, so, obviously I'm not the sharpest tool in the shack. ;-)
Offline
I believe I'd been outputting to /media/username/drive.
No. If you have automount enabled, in /home/<username>/, you mount partitions, not drives!
"Disk partitions are a way of breaking up a storage drive into smaller usable units. A partition is a section of a storage drive that can be treated in much the same way as a drive itself."
https://www.digitalocean.com/community/ … s-in-linux
Drive, harddrive, disk, device, are synonyms.
Last edited by rbh (2020-10-18 01:05:45)
// Regards rbh
Please read before requesting help: "Guide to getting help", "Introduction to the Bunsenlabs Lithium Desktop" and other help topics under "Help & Resources" on the BunsenLabs menu
Offline
I get confused as to the difference between devices and drives as pertaining to the various operations in Linux. I was wiping the drives between attempts and figured I'd try both file systems, just in case. At least you can't say I didn't make an effort to run down every variable on my end. ;-)
Anyway, thanks!
dd is one of those super powerful commands - I found this out the hard way once when trying to write an ISO to a USB drive and instead wiped my 1 terabyte data storage drive LOL
I now obsessively fdisk -l to check the correct drive paths before attempting a dd operation.
Offline
dd is one of those super powerful commands - I found this out the hard way once when trying to write an ISO to a USB drive and instead wiped my 1 terabyte data storage drive LOL
Yeah, that's basically exactly what I did (and not 3 minutes after reading that damn warning :-) ). I have online backups, but the downloads take forever. I've already proven I can recover the data using testdisk, but that yields no folder structure and meaningless file names. Bought a cheap 1T external hdd tonight so I can clone what's there and see if I can hack out a better solution. I've officially learned my lesson about the "convenience" of having all my data on a single hdd, let alone one that's running in an 8-year-old laptop. ... Just went ssd and will load only OS, essential tools, and a few frequently used files and/or current projects. Everything else can live solely in the cloud and/or on externals. Never again shall failure of a single drive knock me offline for days.
I now obsessively fdisk -l to check the correct drive paths before attempting a dd operation.
I REALLY need to familiarize myself with more of those sorts of tools in Linux. I'm just a hobbyist now, not a pro, and none of my friends nor family use Linux (sheep, all of them :-)). so I don't need such things often. I'm not a fan of most online learning resources and, since I have both good backups and a sense of adventure, I'm prone to just saying "f' it, what's the worst that could happen?" then pushing whatever big, red button happens to be before me... It should be noted that this approach almost always results in me finding out exactly what was the worst that could have happened and then spending days digging myself out of holes. Probably not the best approach, but exciting and keeps me learning. ;-)
Offline
I REALLY need to familiarize myself with more of those sorts of tools in Linux. I'm just a hobbyist now, not a pro, and none of my friends nor family use Linux (sheep, all of them :-)). so I don't need such things often. I'm not a fan of most online learning resources and, since I have both good backups and a sense of adventure, I'm prone to just saying "f' it, what's the worst that could happen?" then pushing whatever big, red button happens to be before me... It should be noted that this approach almost always results in me finding out exactly what was the worst that could have happened and then spending days digging myself out of holes. Probably not the best approach, but exciting and keeps me learning. ;-)
Yeah, I took plenty of risks on the command line early days and still do sometimes. Trial and error is a valid approach as long as you understand the risks, as you seem to do! But I suggest continue learning the command line, its fun and becomes more rewarding the more you learn.
Offline
But I suggest continue learning the command line, its fun and becomes more rewarding the more you learn.
I prefer the command line for most things, other than editing media. But, I've only been using linux for about a year and it typically works, so beyond installing and removing packages and swapping distros, I really haven't had much need to learn the sys admin stuff, which really isn't my thing anyway. I was quite competent under Windows, but that's because I was diagnosing and repairing broken systems all the time, whether or not it was technically my job at any given moment. Too bad more of that knowledge doesn't transfer directly over. Now, I've got all the confidence I had under Windows, as well as my typically cavalier attitude, but none of the actual specific knowledge I'd need to justify either. :-)
Offline