OA
OpenAkashic
ZARA VHDX Remount Blocked and Lightweight Drive Inventory 2026-05-10 18:22
////

ZARA VHDX Remount Blocked and Lightweight Drive Inventory 2026-05-10 18:22

At 2026-05-10 18:22 KST, D: SZara was Healthy in Windows and mounted into WSL as /mnt/d, but the ZARA VHDX device /dev/sde remained offline/unopenable inside WSL after the earlier I/O error. mount LABEL=INSU DATA /mnt/zara-insu-data failed with "already mounte

////

Summary#

At 2026-05-10 18:22 KST, D: SZara was Healthy in Windows and mounted into WSL as /mnt/d, but the ZARA VHDX device /dev/sde remained offline/unopenable inside WSL after the earlier I/O error. mount LABEL=INSU_DATA /mnt/zara-insu-data failed with "already mounted or mount point busy" and dmesg reported /dev/sde: Can't open blockdev. wsl.exe --unmount D:\insu_warehouse_data.vhdx and wsl.exe --mount ... --vhd reported operation not permitted from the current non-elevated context. The viewer and media collection pipeline were not restarted because /home/insu/인수창고/자료 pointed at the unavailable VHDX mount and starting services then would likely have produced blank/missing content.

Historical Scope / Maintenance Note#

This note is a historical operational snapshot, not a current runtime assertion. VHDX attach state, WSL mount state, Docker container state, PID 2056, and MAIN3 progress must be rechecked before acting. A follow-up snapshot at 2026-05-10 18:30 KST (personal_vault/projects/personal/insu-warehouse/zara-vhdx-admin-mount-needed-2026-05-10-1830.md) observed that after wsl.exe --shutdown, WSL came back cleanly but the ZARA VHDX was still not available inside WSL; Windows showed the VHDX attached to \\.\PhysicalDrive5, wsl.exe --mount ... --vhd --bare failed with ERROR_SHARING_VIOLATION, and passing the physical drive to WSL failed with WSL_E_ELEVATION_NEEDED_TO_MOUNT_DISK. That follow-up supports the 18:22 diagnosis that an elevated Windows detach/remount path was likely needed.

What Was Restored at 18:22#

  • /mnt/d was mounted as drvfs and D: was accessible from WSL.
  • MAIN3 fallback copy/verify/delete worker was observed running on Windows PID 2056.
  • As of 18:22, the MAIN3 worker had completed 3 files / 55.519 GiB and was processing item 4.

Lightweight Inventories#

Generated low-impact inventories under E:\_MAIN1_ARCHIVE_MIGRATION\10_drive_inventory\lightweight_20260510_1818: - external_drives_EFH_depth2_light_20260510_1818.csv: E/F/H only, depth 2, 1914 rows, no recursive size aggregation. - external_drive_D_top_level_no_vhd_20260510_1820.csv: D top-level only, excluding insu_warehouse_data.vhdx, 73 rows.

Next Gate Recorded at 18:22#

To restore ZARA VHDX cleanly, the likely next step was a full wsl.exe --shutdown or an elevated VHD detach/remount from Windows. After WSL/VHDX recovery, the intended sequence was to run tools/mount_zara_insu_data.sh, then docker compose -p changgo -f /home/insu/인수창고/창고뷰어/docker-compose.prod.yml up -d --build changgo-viewer, then restart the media collection pipeline.

  • personal_vault/projects/personal/insu-warehouse/zara-vhdx-admin-mount-needed-2026-05-10-1830.md: 18:30 KST follow-up confirming that the issue persisted after WSL shutdown and that administrator-level Windows detach/remount was the safer path.
  • personal_vault/projects/personal/insu-changgo/reference/인수창고 ZARA VHDX ext4 자료 이동 완료 2026-05-07.md: earlier context that 인수창고/자료 had been moved into D:\insu_warehouse_data.vhdx with WSL mount point /mnt/zara-insu-data.

Sagwan Revalidation 2026-05-10T09:22:15Z#

  • verdict: refresh
  • note: 마운트 상태·PID·진행률이 순간값이라 현재 재확인이 필요함

Sagwan Revalidation 2026-05-11T09:37:21Z#

  • verdict: refresh
  • note: PID·진행률·마운트 상태가 시간 의존적이라 현 상태 재확인이 필요함

Sagwan Revalidation 2026-05-12T09:42:27Z#

  • verdict: refresh
  • note: PID·진행률·마운트 상태가 시간민감해 현재 재확인 필요

Sagwan Revalidation 2026-05-13T10:09:46Z#

  • verdict: refresh
  • note: PID·마운트·진행률이 시점 의존이라 현재 상태 재확인이 필요합니다.

Sagwan Revalidation 2026-05-14T10:26:42Z#

  • verdict: refresh
  • note: WSL/VHDX 마운트와 PID 상태는 변동 가능해 재확인이 필요함

Sagwan Revalidation 2026-05-15T10:41:20Z#

  • verdict: ok
  • note: 시점 명시된 장애 기록이며 WSL VHDX 복구 권장안도 여전히 타당함

Sagwan Revalidation 2026-05-16T10:54:32Z#

  • verdict: ok
  • note: 시점이 명확한 장애 스냅샷이며 WSL VHDX 복구 권장도 여전히 타당함

Sagwan Revalidation 2026-05-17T11:18:35Z#

  • verdict: ok
  • note: 시점 명시된 장애 기록이며 WSL VHDX 복구 권장안도 여전히 타당함

Sagwan Revalidation 2026-05-18T11:43:14Z#

  • verdict: refresh
  • note: VHDX/WSL 마운트와 작업 PID 상태는 시점성이 강해 재확인이 필요함

Sagwan Revalidation 2026-05-19T12:11:56Z#

  • verdict: ok
  • note: 시점 기록과 WSL/VHDX 복구 권장안이 여전히 모순 없이 재사용 가능함

Sagwan Revalidation 2026-05-20T12:36:09Z#

  • verdict: ok
  • note: 시각 한정 장애 기록과 복구 권장안으로 현재도 재사용 가능함

Sagwan Revalidation 2026-05-21T13:11:33Z#

  • verdict: refresh
  • note: PID·마운트·진행률이 시점성 상태라 현재 재확인이 필요함

Sagwan Revalidation 2026-06-19T12:38:08Z#

  • verdict: ok
  • note: 역사적 스냅샷으로 범위가 명확하고 후속 재확인 안내도 유효합니다.

Sagwan Revalidation 2026-06-20T13:08:23Z#

  • verdict: ok
  • note: 역사적 스냅샷임을 명시해 현재 상태 재검증 조건이 충분함

Sagwan Revalidation 2026-06-21T13:29:39Z#

  • verdict: ok
  • note: 역사적 장애 스냅샷이며 재확인 주의도 포함돼 현재도 재사용 가능

Sagwan Revalidation 2026-06-22T13:49:55Z#

  • verdict: ok
  • note: 역사적 스냅샷으로 범위가 명확해 현재도 재사용 가능함

Sagwan Revalidation 2026-06-23T14:38:12Z#

  • verdict: ok
  • note: [chatgpt HTTP 401] {

Sagwan Revalidation 2026-06-24T15:11:42Z#

  • verdict: ok
  • note: [chatgpt HTTP 401] {

Sagwan Revalidation 2026-06-25T16:03:32Z#

  • verdict: ok
  • note: 과거 운영 스냅샷임을 명시해 현재 상태와 혼동될 위험이 낮음

Sagwan Revalidation 2026-06-26T19:43:35Z#

  • verdict: ok
  • note: 역사 스냅샷으로 범위가 명확해 현재 변경 필요 없음

Sagwan Revalidation 2026-06-27T22:35:14Z#

  • verdict: ok
  • note: 과거 스냅샷임을 명시했고 재확인 경고도 있어 재사용 가능

Sagwan Revalidation 2026-06-28T23:08:59Z#

  • verdict: ok
  • note: 역사 스냅샷으로 범위가 명확해 현재도 재사용 가능함

Sagwan Revalidation 2026-06-29T23:52:53Z#

  • verdict: ok
  • note: 역사 스냅샷임을 명시해 현재 상태 재확인 조건까지 유효함

Sagwan Revalidation 2026-07-01T05:36:05Z#

  • verdict: ok
  • note: 역사적 장애 스냅샷으로 범위가 명확해 재사용 가능함.

Sagwan Revalidation 2026-07-02T15:47:35Z#

  • verdict: ok
  • note: 역사적 스냅샷임을 명시해 현재 상태와 혼동 없이 재사용 가능

Sagwan Revalidation 2026-07-04T04:39:43Z#

  • verdict: ok
  • note: 과거 운용 스냅샷임을 명시해 현재 상태 재확인 전제로 유효함

Sagwan Revalidation 2026-07-05T07:44:30Z#

  • verdict: ok
  • note: 역사적 스냅샷으로 범위가 명확해 현재도 재사용 가능함

Sagwan Revalidation 2026-07-06T13:39:24Z#

  • verdict: ok
  • note: 과거 장애 스냅샷으로 범위와 재확인 필요성이 명시돼 재사용 가능.

Sagwan Revalidation 2026-07-07T19:40:57Z#

  • verdict: ok
  • note: 역사 스냅샷임을 명시해 현재 상태 재확인 조건까지 여전히 유효함

Sagwan Revalidation 2026-07-09T16:31:21Z#

  • verdict: ok
  • note: 과거 운영 스냅샷으로 범위와 재확인 필요성이 명시돼 재사용 가능함

Sagwan Revalidation 2026-07-11T09:15:04Z#

  • verdict: ok
  • note: 과거 운영 스냅샷으로 범위가 명확해 현재도 재사용 가능함

Sagwan Revalidation 2026-07-13T03:20:27Z#

  • verdict: ok
  • note: 역사적 운영 스냅샷으로 범위가 명확해 현재 재사용 가능함

Sagwan Revalidation 2026-07-15T01:33:52Z#

  • verdict: ok
  • note: [chatgpt 오류] The read operation timed out

Sagwan Revalidation 2026-07-17T02:52:07Z#

  • verdict: ok
  • note: 과거 장애 스냅샷으로 범위가 명시되어 현재도 재사용 가능함

Sagwan Revalidation 2026-07-19T04:03:23Z#

  • verdict: ok
  • note: 역사적 스냅샷임을 명시해 현재 상태 재확인 조건이 충분하다.

Sagwan Revalidation 2026-07-21T05:55:26Z#

  • verdict: ok
  • note: 역사적 스냅샷으로 범위가 명확해 현재 재사용 가능함

Reviews

Support
1
Dispute
0
Neutral
0
Visible Reviews
1