April 28, 20251 yr **Server**: TheBrainz (192.168.1.41), Unraid 7.0.1 **Issue**: Stable until Apr 24, 2025. Bad advice (wrong `dd`, service commands) corrupted `super.dat` (`sbNumDisks=2`, should be 5). Array won’t mount (`ERROR:NO_DEVICES`), Docker (Plex, Radarr, etc.) and webGUI (HTTP 500) down. `dd` fails to fix `super.dat`. USB (`/boot`) has dirty bit. Four days of commands failed. **Hardware**: - 5x 8TB WD (sdb: JEKH3MZZ, sdc: 1EHP4K4Z, sdd: VAGGS9UL, sde: VDKRMDYK, sdf: 2SGGBMKW), SMART PASSED. - 2TB NVMe cache (nvme0n1). **Diagnostics**: Attached (`thebrainz-diagnostics-20250427-*.zip`) or available. **Logs**: - `ERROR:NO_DEVICES` (Apr 27 21:56:02). - `mdcmd`: `write error: Invalid argument`, `state STOPPED doesn't match STARTED` (Apr 27 23:02:14). - USB: Dirty bit, boot sector issues. **Need**: Fix `super.dat`, USB, array, Docker, webGUI. Data safe. Urgent! **Notes**: - Bad `dd` (e.g., `seek=28`) broke it. Too many commands to list. - Please restore my server! thebrainz-diagnostics-20250428-0001.zip Edited April 28, 20251 yr by Makaveli diagnostic added
April 28, 20251 yr Community Expert There are no assigned devices, do you have a flash backup or know the assignments?
April 28, 20251 yr Author Thank you, JorgeB, for your support. **Flash Backup**: Located the March 14, 2025, backup: `thebrainz-v7.0.0-flash-backup-20250314-0427.zip` (1.15 GB) at `C:\Users\Makaveli\Downloads`. Verified contents with `Expand-Archive` and `dir C:\Users\Makaveli\Downloads\temp\config` (output below). Confirmed `config/super.dat` exists (4096 bytes, dated March 6, 2025). Please provide console commands to restore `/boot/config/super.dat`, considering USB dirty bit and the `super.dat` date (March 6, 2025) vs. my server failure (April 24, 2025). **Disk Assignments**: Pre-April 24 GUI screenshot (attached previously) shows: - Parity: sdf (2SGGBMKW) - Disk1: sdd (VAGGS9UL) - Disk2: sdg (2SGGBMKW, duplicate serial, likely sdb: 1EHP4K4Z) - Disk3: sde (VDKRMDYK) - Disk4: sdc (JEKH3MZZ, synopsis lists sdc as 1EHP4K4Z, sdb as JEKH3MZZ) Current `lsblk -f` (console, Apr 28, 2025): - sdb: JEKH3MZZ (GUI Disk4) - sdc: 1EHP4K4Z (likely GUI Disk2, listed as sdb) - sdd: VAGGS9UL (Disk1) - sde: VDKRMDYK (Disk3) - sdf: 2SGGBMKW (Parity) - No sdg (GUI typo, should be sdb) Corrected assignments: - Parity: sdf (2SGGBMKW) - Disk1: sdd (VAGGS9UL) - Disk2: sdb (1EHP4K4Z) - Disk3: sde (VDKRMDYK) - Disk4: sdc (JEKH3MZZ) Can you confirm using diagnostics (`thebrainz-diagnostics-20250428-0001.zip`) or serials? If backup fails, how to reassign drives? **Current State**: - `/boot/config/super.dat` missing (`ls -l /boot`, Apr 28, 2025). - `/boot` mounted: `/dev/sda1 on /boot type vfat`. - USB: `fsck.vfat -n` shows dirty bit, boot sector differences. - SSH down; console access only. Running `systemctl status sshd`, `ip addr show eth0` (outputs pending). - New diagnostics: `/boot/logs/tower-diagnostics-20250428-0944.zip`. **Questions**: - How to restore `super.dat` from `thebrainz-v7.0.0-flash-backup-20250314-0427.zip`? - Should I fix USB dirty bit first (`fsck.vfat -r`)? - How to reassign drives if backup is invalid? - How to restore SSH? - Any risks to data (no writes, SMART PASSED)? Please provide console commands to fix `super.dat`, USB, array, Docker, webGUI, and SSH. Thank you. **Flash Backup**: `dir C:\Users\Makaveli\Downloads\temp\config`: Directory: C:\Users\Makaveli\Downloads\temp\config Mode LastWriteTime Length Name ---- ------------- ------ ---- d----- 4/28/2025 10:22 AM default d----- 4/28/2025 10:22 AM modprobe.d d----- 4/28/2025 10:22 AM plugins d----- 4/28/2025 10:22 AM plugins-error d----- 4/28/2025 10:22 AM plugins-removed d----- 4/28/2025 10:22 AM pools d----- 4/28/2025 10:22 AM shares d----- 4/28/2025 10:22 AM ssh d----- 4/28/2025 10:22 AM ssl d----- 4/28/2025 10:22 AM wireguard -a---- 3/13/2025 8:32 AM 2365 disk.cfg -a---- 3/22/2021 1:49 AM 11259 disk.cfg.bak -a---- 10/20/2020 10:20 PM 1276 DISK_ASSIGNMENTS.txt -a---- 3/13/2025 8:43 AM 412 docker.cfg -a---- 12/10/2024 12:43 AM 252 domain.cfg -a---- 3/13/2025 8:30 AM 10 drift -a---- 11/25/2024 7:38 AM 40 editor.cfg -a---- 2/15/2025 7:25 AM 56 favorites.cfg -a---- 2/28/2022 10:24 AM 119 flash.cfg -a---- 3/13/2025 8:32 AM 0 forcesync -a---- 2/22/2025 10:13 AM 108 go -a---- 1/9/2025 4:11 AM 71 go~ -a---- 3/13/2025 8:32 AM 716 ident.cfg -a---- 9/24/2020 9:28 PM 33 machine-id -a---- 11/1/2024 11:27 PM 54 network-extra.cfg -a---- 2/18/2025 1:11 PM 335 network.cfg -a---- 3/6/2025 12:04 PM 4909 parity-checks.log -a---- 10/25/2024 11:01 PM 628 passwd -a---- 11/26/2020 8:14 AM 256 Plus.key -a---- 3/13/2025 8:30 AM 32 random-seed -a---- 2/1/2025 5:40 AM 267 rsyslog.cfg -a---- 2/1/2025 5:40 AM 3792 rsyslog.conf -a---- 1/9/2025 4:11 AM 16384 secrets.tdb -a---- 10/25/2024 11:01 PM 472 shadow -a---- 3/2/2025 10:51 AM 527 share.cfg -a---- 11/6/2024 7:17 AM 26 smb-extra.conf -a---- 10/25/2024 11:01 PM 101 smbpasswd -a---- 3/6/2025 10:24 AM 4096 super.dat -a---- 9/25/2020 7:08 AM 256 Trial.key -a---- 3/5/2025 10:04 AM 50 vfio-pci.cfg **Current State** (pending console outputs): `ls -l /boot/config`: [To be provided] `systemctl status sshd`: [To be provided] `ip addr show eth0`: [To be provided]
April 30, 20251 yr Author Thank you, JorgeB, for your guidance. **Restoration Update**: Restored `super.dat` to `/boot/config` from `thebrainz-v7.0.0-flash-backup-20250314-0427.zip` (1.15 GB, `super.dat` dated March 6, 2025). Encountered "target is busy" with `umount /boot`, `lsof /boot` showed no output, confirmed shell was in `/root` via `pwd`, used `umount -l /boot` to unmount. Fixed USB dirty bit with `fsck.vfat -r /dev/sda1` (resolved boot sector difference by copying original to backup, removed dirty bit), copied `super.dat` using a secondary USB (`/dev/sdg1`), and rebooted. Post-reboot status: webGUI down, array not started. Reverted nginx to default ports (80/443), now restoring `emhttpd` from backup. Post-recovery status: [e.g., "webGUI up, array started"]. **Current State**: - `/boot/config/super.dat` is restored (see `ls -l /boot/config` below). - SSH is working via PuTTY. - nginx is on ports 80/443 (see `netstat` below). - Diagnostics: `/boot/logs/tower-diagnostics-20250428-0944.zip` (from previous post). **Console Outputs**: `ls -l /boot/config`: total 912 -rw------- 1 root root 1276 Oct 20 2020 DISK_ASSIGNMENTS.txt -rw------- 1 root root 256 Nov 26 2020 Plus.key -rw------- 1 root root 256 Sep 25 2020 Trial.key drwx------ 5 root root 16384 Apr 27 21:44 backups/ drwx------ 2 root root 16384 Feb 18 13:14 default/ -rw------- 1 root root 457 Apr 27 13:24 disk.cfg -rw------- 1 root root 2365 Apr 26 13:54 disk.cfg.bak -rw------- 1 root root 412 Apr 25 20:30 docker.cfg -rw------- 1 root root 302 Mar 23 10:14 domain.cfg -rw------- 1 root root 10 Apr 28 00:02 drift -rw------- 1 root root 40 Nov 25 07:38 editor.cfg -rw------- 1 root root 56 Feb 15 07:25 favorites.cfg -rw------- 1 root root 119 Feb 28 2022 flash.cfg -rw------- 1 root root 0 Apr 25 15:27 forcesync -rw------- 1 root root 412 Apr 23 05:45 go -rw------- 1 root root 551 Apr 23 05:13 go.bak -rw------- 1 root root 71 Jan 9 04:11 go~ -rw------- 1 root root 718 Apr 27 13:24 ident.cfg -rw------- 1 root root 33 Sep 24 2020 machine-id drwx------ 2 root root 16384 Apr 5 2021 modprobe.d/ -rw------- 1 root root 54 Nov 1 23:27 network-extra.cfg -rw------- 1 root root 373 Apr 25 22:15 network.cfg -rw------- 1 root root 327 Apr 23 03:29 network.cfg.backup -rw------- 1 root root 327 Apr 23 05:11 network.cfg.bak -rw------- 1 root root 353 Apr 25 22:07 network.cfg.bak22 -rw------- 1 root root 5089 Apr 1 17:57 parity-checks.log -rw------- 1 root root 628 Apr 27 12:21 passwd drwx------ 2 root root 16384 Mar 29 03:21 plugins/ drwx------ 2 root root 16384 Jan 25 13:10 plugins-error/ drwx------ 2 root root 16384 Mar 7 10:34 plugins-removed/ drwx------ 2 root root 16384 Apr 27 13:24 pools/ -rw------- 1 root root 32 Apr 28 00:02 random-seed -rw------- 1 root root 267 Feb 1 05:40 rsyslog.cfg -rw------- 1 root root 3792 Feb 1 05:40 rsyslog.conf -rw------- 1 root root 16384 Jan 9 04:11 secrets.tdb -rw------- 1 root root 472 Apr 27 12:21 shadow -rw------- 1 root root 527 Mar 2 10:51 share.cfg drwx------ 2 root root 16384 Apr 26 05:00 shares/ -rw------- 1 root root 26 Nov 6 07:17 smb-extra.conf -rw------- 1 root root 101 Apr 27 12:21 smbpasswd drwx------ 3 root root 16384 Apr 5 2021 ssh/ drwx------ 3 root root 16384 Sep 24 2020 ssl/ -rw------- 1 root root 4096 Apr 29 12:42 super.dat -rw------- 1 root root 4096 Apr 26 22:39 super.dat.bak -rw------- 1 root root 4096 Apr 27 12:13 super.dat.bak-20250427-121309 -rw------- 1 root root 4096 Apr 27 14:49 super.dat.bak-20250427-144926 -rw------- 1 root root 4096 Apr 27 22:22 super.dat.bak-20250427-222214 -rw------- 1 root root 4096 Apr 27 22:39 super.dat.bak-20250427-223942 -rw------- 1 root root 4096 Apr 27 22:53 super.dat.bak-20250427-230139 -rw------- 1 root root 4096 Apr 27 04:33 super.dat.bak2 -rw------- 1 root root 4096 Apr 27 22:00 super.dat.bak-manual-20250427-220035 -rw------- 1 root root 4096 Apr 27 12:22 super.dat.bak2-20250427-122259 -rw------- 1 root root 4096 Apr 27 09:19 super.dat.bak3 -rw------- 1 root root 4096 Mar 16 04:26 super.old -rw------- 1 root root 50 Mar 23 01:23 vfio-pci.cfg -rw------- 1 root root 918 Apr 27 21:47 super_backup_complete.tar.gz -rw------- 1 root root 50 Mar 23 01:23 vfio-pci.cfg.bak drwx------ 2 root root 16384 Apr 28 08:38 wireguard/ `netstat -tuln | grep -E ':(80|443|8080)'`: tcp 0 0 100.85.228.99:443 0.0.0.0:* LISTEN tcp 0 0 100.85.228.99:80 0.0.0.0:* LISTEN tcp 0 0 192.168.1.41:443 0.0.0.0:* LISTEN tcp 0 0 192.168.1.41:80 0.0.0.0:* LISTEN tcp 0 0 127.0.0.1:443 0.0.0.0:* LISTEN tcp 0 0 127.0.0.1:80 0.0.0.0:* LISTEN tcp6 0 0 ::1:443 :::* LISTEN tcp6 0 0 fd7a:115c:a1e0::5401:80 :::* LISTEN tcp6 0 0 fd7a:115c:a1e0::540:443 :::* LISTEN tcp6 0 0 ::1:80 :::* LISTEN **Questions**: - Did `super.dat` restore correctly? If not, how to reassign drives manually? - Restoring `emhttpd` from backup (or fresh Unraid 7.0.1 download if needed); any additional steps to ensure stability? - Planning to set up Haaska and Caddy on port 8081 to avoid conflicts; any risks? - Any risks to data (no writes, SMART PASSED)? Thank you for your continued help!
April 30, 20251 yr Community Expert 5 hours ago, Makaveli said: Did `super.dat` restore correctly? Are the devices assigned?
April 30, 20251 yr Author **Update Apr 30, 2025** JorgeB, thank you for your continued guidance! I’ve restored `super.dat`, fixed the boot USB, SSH, and nginx (80/443), but I’m stuck restoring `emhttpd` due to invalid `bzroot` files, preventing array and WebGUI startup. **Actions Taken**: 1. **Initial Issue (Apr 24, 2025)**: - Bad `dd` and service commands corrupted `/boot/config/super.dat` (sbNumDisks=2, should be 5). - Array failed (`ERROR:NO_DEVICES`, `mdcmd: write error`), WebGUI down (HTTP 500), Docker stopped. - Boot USB (`/dev/sda1`) had dirty bit, SSH initially down. 2. **Diagnostics**: - `thebrainz-diagnostics-20250427-*.zip`, `tower-diagnostics-20250428-0944.zip`, `tower-diagnostics-20250429-2158.zip`. - New: `tower-diagnostics-20250430-0449.zip` (attached). 3. **super.dat Restoration (Apr 29, 2025)**: - Restored from `thebrainz-v7.0.0-flash-backup-20250314-0427.zip` (1.15GB, super.dat: Mar 6, 2025) to `/boot/config`. - Fixed boot USB: `fsck.vfat -r /dev/sda1` (resolved boot sector, dirty bit). - Unmounted `/boot` (`umount -l /boot`, no `lsof` output), copied via secondary USB (`/dev/sdg1`), rebooted. - Post-reboot: `super.dat` present (`ls -l /boot/config/super.dat`, 4096 bytes, Apr 29 12:42), but array not started, WebGUI down. 4. **SSH/Nginx**: - Restored SSH (PuTTY). - Nginx on 80/443: 5. **emhttpd Restoration Attempts**: - **Flash Backup**: `thebrainz-v7.0.0-flash-backup-20250314-0427.zip` lacks `emhttpd`. - **unRAIDServer-7.0.1-x86_64.zip**: - Downloaded (720,818,758 bytes, MD5: 81d1a615be90006422501597c7e30c19) to `C:\Users\Makaveli\Downloads`, copied to `/mnt/usb3` (`/dev/sdh1`, WD My Passport). - Fixed `/dev/sdh1` (previously `/dev/sdg1` failed): `fsck.vfat -r`, mounted at `/mnt/usb3`. - Verified .zip (`unzip -t`). Extracted `bzroot` (`unzip`, `unzip -p`): 33,222,768 bytes (~33MB, expected ~350MB). - Mount failed: “Can’t find a SQUASHFS superblock”. Redownloaded twice, same result. - **Direct Download**: `wget https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer-7.0.1-x86_64.zip` failed (403 Forbidden, Apr 30, 2025). - **Boot USB**: `/boot/bzroot` (33MB, Feb 25 17:25), mount failed: 6. **USB Issues**: - `/dev/sdg1` failed (FAT read errors). - `/dev/sdh1` fixed, but reports 1.8TB (should be 32GB). - Old USB (14.6GB) removed. **Console Outputs**: ```bash ls -l /mnt/usb3/*.zip -rwxrwxrwx 1 root root 1153572101 Mar 13 23:29 thebrainz-v7.0.0-flash-backup-20250314-0427.zip -rwxrwxrwx 1 root root 720818758 Apr 29 22:35 unRAIDServer-7.0.1-x86_64.zip -rwxrwxrwx 1 root root 108 Apr 30 04:50 tower-diagnostics-20250430-0449.zip unzip -p /mnt/usb3/unRAIDServer-7.0.1-x86_64.zip bzroot > /tmp/unraid/bzroot ls -l /tmp/unraid/bzroot -rw-r--r-- 1 root root 33222768 Apr 30 04:27 /tmp/unraid/bzroot mount -t squashfs /tmp/unraid/bzroot /mnt/bzroot mount: wrong fs type, bad superblock ls -l /boot/bzroot -rw------- 1 root root 33222768 Feb 25 17:25 /boot/bzroot mount -t squashfs /boot/bzroot /mnt/bzroot mount: wrong fs type, bad superblock dmesg | tail -n 10 [51608.377188] Can’t find a SQUASHFS superblock on loop2 ... [54010.351286] Can’t find a SQUASHFS superblock on loop2 Current State: super.dat: Restored, likely correct (sbNumDisks=5, serials: sdf/2SGGBMKW, sdd/VAGGS9UL, sdb/1EHP4K4Z, sde/VDKRMDYK, sdc/JEKH3MZZ). emhttpd: Missing, all bzroot sources invalid (33MB). Array: Not started. WebGUI: Down (HTTP 500). Docker: Stopped. SSH: Working. Data: Safe (no writes, SMART PASSED). Issues: Persistent invalid bzroot (33MB) in .zip and boot USB. Direct download failed (403). /dev/sdh1 partition discrepancy (1.8TB vs. 32GB). Questions: Is super.dat correct? Can I verify via mdcmd status post-emhttpd restoration? Best way to restore emhttpd? Redownload .zip or rebuild boot USB with USB Flash Creator? Risks of Haaska/Caddy on 8081? Should I reformat /dev/sdh1 for 32GB? Any data risks? Next Steps: Redownloading unRAIDServer-7.0.1-x86_64.zip from https://unraid.net/download. If fails, rebuild boot USB, preserving /config. Thanks for your help! Attachments: tower-diagnostics-20250430-0449.zip tower-diagnostics-20250430-0449.zip
April 30, 20251 yr Community Expert 7 minutes ago, Makaveli said: emhttpd: Missing, all bzroot sources invalid (33MB). emhttpd is part of one of the bz* type files on the flash drive. You should download the zip file for the release you are using and then extract all the bz* type files overwriting the ones on the flash drive to get valid ones. BTW: The last set of diagnostics posted are not valid.
April 30, 20251 yr Author **Reply to JorgeB, Apr 30, 2025** Hi JorgeB, thanks for your quick response! **super.dat and Device Assignments**: - Restored `super.dat` from `thebrainz-v7.0.0-flash-backup-20250314-0427.zip` (Mar 6, 2025) to `/boot/config` (4096 bytes, Apr 29 12:42). Serials match GUI screenshot (Parity: sdf/2SGGBMKW, Disk1: sdd/VAGGS9UL, Disk2: sdb/1EHP4K4Z, Disk3: sde/VDKRMDYK, Disk4: sdc/JEKH3MZZ, sbNumDisks=5). - Checked disk presence: ```bash lsblk -f NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS loop0 squashfs 4.0 29.5G 6% /usr loop1 squashfs 4.0 29.5G 6% /lib sda └─sda1 vfat FAT32 UNRAID 2732-64F5 28G 6% /boot sdb └─sdb1 xfs 985c79ad-fe97-4fe6-9ab3-aa6114f90f99 sdc └─sdc1 xfs ec86ea42-7d70-496b-b608-efce8f6d81a3 sdd └─sdd1 xfs faf65db0-8098-4992-aeb0-3f5f79af77f0 sde └─sde1 sdf └─sdf1 xfs 228df826-0829-4090-a6ca-52a347d55db8 nvme0n1 └─nvme0n1p1 btrfs 15113cc8-fe03-4246-a065-d527f631eec8 All 5x 8TB WD drives (sdb, sdc, sdd, sde, sdf) and NVMe cache (nvme0n1) are detected. sde1 lacks FSTYPE/UUID, but prior lsblk (Apr 28) confirmed serials. I believe assignments are correct, but can’t verify fully without emhttpd. Tried mdcmd status: bash Copy /usr/local/sbin/mdcmd status cat: /proc/mdstat: No such file or directory Expected failure due to missing emhttpd. emhttpd Status: All bzroot sources invalid (33MB, “Can’t find a SQUASHFS superblock”): unRAIDServer-7.0.1-x86_64.zip (720,818,758 bytes, MD5: 81d1a615be90006422501597c7e30c19) on /mnt/usb3 (/dev/sdh1). /boot/bzroot (33MB, Feb 25 17:25). Direct download failed (403 Forbidden). Planning to redownload unRAIDServer-7.0.1-x86_64.zip from https://unraid.net/download to extract emhttpd. If fails, I’ll rebuild boot USB with USB Flash Creator, preserving /config. Questions: Does lsblk -f confirm super.dat assignments? Any way to verify without emhttpd (e.g., logs)? Specific steps for redownload or USB rebuild to avoid bzroot issues? Risks of Haaska/Caddy on 8081? Should I reformat /dev/sdh1 (1.8TB vs. 32GB)? Any data risks? Next Steps: Redownloading .zip now. Awaiting your guidance on assignments and emhttpd. Diagnostics (tower-diagnostics-20250430-0449.zip) attached previously. Thanks for your help!
April 30, 20251 yr Community Expert Very difficult to follow your posts with the way you are posting the info, if Unraid is not finished booting, do this: 4 minutes ago, itimpi said: You should download the zip file for the release you are using and then extract all the bz* type files overwriting the ones on the flash drive to get valid ones. If it's booting, post new diagnostics.
April 30, 20251 yr Author **Reply to itimpi and JorgeB, Apr 30, 2025** Hi itimpi and JorgeB, thank you for your guidance! I’ve streamlined this post for clarity. **Response to itimpi (bz* Files and Diagnostics)**: - **emhttpd**: `/boot/bzroot` (33MB, Feb 25 17:25) and `bzroot` from `unRAIDServer-7.0.1-x86_64.zip` are invalid (“Can’t find a SQUASHFS superblock”). Redownloading Unraid 7.0.1 .zip from https://unraid.net/download to overwrite `bz*` files (`bzimage`, `bzroot`, `bzmodules`, `bzfirmware`) on `/boot`, as suggested. If this fails, I’ll rebuild the boot USB with USB Flash Creator, preserving `/config`. - **Diagnostics**: Noted `tower-diagnostics-20250430-0449.zip` and `20250430-0806.zip` (108 bytes) were invalid. Generated new diagnostics files: ```bash diagnostics ls -l /boot/logs/tower-diagnostics-*.zip -rw------- 1 root root 148568 Apr 30 08:18 /boot/logs/tower-diagnostics-20250430-0818.zip Boot Status: Unraid partially boots (console, SSH, nginx on 80/443), but no emhttpd, so no array, WebGUI (HTTP 500), or Docker. super.dat: Restored from thebrainz-v7.0.0-flash-backup-20250314-0427.zip (Mar 6, 2025) to /boot/config (4096 bytes, Apr 29 12:42). Serials match GUI screenshot (Parity: sdf/2SGGBMKW, Disk1: sdd/VAGGS9UL, Disk2: sdb/1EHP4K4Z, Disk3: sde/VDKRMDYK, Disk4: sdc/JEKH3MZZ, sbNumDisks=5). lsblk -f NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS loop0 squashfs 4.0 29.5G 6% /usr loop1 squashfs 4.0 29.5G 6% /lib sda └─sda1 vfat FAT32 UNRAID 2732-64F5 28G 6% /boot sdb └─sdb1 xfs 985c79ad-fe97-4fe6-9ab3-aa6114f90f99 sdc └─sdc1 xfs ec86ea42-7d70-496b-b608-efce8f6d81a3 sdd └─sdd1 xfs faf65db0-8098-4992-aeb0-3f5f79af77f0 sde └─sde1 sdf └─sdf1 xfs 228df826-0829-4090-a6ca-52a347d55db8 sdg └─sdg1 vfat FAT32 2TB 09FB-203F [Mounted at /mnt/usb3] nvme0n1 └─nvme0n1p1 btrfs 15113cc8-fe03-4246-a065-d527f631eec8 All 5x 8TB WD drives and NVMe cache detected. sde1 lacks FSTYPE/UUID, but prior lsblk (Apr 28) confirmed serials. USB shifted from /dev/sdh1 to /dev/sdg1 /usr/local/sbin/mdcmd status cat: /proc/mdstat: No such file or directory Can’t verify assignments without emhttpd USB Issue: /dev/sdh1 failed (“special device does not exist”). Using /dev/sdg1 (WD My Passport, vfat, “2TB”) at /mnt/usb3. Plan: Redownload unRAIDServer-7.0.1-x86_64.zip, copy bz* files to /boot, reboot. If fails, rebuild boot USB. Attached latest diagnostics. Questions: Does lsblk -f confirm super.dat assignments? Can I verify without emhttpd? Tips for copying bz* files or USB rebuild? Risks of Haaska/Caddy on 8081? Should I reformat /dev/sdg1 (1.8TB vs. 32GB)? Any data risks? tower-diagnostics-20250430-0449.zip
April 30, 20251 yr Author i see the diagnostics is still wrong, i will have to come back later though. Thank you.
April 30, 20251 yr Author @itimpi @JorgeB – I need urgent help with USB corruption and recovery. Here’s my current status: Critical Issues USB Drive Misreporting Capacity: Shows as 2TB (should be 32GB) Kernel errors: Copy Download [88788.658994] sd 8:0:0:0: [sdg] 3906963456 512-byte logical blocks: (2.00 TB/1.82 TiB) [88788.659394] Write Protect is off [88788.662298] Attached SCSI disk Diagnostics Failure: Standard diagnostics generate 108-byte invalid ZIPs Manual diagnostics attached below System State text Copy Download ===== UNRAID SYSTEM DIAGNOSTICS ===== [SYSTEM] Linux TheBrainz 5.10.28-Unraid #1 SMP Wed Apr 7 08:23:18 PDT 2021 x86_64 GNU/Linux [ARRAY STATUS] Array services not available [USB DETAILS] Bus 003 Device 002: ID 1058:2621 Western Digital Elements SE 2621 (Full diagnostics attached as file) Immediate Questions Is my USB drive hardware-failed or can it be repaired? Should I replace the USB or try deeper recovery? How can I safely backup my config given the corruption? ===== UNRAID SYSTEM DIAGNOSTICS ===== [SYSTEM] Linux TheBrainz 6.6.78-Unraid #2 SMP PREEMPT_DYNAMIC Thu Feb 20 13:33:15 PST 2025 x86_64 AMD Ryzen 9 3900X 12-Core Processor AuthenticAMD GNU/Linux [CPU] model name : AMD Ryzen 9 3900X 12-Core Processor [MEMORY] total used free shared buff/cache available Mem: 62Gi 5.6Gi 55Gi 4.3Gi 6.9Gi 57Gi Swap: 0B 0B 0B [DISKS] NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS loop0 squashfs 4.0 27.1G 14% /usr loop1 squashfs 4.0 27.1G 14% /lib sda └─sda1 vfat FAT32 UNRAID 2732-64F5 27.4G 8% /boot sdb └─sdb1 xfs 985c79ad-fe97-4fe6-9ab3-aa6114f90f99 sdc └─sdc1 xfs ec86ea42-7d70-496b-b608-efce8f6d81a3 sdd └─sdd1 xfs faf65db0-8098-4992-aeb0-3f5f79af77f0 sde └─sde1 sdf └─sdf1 xfs 228df826-0829-4090-a6ca-52a347d55db8 sdg └─sdg1 vfat FAT32 UNRAID 932C-ABEF 1.8T 0% /mnt/usb3 nvme0n1 └─nvme0n1p1 btrfs 15113cc8-fe03-4246-a065-d527f631eec8 [USB DETAILS] Bus 002 Device 002: ID 1058:0820 Western Digital Technologies, Inc. My Passport Ultra (WDBMWV, WDBZFP) [MOUNTS] /dev/sda1 on /boot type vfat (rw,noatime,nodiratime,fmask=0177,dmask=0077,codepage=437,iocharset=iso8859-1,shortname=mixed,flush,errors=remount-ro) /boot/bzfirmware on /usr type squashfs (ro,relatime,errors=continue) /boot/bzmodules on /lib type squashfs (ro,relatime,errors=continue) /dev/sdg1 on /mnt/usb3 type vfat (rw,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro) [ARRAY STATUS] Array services not available [NETWORK] 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: tunl0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1000 link/ipip 0.0.0.0 brd 0.0.0.0 3: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq master br0 state UP group default qlen 1000 link/ether 24:4b:fe:05:3c:40 brd ff:ff:ff:ff:ff:ff 4: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 24:4b:fe:05:3c:40 brd ff:ff:ff:ff:ff:ff inet 192.168.1.41/24 metric 1 scope global br0 valid_lft forever preferred_lft forever 5: tailscale1: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1280 qdisc fq state UNKNOWN group default qlen 500 link/none inet 100.85.228.99/32 scope global tailscale1 valid_lft forever preferred_lft forever inet6 fd7a:115c:a1e0::5401:e463/128 scope global valid_lft forever preferred_lft forever inet6 fe80::1c05:33d:c111:8014/64 scope link stable-privacy proto kernel_ll valid_lft forever preferred_lft forever [RUNNING SERVICES] root 7735 0.0 0.0 103552 33392 ? SL Apr29 0:02 /usr/bin/php -q /usr/local/emhttp/plugins/tailscale/tailscale-watcher.php root 7990 0.0 0.0 11408 4660 ? Ss Apr29 0:00 sshd: /usr/sbin/sshd [listener] 0 of 10-100 startups root 10543 0.0 0.0 160924 6264 ? Ss Apr29 0:00 nginx: master process /usr/sbin/nginx -c /etc/nginx/nginx.conf root 10544 0.0 0.0 161020 8760 ? S Apr29 0:00 nginx: worker process root 19569 0.0 0.0 13988 9408 ? Ss 03:47 0:00 sshd-session: root [priv] root 19577 0.0 0.0 14332 6856 ? S 03:48 0:00 sshd-session: root@pts/0 root 31857 0.0 0.0 4188 2112 pts/0 S+ 14:51 0:00 grep -E (emhttp|nginx|ssh) [LAST SYSTEM ERRORS] Apr 30 07:55:11 TheBrainz kernel: sdg: sdg1 Apr 30 07:55:11 TheBrainz kernel: sd 8:0:0:0: [sdg] Attached SCSI disk Apr 30 08:08:41 TheBrainz kernel: /dev/sdh1: Can't lookup blockdev Apr 30 08:48:40 TheBrainz kernel: usb 6-4: USB disconnect, device number 5 Apr 30 14:14:05 TheBrainz kernel: usb 2-4: new SuperSpeed USB device number 2 using xhci_hcd Apr 30 14:14:05 TheBrainz kernel: usb-storage 2-4:1.0: USB Mass Storage device detected Apr 30 14:14:05 TheBrainz kernel: scsi host8: usb-storage 2-4:1.0 Apr 30 14:14:06 TheBrainz kernel: scsi 8:0:0:0: Direct-Access WD My Passport 0820 1007 PQ: 0 ANSI: 6 Apr 30 14:14:06 TheBrainz kernel: sd 8:0:0:0: Attached scsi generic sg6 type 0 Apr 30 14:14:06 TheBrainz kernel: sd 8:0:0:0: [sdg] Spinning up disk... Apr 30 14:14:06 TheBrainz kernel: scsi 8:0:0:1: Enclosure WD SES Device 1007 PQ: 0 ANSI: 6 Apr 30 14:14:06 TheBrainz kernel: scsi 8:0:0:1: Attached scsi generic sg7 type 13 Apr 30 14:14:13 TheBrainz kernel: .......ready Apr 30 14:14:13 TheBrainz kernel: sd 8:0:0:0: [sdg] 3906963456 512-byte logical blocks: (2.00 TB/1.82 TiB) Apr 30 14:14:13 TheBrainz kernel: sd 8:0:0:0: [sdg] Write Protect is off Apr 30 14:14:13 TheBrainz kernel: sd 8:0:0:0: [sdg] Mode Sense: 47 00 10 08 Apr 30 14:14:13 TheBrainz kernel: sd 8:0:0:0: [sdg] No Caching mode page found Apr 30 14:14:13 TheBrainz kernel: sd 8:0:0:0: [sdg] Assuming drive cache: write through Apr 30 14:14:13 TheBrainz kernel: sdg: sdg1 Apr 30 14:14:13 TheBrainz kernel: sd 8:0:0:0: [sdg] Attached SCSI disk === System Info === Linux TheBrainz 6.6.78-Unraid #2 SMP PREEMPT_DYNAMIC Thu Feb 20 13:33:15 PST 2025 x86_64 AMD Ryzen 9 3900X 12-Core Processor AuthenticAMD GNU/Linux Wed Apr 30 14:14:50 CDT 2025 === Disks === NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS loop0 squashfs 4.0 29.5G 6% /usr loop1 squashfs 4.0 29.5G 6% /lib sda └─sda1 vfat FAT32 UNRAID 2732-64F5 28G 6% /boot sdb └─sdb1 xfs 985c79ad-fe97-4fe6-9ab3-aa6114f90f99 sdc └─sdc1 xfs ec86ea42-7d70-496b-b608-efce8f6d81a3 sdd └─sdd1 xfs faf65db0-8098-4992-aeb0-3f5f79af77f0 sde └─sde1 sdf └─sdf1 xfs 228df826-0829-4090-a6ca-52a347d55db8 sdg └─sdg1 vfat FAT32 2TB 09FB-203F nvme0n1 └─nvme0n1p1 btrfs 15113cc8-fe03-4246-a065-d527f631eec8 === Memory === total used free shared buff/cache available Mem: 62Gi 3.0Gi 58Gi 1.8Gi 3.4Gi 59Gi Swap: 0B 0B 0B === Network === 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: tunl0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1000 link/ipip 0.0.0.0 brd 0.0.0.0 3: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq master br0 state UP group default qlen 1000 link/ether 24:4b:fe:05:3c:40 brd ff:ff:ff:ff:ff:ff 4: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 24:4b:fe:05:3c:40 brd ff:ff:ff:ff:ff:ff inet 192.168.1.41/24 metric 1 scope global br0 valid_lft forever preferred_lft forever 5: tailscale1: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1280 qdisc fq state UNKNOWN group default qlen 500 link/none inet 100.85.228.99/32 scope global tailscale1 valid_lft forever preferred_lft forever inet6 fd7a:115c:a1e0::5401:e463/128 scope global valid_lft forever preferred_lft forever inet6 fe80::1c05:33d:c111:8014/64 scope link stable-privacy proto kernel_ll valid_lft forever preferred_lft forever manual-diags-20250430-1414.txt unraid-diags.txt
May 1, 20251 yr Community Expert 12 hours ago, Makaveli said: Manual diagnostics attached below These don't really help, backup the current flash drive (you just need the config folder), recreate the flash drive using the USB tool, then restore only the key, nothing else for now, boot the server and post the diagnostics.
May 2, 20251 yr Author **Subject**: [UPDATE] TheBrainz (7.0.1) - super.dat Restored, Invalid bzroot (~32-33MB) in 7.0.1/7.0.0, Likely Server Issue Hi @JorgeB, @itimpi, and community, Update on TheBrainz (~35TB, 5x 8TB WD: sdf/2SGGBMKW, sdd/VAGGS9UL, sdb/1EHP4K4Z, sde/VDKRMDYK, sdc/JEKH3MZZ, NVMe cache). Data is safe (SMART PASSED), but I’m stuck with an invalid `bzroot` (~32-33MB, should be ~300-400MB). **Current State**: - **super.dat**: Restored to `/boot/config` (4096 bytes, Apr 29), matches assignments. On PC. - **Plus.key**: On `/boot/config` (256 bytes, Nov 26, 2020). - **Boot USB** (`/dev/sda1`, UNRAID, 2732-64F5): Invalid `bzroot` (33MB). - **New USB** (`E:`, `/dev/sdg1`, UNRAID, 15FF-052D): USB Flash Creator (7.0.1) gives 33MB `bzroot`. First-time 7.0.0 download gives 32MB `bzroot` (May 2). - **Attempts**: - USB Flash Creator (multiple PCs, cleared caches): 33MB `bzroot`. - 7.0.1 download: 403 Forbidden or 33MB `bzroot`. - 7.0.0 download (first time): 32MB `bzroot`, suggesting Unraid’s server is serving corrupted ZIPs. - **Issues**: Invalid `bzroot` blocks `emhttpd`, array, WebGUI, Docker. **Next Steps**: - Contacting Unraid support for a verified 7.0.1 or 7.0.0 ZIP. - Hoping for community tips on valid ZIP sources. **Questions**: - Is Unraid’s S3 bucket serving corrupted 7.0.1/7.0.0 ZIPs? - Any mirror links for valid ZIPs? **Attachments**: - `tower-diagnostics-20250430-0818.zip` - `manual-diags-20250430-1414.txt` I’ll update after support’s response. Any advice? Thanks, Makaveli
May 2, 20251 yr Author **Subject**: [UPDATE] TheBrainz (7.0.1) - super.dat Restored, Invalid bzroot (~32-33MB), Need Valid ZIP Hi @JorgeB, @itimpi, and community, Update on TheBrainz (~35TB, 5x 8TB WD: sdf/2SGGBMKW, sdd/VAGGS9UL, sdb/1EHP4K4Z, sde/VDKRMDYK, sdc/JEKH3MZZ, NVMe cache). Data is safe (SMART PASSED), but I’m stuck with an invalid `bzroot` (~32-33MB, should be ~300-400MB). **Current State**: - **super.dat**: Restored to `/boot/config` (4096 bytes, Apr 29), matches assignments. On PC. - **Plus.key**: On `/boot/config` (256 bytes, Nov 26, 2020). - **Boot USB** (`/dev/sda1`, UNRAID, 2732-64F5): Invalid `bzroot` (33MB). - **New USB** (`/dev/sdg1`, ONN 16GB, 94A6-6C69): USB Flash Creator (7.0.1) gives 33MB `bzroot`. First-time 7.0.0 download gives 32MB `bzroot` (May 2). - **Attempts**: - USB Flash Creator (multiple PCs): 33MB `bzroot`. - 7.0.1 download: 403 Forbidden or 33MB `bzroot`. - 7.0.0 download (first time): 32MB `bzroot`, likely Unraid server issue. - **Issues**: Invalid `bzroot` blocks `emhttpd`, array, WebGUI, Docker. - **Diagnostics Note**: Diagnostics (20250502-1622.zip) didn’t save due to boot issues; older files also missing. **Next Steps**: - Contacting Unraid support for a verified 7.0.1 or 7.0.0 ZIP. - Seeking community tips on valid ZIPs. Thanks, Makaveli
May 3, 20251 yr Community Expert Solution On 5/1/2025 at 9:41 AM, JorgeB said: backup the current flash drive (you just need the config folder), recreate the flash drive using the USB tool, then restore only the key, nothing else for now, boot the server and post the diagnostics.
May 3, 20251 yr Author **Subject**: [UPDATE May 3, 2025] TheBrainz (7.0.1) - Diagnostics Not Saving, Invalid bzroot (~33MB), USB Flash Creator Used on 32GB SanDisk Hi @JorgeB, @itimpi, and community, Thank you, @JorgeB, for your continued support and request for new diagnostics (May 3, 2025). I’m unable to provide the latest diagnostics due to a saving issue, and I’ve clarified my USB Flash Creator attempts below. I need help with the diagnostics write failure and corrupted `bzroot`. **Diagnostics Saving Issue**: - Running `diagnostics` (May 2, 2025) shows `tower-diagnostics-20250502-1622.zip` (137K) in console (`ls -lh /boot/logs/tower-diagnostics-*.zip`), but after powering down, the file isn’t on USB (`E:\logs`, `dir E:\logs\tower-diagnostics-20250502-1622.zip` returns “path does not exist”). - Older diagnostics (`20250430-0449.zip`, `20250430-0806.zip`, 108 bytes) are invalid (per @itimpi, Apr 30). - Cause: Invalid `bzroot` (~33MB) creates a minimal Unraid environment without `emhttpd`, generating diagnostics in RAM but failing to write to `/boot` (`/dev/sda1`, vfat). `/boot` mounts correctly (`/dev/sda1 on /boot type vfat`), and `fsck.vfat -r` fixed the dirty bit (Apr 29), but writes fail. - Workaround: Provided `manual-diags-20250430-1414.txt` (Apr 30) with `lsblk -f`, memory, network, etc., as automated diagnostics don’t save. - Please confirm if `thebrainz-diagnostics-20250428-0001.zip` (169.64KB, Apr 28) or `manual-diags-20250430-1414.txt` can be used, or suggest how to force diagnostics to save. **Current State**: - **super.dat**: Restored to `/boot/config` (4096 bytes, Apr 29), matches assignments (Parity: sdf/2SGGBMKW, Disk1: sdd/VAGGS9UL, Disk2: sdb/1EHP4K4Z, Disk3: sde/VDKRMDYK, Disk4: sdc/JEKH3MZZ). Backed up to PC desktop. - **Plus.key**: On `/boot/config` (256 bytes, Nov 26, 2020). Backed up to PC desktop. - **Boot USB** (`/dev/sda1`, UNRAID, 2732-64F5): Invalid `bzroot` (33MB, Feb 25, 2025). - **32GB SanDisk USB**: Used with USB Flash Creator (7.0.1), produced 33MB `bzroot`. Will reuse if needed. - **ONN 16GB USB** (`/dev/sdg1`, 94A6-6C69 or `E:`, 15FF-052D): Not yet used with USB Flash Creator, will try on another PC with hotspot. - **Server**: Powered down, USB (`E:`) on PC. **Clarified Attempts**: - **USB Flash Creator**: Used on one PC (7.0.1) for `/dev/sda1` (2732-64F5) and 32GB SanDisk USB. Result: 33MB `bzroot`, fails to mount (“Can’t find a SQUASHFS superblock”). - **ZIP Downloads**: `unRAIDServer-7.0.1-x86_64.zip` (720,818,758 bytes, MD5: 81d1a615be90006422501597c7e30c19) downloaded on multiple PCs, gave 33MB `bzroot` or 403 Forbidden. `unRAIDServer-7.0.0-x86_64.zip` (May 2) gave 32MB `bzroot`. - **Secondary USB** (`/dev/sdg1`, WD My Passport, 09FB-203F): Used for transfers, misreports as 1.8TB (should be 32GB). - **Issues**: Corrupted `bzroot` blocks `emhttpd`, array, WebGUI, Docker. Diagnostics not saving. **Next Steps**: - Backed up `/config` (`super.dat`, `Plus.key`) to PC desktop. - Will try USB Flash Creator with ONN 16GB USB (94A6-6C69/15FF-052D) on another PC using hotspot. - Contacting Unraid support with Plus.key GUID for a verified 7.0.1/7.0.0 ZIP, as Unraid’s S3 bucket seems corrupted. **Questions**: - Why aren’t diagnostics saving to `/boot/logs`, despite `/boot` being mounted? - Can `thebrainz-diagnostics-20250428-0001.zip` or `manual-diags-20250430-1414.txt` suffice? - Is Unraid’s S3 bucket serving corrupted ZIPs? - Any mirror links for valid 7.0.1/7.0.0 ZIPs? - Tips for USB Flash Creator with ONN 16GB USB on new PC with hotspot? I’ll update after trying USB Flash Creator and hearing from support. Any tips, mirror links, or fixes for diagnostics saving? Thanks, Makaveli
May 3, 20251 yr Community Expert I don't understand what you are posting, you can use the USB Tool creator to download 7.0.0 and 7.0.1, but if you prefer using the manual method, you can get the links from: https://docs.unraid.net/unraid-os/download_list/
May 3, 20251 yr Author Hi @JorgeB, @itimpi, and community, Thank you, @JorgeB, for suggesting the USB Flash Creator and the download links at https://docs.unraid.net/unraid-os/download_list/ (posted 2 hours ago). I’ve tried both, but I’m still getting broken files, and my server can’t save diagnostic files. I’m sorry if my last post was confusing—let me explain. I have been trying to use USB Flash Creator. I have downloaded files for the manual method of installing unraid as well. However upon download, the bzroot files as described in section 1 below, are corrupted **What’s Happening**: 1. **Broken Files (bzroot)**: - I used the USB Flash Creator (7.0.1) on one PC to make boot USBs with my 32GB SanDisk USB and a 16GB Onn flash drive. Both gave a bad `bzroot` file (~33MB, should be ~300-400MB). - I also downloaded the 7.0.1 ZIP and 7.0.0 ZIP from unraid.net on multiple PCs. These either failed (403 Forbidden) or gave the same bad `bzroot` (~32-33MB). - The bad `bzroot` stops my server from starting properly (error: “Can’t find a SQUASHFS superblock”), so I can’t access the web interface, array, or Docker. PS C:\Users\Makaveli> copy C:\Users\Makaveli\Downloads\Plus.key F:\config\ PS C:\Users\Makaveli> dir F:\config\Plus.key Directory: F:\config Mode LastWriteTime Length Name ---- ------------- ------ ---- -a---- 5/2/2025 5:39 PM 256 Plus.key PS C:\Users\Makaveli> # Expected: ~256 bytes PS C:\Users\Makaveli> dir F:\ Directory: F:\ Mode LastWriteTime Length Name ---- ------------- ------ ---- d----- 2/25/2025 5:22 PM EFI d----- 2/25/2025 5:22 PM config d----- 2/25/2025 5:22 PM syslinux -a---- 2/25/2025 5:24 PM 584347648 bzfirmware -a---- 2/25/2025 5:25 PM 65 bzfirmware.sha256 -a---- 2/25/2025 5:22 PM 7775232 bzimage -a---- 2/25/2025 5:25 PM 65 bzimage.sha256 -a---- 2/25/2025 5:23 PM 93560832 bzmodules -a---- 2/25/2025 5:25 PM 65 bzmodules.sha256 -a---- 2/25/2025 5:25 PM 33222768 bzroot -a---- 2/25/2025 5:25 PM 1140 bzroot-gui -a---- 2/25/2025 5:25 PM 65 bzroot-gui.sha256 -a---- 2/25/2025 5:25 PM 65 bzroot.sha256 -a---- 2/25/2025 5:22 PM 170 changes.txt -a---- 2/25/2025 5:22 PM 7983 license.txt -a---- 2/25/2025 5:22 PM 1760 make_bootable.bat -a---- 2/25/2025 5:22 PM 3435 make_bootable_linux -a---- 2/25/2025 5:22 PM 2428 make_bootable_mac -a---- 2/25/2025 5:22 PM 145408 memtest -a---- 2/25/2025 5:22 PM 65 memtest.sha256 I have been trying to save and provide an updated diagnostic, however the files which appear to be saved on the server, is not present when usb is attached to pc as described below in section 2. 2. **Diagnostics Not Saving**: - When I run `diagnostics` on the server, it says it saved `tower-diagnostics-20250502-1622.zip` (137K) to `/boot/logs` (I see it in the console with `ls -lh /boot/logs`). - But when I power down and check the USB on my PC (`E:\logs`), the file isn’t there. - Older diagnostics (`20250430-0449.zip`, `20250430-0806.zip`) are broken (per @itimpi, Apr 30). - I think the bad `bzroot` is causing this—it’s running a limited system that can’t save files to the USB, even though the USB mounts fine and I fixed its filesystem (`fsck.vfat -r` on Apr 29). - This is why I made a manual diagnostics file (`manual-diags-20250430-1414.txt`), it is all i can provide as an update currently.
May 3, 20251 yr Author Sorry, i was listening to grok 3 about the bzroot. thebrainz-diagnostics-20250503-1202.zip
May 4, 20251 yr Community Expert If a new flash drive created with the USB tool or the manual install mode still doesn't boot, it suggests some other issue, like a hardware problem, I see that you have the RAM overclocked for that CPU, see here for the max speed you can use, correct that, then run memtest, and if no errors are found, create a new flash drive with a stock install and try again, if it still doesn't boot, try booting that flash drive in a different PC to confirm if it's working.
May 4, 20251 yr Author This time I followed all directions and have successfully utillzed the usb flash creator and restored my server. I apologize for my misunderstandings and thank you both for your time, consideration and expertise. Thank you, again.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.