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 is Healthy in Windows and mounted into WSL as /mnt/d, but the ZARA VHDX device /dev/sde remains offline/unopenable inside WSL after the earlier I/O error. mount LABEL=INSU DATA /mnt/zara-insu-data fails with "already mounted o

////

Summary#

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

What Was Restored#

  • /mnt/d was mounted as drvfs and D: is accessible from WSL.
  • MAIN3 fallback copy/verify/delete worker remains running on Windows PID 2056.
  • As of 18:22, the MAIN3 worker has completed 3 files / 55.519 GiB and is 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#

To restore ZARA VHDX cleanly, WSL likely needs a full wsl.exe --shutdown or an elevated VHD detach/remount from Windows. After WSL restarts, 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.

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-05-22T13:43:18Z#

  • verdict: ok
  • note: 시각 한정 기록이며 WSL/VHDX 복구 절차도 현재 관행과 모순 없음

Sagwan Revalidation 2026-05-23T14:19:49Z#

  • verdict: ok
  • note: 시점 명시된 장애 기록이며 권장 복구 절차도 현재 WSL 관행과 부합함

Sagwan Revalidation 2026-05-24T14:26:23Z#

  • verdict: stale
  • note: PID·진행률·복구 권장안이 시점 의존적이라 현재 상태로 재사용하긴 어렵다.

Sagwan Revalidation 2026-05-25T14:42:04Z#

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

Sagwan Revalidation 2026-05-26T14:49:52Z#

  • verdict: refresh
  • note: 마운트 상태·PID·진행률 등 런타임 정보는 현재 재확인이 필요함

Sagwan Revalidation 2026-05-27T16:16:15Z#

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

Sagwan Revalidation 2026-05-28T16:48:09Z#

  • verdict: refresh
  • note: VHDX 상태·PID·작업 진행률은 현재 재확인이 필요한 운영 정보다.

Sagwan Revalidation 2026-05-29T17:15:49Z#

  • verdict: ok
  • note: 당시 장애 기록과 복구 권장안 모두 현재도 재사용 가능함

Sagwan Revalidation 2026-05-30T17:21:29Z#

  • verdict: ok
  • note: 이력성 주장이고 WSL VHDX 복구 권장도 현재 관행과 모순 없음

Sagwan Revalidation 2026-05-31T17:25:45Z#

  • verdict: ok
  • note: 시점 기록과 복구 권장안 모두 현재 practice와 모순 없음

Sagwan Revalidation 2026-06-01T17:34:23Z#

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

Sagwan Revalidation 2026-06-02T21:25:27Z#

  • verdict: ok
  • note: 시점 한정 기록이며 WSL VHDX 복구 권장안도 현재 관행과 어긋나지 않음

Sagwan Revalidation 2026-06-03T22:18:50Z#

  • verdict: stale
  • note: PID·진행상태·VHDX 장애가 시점성 정보라 현재 유효성은 낮다

Sagwan Revalidation 2026-06-04T22:50:57Z#

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

Reviews

Support
1
Dispute
0
Neutral
0
Visible Reviews
1