Timeline for What can I do to determine why my hdd is not mounting?
Current License: CC BY-SA 4.0
16 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Nov 1, 2019 at 7:46 | vote | accept | topencrypt | ||
Oct 29, 2019 at 10:52 | history | edited | topencrypt | CC BY-SA 4.0 |
added 665 characters in body
|
Oct 29, 2019 at 10:51 | comment | added | topencrypt | @KamilMaciorowski Yes, my input on this one was very disorganized, agreed. There are 2 hdds: host: 4tb.gold; destination: boo.boo. I see what you are saying: "4tb.gold" is NOT a hdd, but rather, a partition; my mistake. The destination hdd was encrypted before the duplication process. | |
Oct 29, 2019 at 10:39 | comment | added | Kamil Maciorowski |
Another example, one of your comments: "dev/mapper" likely had 1 [partition] . What? If /dev/mapper/boo.boo exists then /dev/mapper is a directory, it cannot have partitions. Such inconsistencies on the edge of mumbo-jumbo make the task of writing a good answer very hard.
|
|
Oct 29, 2019 at 10:38 | answer | added | grawity_u1686 | timeline score: 1 | |
Oct 29, 2019 at 10:28 | comment | added | Kamil Maciorowski |
I've seen few questions of yours and frankly it seems you perform some voodoo. You're experimenting, asking and trying to learn. These are good. But frankly sometimes you're not able to explain your setup, you get partial answers or comments that doesn't necessarily match the case and add to the confusion. E.g.: now you're saying "Originally mount the hdd" just after you call 4tb.gold and boo.boo hdds. Which one is "the hdd"? And then there is sdx (the only thing I would call hdd here). So three hdds? How is cryptsetup involved?
|
|
Oct 29, 2019 at 10:21 | history | edited | topencrypt | CC BY-SA 4.0 |
added 106 characters in body
|
Oct 29, 2019 at 10:18 | comment | added | topencrypt | @AttieThe source hdd was not mounted, only the empty destination. If the source hdd was not mounted, would you still say that the source hdd may have a corrupt image? I know the destination hdd may be useless. I think I need to remove encryption from the destination hdd and redo the duplication with no encryption and no mounted device. | |
Oct 29, 2019 at 10:16 | comment | added | Kamil Maciorowski |
When you write "originally mount the hdd", it's not clear if you mean sdx or boo.boo . Were/are you able to mount /dev/sdx ? (and I don't mean sdx1 or so). If not, then it's normal you cannot just mount boo.boo now, regardless of what you could do with boo.boo before.
|
|
Oct 29, 2019 at 10:13 | comment | added | topencrypt | @KamilMaciorowski Updated question. "sdx" has 3 partitions, "dev/mapper" likely had 1. | |
Oct 29, 2019 at 10:13 | comment | added | Attie |
"destination hdd was mounted before running that command" ... not a good idea - you may have corrupted the image due to this. Try again, but first unmount both source and destination filesystems. Additionally /dev/mapper/boo.boo is somewhat equivalent to a partition (i.e: /dev/sdx1 ), not a disk (i.e: /dev/sdx ), so use /dev/sdx1 (or whatever is appropriate) as the source.
|
|
Oct 29, 2019 at 10:10 | history | edited | topencrypt | CC BY-SA 4.0 |
added 4 characters in body
|
Oct 29, 2019 at 10:05 | history | edited | topencrypt | CC BY-SA 4.0 |
added 4 characters in body
|
Oct 29, 2019 at 9:59 | history | edited | topencrypt | CC BY-SA 4.0 |
added 66 characters in body
|
Oct 29, 2019 at 9:56 | answer | added | binarym | timeline score: 1 | |
Oct 29, 2019 at 9:52 | history | asked | topencrypt | CC BY-SA 4.0 |