Title: Existing USB-connected RAID5 is missing from ZimaOS Storage UI after updating to v1.8.0

Aperta
  • Qualcosa non va?
#625 3 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
35/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
linux, shell
Ambito
operating-systems

Direzione di ricerca

Start by tracing how the local storage service discovers RAID devices and populates the raids table, using the reported API endpoint and /var/lib/casaos/db/local-storage.json as entry points. Compare the detected /dev/md0 metadata with the mounted filesystem information after the v1.8.0 update. Done means the existing array appears in the Storage UI and API with its mount point, capacity, and usage preserved across reboot.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Hello ZimaOS team,

After updating to ZimaOS v1.8.0 and rebooting, my existing USB-connected RAID5 array is no longer detected correctly in the ZimaOS Storage interface.

The RAID array itself is working correctly in Linux, and my data is still accessible. However, ZimaOS does not list the array in its Storage interface or API.

System information

ZimaOS version: v1.8.0

Local storage service version: v0.4.4

RAID type: RAID5

Connection: Four drives connected via USB

RAID device: /dev/md0

Filesystem: ext4

Mount point: /DATA/RAID5

RAID state: clean

Active members: 4/4, no failed drives

Capacity: approximately 17 TB

Used space: approximately 3.3 TB

Observed behavior

The RAID5 array is assembled and active in Linux.

All four RAID members are active and synchronized.

The filesystem is mounted and accessible at /DATA/RAID5.

Linux correctly reports the filesystem capacity and usage.

The ZimaOS local storage database has an empty raids table.

The API endpoint /v2/local_storage/raid?all=true returns an empty list.

The file /var/lib/casaos/db/local-storage.json recognizes the four USB-connected RAID member drives and /dev/md0, but the RAID filesystem information is incomplete: the mount point is empty and filesystem size and usage are reported as zero.

The issue appears to have started after the update to ZimaOS v1.8.0 and the subsequent reboot.

Expected behavior

ZimaOS should detect and register the existing USB-connected RAID5 array, display its correct filesystem capacity and usage, and preserve its existing mount point and data. The array should remain available after future reboots.

Request

Could you please advise how to safely restore the RAID metadata or storage database entry so that ZimaOS recognizes the existing array again, without recreating, formatting, or rebuilding it?

The data is important, so I have not attempted to create a new RAID array, format any drives, modify RAID superblocks, or manually insert records into the database.

Thank you for your help.

Lingua principale
Shell
Stelle
3.1k
Fork
130
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di IceWhaleTech/ZimaOS

Tutte le issue di IceWhaleTech/ZimaOS

Issue simili

Altre issue su Shell/Bash

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.