the drive was fine and my instrument was not — corrected, and R-542 filed
gates / gates (push) Successful in 20s
gates / gates (push) Successful in 20s
I read „formatted but not mounted" off /api/disks/candidates and briefly held it as a product fault. The storage page — the surface a household opens — says the opposite and is right: Adatlemez, /mnt/felhom-drives/adatlemez, default, active, ext4. R-542 records the real (small) defect: that endpoint offers a REGISTERED, in-use drive under „initialize", with already_mounted null. The page filters it out, so no customer sees it; it fed a formatting flow and it misled a session, which is enough. Also recorded: off-site is LIVE on this fresh box by default — „Aktív — nincs kijelölt alkalmazás" — an hour after that default shipped, with nobody pressing anything. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
This commit is contained in:
@@ -292,3 +292,23 @@ urllib.error.HTTPError: HTTP Error 403: Forbidden
|
||||
## rediscovered.
|
||||
## First attempt was refused 403 „CSRF token missing or invalid": I had read the token from a page
|
||||
## path that does not exist and the fallback did not follow its redirect. My error, not the box's.
|
||||
## CORRECTION (17:0xZ) — MY EARLIER READING WAS WRONG, and the product was fine all along.
|
||||
## I wrote that the drive was „formatted but not mounted, 42 minutes on" from
|
||||
## `/api/disks/candidates`, which lists /dev/sdb under BOTH „initialize" and „attach".
|
||||
## The storage page — the surface the household actually opens — says the opposite and is right:
|
||||
## „Adatlemez · /mnt/felhom-drives/adatlemez · Alapértelmezett · Aktív · 0.0 GB / 97.9 GB
|
||||
## · ext4 · /dev/sdb[/felhom-data] · QEMU HARDDISK · Nincs alkalmazás ezen a tárolón"
|
||||
## So the init COMPLETED: formatted, mounted, registered, set as default.
|
||||
## WHY I GOT IT WRONG: `/api/disks/candidates` reports what the AGENT sees on the bus (raw disks),
|
||||
## not what the CONTROLLER has registered. Reading a registration question off a disk-enumeration
|
||||
## endpoint is the same class this project keeps re-learning — the instrument decided the verdict.
|
||||
## No product finding about the format. One possible small row about that endpoint still offering a
|
||||
## registered, in-use drive for initialisation is checked separately below.
|
||||
## THE OFF-SITE DEFAULT, WORKING END TO END ON A FRESH BOX (this is what hub v0.116.0 shipped for):
|
||||
## „Biztonsági mentés — Távoli mentés … Aktív — nincs kijelölt alkalmazás"
|
||||
## „Távoli mentés (3. mentés) — titkosított, offsite: az alkalmazás-mentések titkosított másolata
|
||||
## egy távoli tárolóra"
|
||||
## So tier 3 is LIVE on a box installed an hour after the default was shipped — the customer did
|
||||
## nothing, the operator pressed nothing. It has no app pointed at it yet, which is the next step.
|
||||
## The drive itself: „Adatlemez · /mnt/felhom-drives/adatlemez · Alapértelmezett · Aktív ·
|
||||
## 0.0 GB / 97.9 GB · ext4 · /dev/sdb · Nincs alkalmazás ezen a tárolón".
|
||||
|
||||
Reference in New Issue
Block a user