TrueNAS pool

Pool health, RAIDZ1, imports, upgrades, datasets, and SMB on the Ugreen DXP 8800 Plus @ 192.168.2.203. Admin UI: dsm.saxobroko.com.

42 entries — IDs NAS-001 through NAS-042.

NAS-001: Dashboard says pool is DEGRADED

Symptoms: TrueNAS home screen shows a yellow warning. Storage page says the pool is DEGRADED. Likely cause: One drive in the RAIDZ1 pool has failed or gone offline. Fix: 1. Open https://dsm.saxobroko.com on the home network. 2. Go to Storage and note which disk shows FAULTED or OFFLINE. 3. Write down the drive serial number and bay slot. 4. Stop heavy downloads (qBittorrent, big file copies to A:). 5. Do not pull any drive until you know which one failed. Still broken? Server When Pool Degraded

NAS-002: Pool shows FAULTED — everything red

Symptoms: Pool status is FAULTED. Shares and apps may not work. Likely cause: More than one drive failed, or the pool lost too many disks at once. Fix: 1. Do not destroy or reformat the pool. 2. Power the NAS on and leave it running. 3. Open Storage and count how many drives show errors. 4. If two or more drives failed, stop using the NAS and seek professional data recovery. 5. If only one drive failed but pool says FAULTED, check Alerts for import or config errors. Still broken? Server When Pool Degraded

NAS-003: Resilver stuck or very slow

Symptoms: After replacing a drive, resilver progress barely moves for hours or days. Likely cause: Large pool (7×16 TB RAIDZ1) — rebuild takes many hours. Heavy use slows it down. Fix: 1. Open Storage → pool → check resilver percent and ETA. 2. Pause qBittorrent and large SMB copies from Windows A: drive. 3. Leave the NAS powered on — do not reboot during resilver. 4. Check Alerts for new disk errors. 5. If stuck at 0% for over 24 hours, verify the new drive is the same size or larger. Still broken? Server When Pool Degraded

NAS-004: Cannot open dsm.saxobroko.com from outside home

Symptoms: Browser times out or cannot reach TrueNAS when away from home. Likely cause: Cloudflare tunnel or cloudflared app may be down, or home internet is out. Fix: 1. Try https://192.168.2.203 while on home Wi‑Fi. 2. If LAN works, check cloudflared app in TrueNAS Apps. 3. Check status.saxobroko.com for broader outages. 4. See Cloudflare tunnel FAQ if tunnel is the issue. Still broken? Home Truenas Basics

NAS-005: Cannot open TrueNAS on LAN (192.168.2.203)

Symptoms: https://192.168.2.203 does not load on home network. Likely cause: NAS is off, wrong network, or IP changed. Fix: 1. Confirm PC/phone is on home Wi‑Fi (not guest network). 2. Ping 192.168.2.203 from a PC. 3. Check the Ugreen DXP 8800 Plus has power and network LED lit. 4. Try the physical display/port if available, or power-cycle after 30 seconds off. Still broken? Home Turn Everything On

NAS-006: Forgot TrueNAS admin password

Symptoms: Login page rejects your username and password. Likely cause: Wrong password saved, or password was changed and not updated in Vaultwarden. Fix: 1. Check Vaultwarden for TrueNAS admin credentials. 2. If still locked out, you need console access to reset — see TrueNAS docs or ask Ryan. 3. Do not guess repeatedly and lock the account. Still broken? Access Open Vaultwarden

NAS-007: Pool imported as UNAVAIL after reboot

Symptoms: After power cycle, pool shows UNAVAIL or will not import. Likely cause: Drives did not all spin up, cable loose, or drive failed during boot. Fix: 1. Wait 5 minutes after boot for all drives to spin up. 2. Storage → Disks — check all 7 (or 8) drives are ONLINE. 3. Try Import if pool shows as available but not mounted. 4. If a drive is missing, treat as degraded — do not create a new pool. Still broken? Server When Pool Degraded

NAS-008: Accidentally clicked Destroy Pool

Symptoms: You see a destroy prompt or started wipe by mistake. Likely cause: Mis-click in Storage settings. Fix: 1. Cancel immediately — do not confirm destroy. 2. If destroy already ran, data may be unrecoverable without backups. 3. STOP and read backups FAQ before any further action. Still broken? Handover First 24 Hours

NAS-009: Dataset quota exceeded — app cannot write

Symptoms: Jellyfin, arr, or qBittorrent logs say no space or quota exceeded. Likely cause: A dataset has a quota set and is full, even if pool has free space elsewhere. Fix: 1. Storage → Datasets → find the dataset with red usage. 2. Increase quota or remove quota limit if safe. 3. Or delete unneeded files in that dataset only. Still broken?* Server Check Disk Space

NAS-010: SMB share A: drive missing on Windows

Symptoms: Windows Explorer no longer shows A: or says network path not found. Likely cause: NAS offline, share disabled, or Windows disconnected the mapping. Fix: 1. Confirm NAS is up at 192.168.2.203. 2. Try \192.168.2.203\Media or the share name from TrueNAS Shares. 3. Remap A: via Map network drive if needed. 4. Check TrueNAS Shares → SMB is enabled. Still broken? Home Windows Pc Basics

NAS-011: SMB share works but is very slow

Symptoms: Copying to A: takes forever; Jellyfin buffers. Likely cause: Pool degraded, scrub/resilver running, or network issue. Fix: 1. Check pool health in TrueNAS. 2. See if scrub or resilver is active. 3. Use wired Ethernet on PC if on Wi‑Fi. 4. Pause torrents during large copies. Still broken? Server Check Disk Space

NAS-012: Permission denied on SMB share

Symptoms: Windows says you do not have permission to access \truenas... Likely cause: Wrong SMB user, ACL, or guest access disabled. Fix: 1. Use credentials from Vaultwarden for SMB user. 2. TrueNAS → Shares → SMB → edit share permissions. 3. On Windows, disconnect and reconnect with correct username. Still broken? Home Windows Pc Basics

NAS-013: TrueNAS upgrade failed mid-install

Symptoms: Update screen shows error or system stuck on older version. Likely cause: Network drop during download or insufficient boot environment space. Fix: 1. Check Alerts for upgrade error details. 2. Retry update from System → Update when network is stable. 3. Do not power off during update. 4. If system boots, pool data is usually safe even if update failed. Still broken? Home Truenas Basics

NAS-014: After TrueNAS upgrade apps won't start

Symptoms: Docker apps show stopped after OS update. Likely cause: Apps need restart or chart version mismatch after major upgrade. Fix: 1. Apps → Installed → restart each critical app. 2. Check cloudflared, Jellyfin, NPM first. 3. Review app logs in TrueNAS UI. 4. See Docker apps FAQ for per-app issues. Still broken? Server Restart Docker App

NAS-015: New drive not detected in Storage

Symptoms: Installed 8th drive but it does not appear in Disks list. Likely cause: Drive not seated, not powered, or needs rescan. Fix: 1. Power down safely if not hot-swappable. 2. Reseat drive and SATA/NVMe connection. 3. Boot and Storage → Disks → Rescan. 4. Confirm drive is same interface as other pool drives. Still broken? Server When Pool Degraded

NAS-016: Expand pool wizard greyed out

Symptoms: Cannot start pool expansion after adding 8th drive. Likely cause: Drive not formatted/unused, or pool is degraded. Fix: 1. Fix any degraded status first. 2. New drive must be Wiped or unused — not part of another pool. 3. Follow expansion steps in backups runbook. Still broken? Server When Pool Degraded

NAS-017: Snapshot rollback greyed out

Symptoms: Cannot roll back dataset to earlier snapshot. Likely cause: Snapshots disabled, wrong dataset selected, or clones exist. Fix: 1. Storage → Snapshots — confirm snapshots exist. 2. Stop apps using that dataset before rollback. 3. Rollback destroys changes after snapshot time — confirm first. Still broken? Server Export Photos Safely

NAS-018: ZFS checksum errors in Alerts

Symptoms: Alerts mention checksum errors or data integrity issues. Likely cause: Silent bit rot or failing drive — ZFS detected bad blocks. Fix: 1. Note which drive/vdev is mentioned. 2. Run an immediate scrub. 3. Run SMART long test on suspect disk. 4. Replace drive if errors repeat. Still broken? Server Read Smart Disk Errors

NAS-019: Pool at 90%+ capacity warning

Symptoms: Dashboard warns pool is almost full. Likely cause: Media, photos, and downloads filling RAIDZ1 space. Fix: 1. Check largest datasets in Storage. 2. Remove old torrents and duplicates safely. 3. Plan expansion or archive to external drive. 4. Full pools risk failed writes and instability. Still broken? Server Check Disk Space

NAS-020: Cannot delete file — dataset is read-only

Symptoms: Error says dataset or pool is read-only. Likely cause: Pool degraded beyond safe writes, or admin set read-only. Fix: 1. Check pool health — degraded pools may go read-only. 2. Storage → dataset → clear Read-only if health is OK. 3. Fix underlying disk issue before writing again. Still broken? Server When Pool Degraded

NAS-021: Import pool from old Synology migration

Symptoms: Migrated disks show foreign pool or import prompt. Likely cause: Pool was moved from Synology to TrueNAS on same or new drives. Fix: 1. Use Import — never create new pool on same disks. 2. Confirm drive order and labels. 3. After import, verify shares and app paths still match. Still broken? Basics What Is Truenas

NAS-022: Dataset compression setting broke app

Symptoms: App errors after enabling lz4 or gzip on dataset. Likely cause: Some apps expect uncompressed or specific block sizes. Fix: 1. Revert compression to inherit or off for that dataset. 2. Restart affected Docker app. 3. Test write with a small file. Still broken? Server Restart Docker App

NAS-023: Recordsize change caused poor performance

Symptoms: Large file copies slower after tuning dataset. Likely cause: Wrong recordsize for workload (e.g. small files vs media). Fix: 1. Media datasets often use 1M recordsize; app configs use default. 2. Change only with guidance — wrong settings need dataset recreate. 3. When unsure, leave defaults. Still broken? Server Check Disk Space

NAS-024: Child dataset not visible in SMB share

Symptoms: Subfolder exists in TrueNAS but not on Windows A:. Likely cause: Share path points to parent only, or nested share not exported. Fix: 1. Shares → SMB → confirm path includes needed dataset. 2. Create separate share or adjust ACL on child dataset. 3. Refresh Windows Explorer (F5). Still broken? Home Windows Pc Basics

NAS-025: ACL permissions confusing — everyone denied

Symptoms: After ACL edit, nobody can access files. Likely cause: ACL inheritance broken or explicit deny added. Fix: 1. Reset ACL to inherit from parent dataset. 2. Use a known-good SMB user from Vaultwarden. 3. Avoid mixing NFS and SMB ACL models on same folder. Still broken? Home Windows Pc Basics

NAS-026: NFS share needed for app but won't mount

Symptoms: Docker app expects NFS mount and fails. Likely cause: NFS service off, wrong export path, or firewall. Fix: 1. Services → NFS — enable if required. 2. Match export path to app host path. 3. Prefer local dataset mount for TrueNAS apps when possible. Still broken? Basics What Is Docker

NAS-027: iSCSI not needed but shows in Storage

Symptoms: iSCSI targets visible and confusing. Likely cause: Default TrueNAS modules — not used in this homelab. Fix: 1. Ignore iSCSI unless Saxon documented a use. 2. Do not delete pool thinking iSCSI is required. Still broken? Basics What Is Truenas

NAS-028: Alerts email not arriving

Symptoms: Expected pool alert emails never show up. Likely cause: SMTP not configured in TrueNAS. Fix: 1. System → Alert Services → configure email. 2. Use Gmail app password or SMTP from Vaultwarden. 3. Send test alert. 4. Until fixed, check dashboard manually weekly. Still broken? Home Check Status Page

NAS-029: Middleware failed to start on boot

Symptoms: TrueNAS UI loads but services show errors. Likely cause: Database corruption or failed app blocking middleware. Fix: 1. Reboot once and wait 10 minutes. 2. Check System → Advanced → Init/Shutdown scripts. 3. Disable recently added apps if boot loop. 4. Community forums or Ryan for persistent middleware errors. Still broken? Home Truenas Basics

NAS-030: Certificate warning on LAN login

Symptoms: Browser warns certificate not trusted at 192.168.2.203. Likely cause: Self-signed TrueNAS cert — normal on LAN. Fix: 1. Proceed only on home network you trust. 2. Or install TrueNAS CA cert on your PC. 3. Public access uses Cloudflare — different cert path. Still broken? Basics What Is Cloudflare

NAS-031: Two-factor login locked me out of TrueNAS

Symptoms: 2FA code rejected on admin login. Likely cause: Time drift on phone or lost authenticator. Fix: 1. Use backup codes if saved in Vaultwarden. 2. Console recovery may be needed — ask Ryan. 3. Do not disable 2FA without understanding risk. Still broken? Access Login Troubleshooting

NAS-032: Replication task failing to second NAS

Symptoms: Replication shows errors — no second NAS in Saxon setup. Likely cause: Legacy task from old plan or typo in remote host. Fix: 1. Disable unused replication tasks. 2. This homelab uses snapshots on same pool — see backups FAQ. 3. Do not point replication at wrong IP. Still broken? Server Export Photos Safely

NAS-033: Cloud sync task stuck

Symptoms: TrueNAS cloud sync task not completing. Likely cause: Cloud credentials expired or API limit. Fix: 1. Check task logs in Data Protection. 2. Re-enter cloud credentials from Vaultwarden. 3. Confirm off-site backup strategy in SaxDocs. Still broken? Server Export Photos Safely

NAS-034: Dataset name with space breaks script

Symptoms: Automation fails on dataset with spaces. Likely cause: Shell scripts and some apps dislike spaces in paths. Fix: 1. Rename dataset to use underscores. 2. Update app mount paths after rename. 3. Restart apps. Still broken? Server Restart Docker App

NAS-035: Pool label wrong after import

Symptoms: Pool shows old name from previous system. Likely cause: Imported pool keeps original pool name. Fix: 1. Renaming pool is advanced — only if documented. 2. Apps use mount paths — name may not matter. 3. Do not rename without backup. Still broken? Basics What Is Truenas

NAS-036: Hot spare not kicking in

Symptoms: Configured spare did not replace failed drive automatically. Likely cause: Hot spare not configured on this RAIDZ1 layout. Fix: 1. RAIDZ1 here uses manual replace — follow degraded guide. 2. Replace failed drive physically, then let resilver run. Still broken? Server When Pool Degraded

NAS-037: Drive shows REMOVED but still in slot

Symptoms: UI says REMOVED; drive is physically present. Likely cause: Loose connector, failing drive controller, or USB/SATA glitch. Fix: 1. Reseat drive with NAS powered off if needed. 2. Check cable and backplane. 3. If repeats on same slot, suspect backplane or HBA. Still broken? Server When Pool Degraded

NAS-038: Cannot create snapshot — out of space

Symptoms: Snapshot fails though pool reports free space. Likely cause: Snapshot metadata or reservation limits. Fix: 1. Check dataset reserved space. 2. Delete old snapshots to free metadata. 3. Ensure pool is not actually full. Still broken? Server Check Disk Space

NAS-039: Performance fine but latency spikes

Symptoms: Random slow periods browsing A: or Jellyfin. Likely cause: Scrub, SMART test, or Windows indexer hitting disk. Fix: 1. Check active tasks in TrueNAS. 2. Schedule scrubs off-peak. 3. Exclude network drive from Windows Search indexing. Still broken? Server Run Pool Scrub

NAS-040: TrueNAS time wrong — certs and logs fail

Symptoms: System clock off by hours; SSL or sync issues. Likely cause: NTP not configured or blocked. Fix: 1. System → General → set timezone (Australia). 2. Enable NTP servers. 3. Sync time before troubleshooting TLS. Still broken? Home Truenas Basics

NAS-041: Ryan inherited NAS — where to start

Symptoms: Brother Ryan needs to operate TrueNAS after handover. Likely cause: New operator without prior NAS experience. Fix: 1. Read handover guide and will tech section. 2. Get Vaultwarden access for all passwords. 3. Bookmark dsm.saxobroko.com and this FAQ. 4. Never destroy pool without expert help. Still broken? Handover Who Gets What

NAS-042: Everything on NAS feels broken at once

Symptoms: Apps, shares, and UI all failing together. Likely cause: Usually pool health, power, or network — not five separate bugs. Fix: 1. Check power and network first. 2. Open TrueNAS UI — pool status. 3. Check status.saxobroko.com. 4. Fix pool before restarting every app individually. Still broken? Handover First 24 Hours