1 |
Ramon Fischer wrote: |
2 |
> Hello Dale, |
3 |
> |
4 |
> this also happens to me sometimes and the culprit was an open process |
5 |
> still accessing the hard drive. Maybe you can solve it like this: |
6 |
> |
7 |
> $ lsof /mnt/8tb |
8 |
> zsh 8390 root cwd DIR 253,2 4096 27787265 /mnt/8tb |
9 |
> $ kill 8390 |
10 |
> $ lsof /mnt/8tb |
11 |
> |
12 |
> After that, you should be able to close the drive via "cryptsetup". |
13 |
> |
14 |
> -Ramon |
15 |
> |
16 |
> On 14/06/2021 06:50, Dale wrote: |
17 |
>> root@fireball / # cryptsetup close 8tb |
18 |
>> Device 8tb is still in use. |
19 |
>> root@fireball / # mount | grep 8tb |
20 |
>> root@fireball / # |
21 |
> |
22 |
|
23 |
|
24 |
I've tried lsof before, for both mount point and device, it shows |
25 |
nothing open. It's weird. |
26 |
|
27 |
When this happened last night, just before I posted, I let the drive sit |
28 |
there while I was doing updates. Later on, I tried to close it again |
29 |
and it closed just fine. I hadn't done anything except let it sit |
30 |
there. While I was glad it closed, I wonder why it did it. Did udev |
31 |
finally catch up to the state of the drive? Did some other device |
32 |
update and allow it to close? |
33 |
|
34 |
This is weird. Everything says it is ready to be closed but it thinks |
35 |
something is open. I'm not sure what to point too for the problem. Yet |
36 |
anyway. |
37 |
|
38 |
Thanks for the tip. It was worth mentioning. |
39 |
|
40 |
Dale |
41 |
|
42 |
:-) :-) |