README.md
# DS1812+ unlock
This publication copy contains anonymized configuration examples and sanitized
ramdisks. Start with [publication notes](docs/PUBLISHING.md) before building or
installing; the sample addresses and device identities are not usable defaults.
[Post-scrub validation](docs/VALIDATION.md) records 100 Python tests, 37 PHP
checks, and generated-image handoff tests.
A Synology DS1812+, and the other Cedarview boards with the same firmware,
only start a USB stick whose ID is `F400:F400`. The loader on that stick
does not run a chained program unless `boot` follows `chainloader`
immediately. This repository records the boot recovery and provides tooling for
Debian 13 / OpenMediaVault 8 with separate OS and storage arrays.
Historical release ramdisks
contain unauthenticated diagnostics and are for recovery work only. Production
uses the secured per-device images from the rebuild procedure; recovery images
contain a private SSH host key and must not be published.
## Read this
- Narrative: [`docs/ds1812-unlock-post.md`](docs/ds1812-unlock-post.md)
- Procedure: [`docs/ds1812-unlock-guide.md`](docs/ds1812-unlock-guide.md)
- What is verified, and what is not: [`docs/ds1812-findings-2026-09-23.md`](docs/ds1812-findings-2026-09-23.md)
- Post-install repair scripts and tests: [`scripts/ds1812/postinstall/`](scripts/ds1812/postinstall/)
- Hardware monitoring and OMV integration: [`docs/ds1812-monitoring-2026-09-23.md`](docs/ds1812-monitoring-2026-09-23.md)
- Bulk shares, clients and production qualification: [`scripts/ds1812/production/`](scripts/ds1812/production/)
- Ramdisk, selector, and checksums: [`release/ds1812-unlock/`](release/ds1812-unlock/)
## Target
Debian 13 and OpenMediaVault 8, on a kernel Debian 13 still updates.
The default is a 32 GiB OS RAID1 mirrored across all eight disks and a
separate storage RAID6 using their remaining capacity. The USB remains
boot-only. See the [rebuild procedure](scripts/ds1812/rebuild/README.md).
The clean rebuild and OS restore are complete. Debian and OMV run on the OS
mirror; the separate empty data filesystem is mounted and manageable in OMV.
All eight members are present in both arrays. OS synchronization is complete;
the new RAID6 is synchronizing normally in the background.
See the [execution log](docs/ds1812-os-separation-plan.md).
The independent RAM recovery and RAM-to-Debian handoff are verified. The
normal OS boot image also passed a software reboot on 2026-09-24: Debian, SSH
and OMV returned on .4 without a physical power cycle. Healthy Debian
boots rearm the OS selector; a failed boot leaves independent RAM recovery
selected for the following start. The USB contains boot payloads only.
OMV storage operations cannot wipe, format, resize or remove the OS mirror,
its members, their parent disks or the boot USB. Debian root stays writable
for normal services and SSH administration. Unused data partitions remain
available to native RAID/filesystem operations. A live RAM-disk integration
test verified EXT4 and Btrfs creation and wiping without changing an adjacent
OS partition or either GPT header.
LAN1 uses sticker MAC `02:00:00:00:00:01` and DHCP reservation
`http://192.0.2.4/`. Both LAN interfaces appear in OMV. LAN2's name match and
optional status prevent its disconnected cable from delaying boot readiness.
SMART monitoring covers all eight bays, with scheduled tests and temperature
thresholds. CPU history and rear-fan rotation checks run without changing fan
speed. All eight green bay lights use the verified
[LED service](docs/ds1812-leds-2026-09-23.md). Monitoring is local and needs manual review unless you configure external
notifications; see the monitoring notes for hardware limits.
Historical checks before publication: 31 rebuild tests, 34 post-install tests, 13 production tests,
10 hardware tests, 6 LED tests, 21 PHP policy checks, 11 partition-backend checks
and 5 filesystem details checks pass. Both generated archives passed the packed BusyBox
handoff test. The storage integration test uses RAM only, never the NAS arrays.
Optional SMB/NFS sharing, client mounts, and disk qualification helpers are
included in the [production procedure](scripts/ds1812/production/README.md).
Supply your own client allowlist and credentials. Historical validation results
are recorded in the anonymized logs; qualify your own disks and backups.
## Layout
- `docs/` — the post, the guide, the findings, and the earlier lab notes
- `release/ds1812-unlock/` — the files meant to be published
- `scripts/ds1812/` — historical ramdisk and installer scripts
- `dist/` — local images and stick backups, not part of git
Default disk layout: [separate OS RAID1 and storage RAID6](scripts/ds1812/rebuild/README.md). The USB remains boot-only. [Migration status](docs/ds1812-os-separation-plan.md).