Everything posted by JorgeB
-
UNRAID 7.3.0 --> 7.3.1 array start/performance related issues
I've not seen that help with a similar issue, but it won't hurt, so it's worth a try.
-
(SOLVED) Is there a list of "approved" USB flash drives?
It's worth trying with a different flash drive using a stock install, no key needed, just to see if it boots.
-
UNRAID 7.3.0 --> 7.3.1 array start/performance related issues
Firmware update should be pretty safe, and you can do it from Unraid:
-
Disk 1 Unmountable after "unclean" update of OS, XFS Repair failed. Also Dockers gone.
Wrong partition layout, with the array stopped (and assuming disk1 is still sdb), type: sgdisk -o -a 8 -n 1:32K:0 /dev/sdb Reboot the server. Disk1 should then show as "wrong." Go to Tools - New Config - Keep All - Apply. Back on main check that all disks are assigned as before but with a blue icon, check "parity is already valid", start the array and post new diags.
-
UNRAID 7.3.0 --> 7.3.1 array start/performance related issues
Broadcom's site has 16.00.12.00 https://www.broadcom.com/support/download-search?pg=Storage+Adapters,+Controllers,+and+ICs&pf=Legacy+Host+Bus+Adapters&pn=SAS+9305-16e+Host+Bus+Adapter&pa=&po=&dk=&pl=&l=true
-
Andrew's testing. Don't block me Trurl!
Not really sure, @blahblahblahblah can we hide this?
-
[HELP] Disk 12 and 13 DISK_DSBL after adding 2 new drives — trailing 0 flag in dmesg **updated**
If no data was written to the emulated disks, i.e., after they got disabled, you can do a new config, check parity is already valid, and then run a correcting parity check.
-
Parity check paused — 2 disks with read errors.
You can do that, and rebuild both at the same time, but make sure the emulated disks are mounting and the contents look correct before rebuilding on top.
-
Sudden spike of errors in 12TB drives connected to SAS2308 controller
Not that I'm aware of, but the diags are after a reboot, if it happens again, post new ones before.
-
Nginx Returning 500 (And Localhost Not Loading in SafeMode)
It's optional.
-
Migrate to TPM, the process rich of error, bad experience !!
Correct, you would need to replace the smaller device with one the same size as the other one.
-
Unmountable: no pool uuid after New Config. BTRFS pool intact, manual mount works
The pool should be fine, problem is that other device, which is not part of the pool, probably it was before and was not correctly removed, if you remove or wipe that device, the pool should then mount
-
Parity check paused — 2 disks with read errors.
Both disks dropped offline; it looks more like a power/connection issue. Check/replace cables, especially if both disks share something, like a power splitter.
-
ZFS Pool for SSD. One SSD in state REMOVED (trimming)
Still same issue, it may be worth trying a different PCI slot, if you haven't yet, or a different HBA
-
Failed disk shelf - Start docker only on cache/pool device
Yes, you can do a new config with the remaining devices, then add them back the same as they were.
-
Shares & Docker Missing After Upgrade
It's the same issue as above; you have something creating this folder before the array is started: Jun 1 07:06:11 denver emhttpd: error: malloc_share_locations, 9121: Operation not supported (95): getxattr: /mnt/user/backups
-
[HELP] Disk 12 and 13 DISK_DSBL after adding 2 new drives — trailing 0 flag in dmesg **updated**
I would start by replacing the miniSAS cablw, since it's the cheaper option.
-
[SOLVED] Errors During Resilvering
I believe so.
-
Online errors on cache drives.
- Online errors on cache drives.
Btrfs is detecting data corruption on both devices. I recommend running Memtest first, then resetting the stats and keeping monitoring. If new errors come up, there's still a problem.- All SATA drives disappeared after upgrade to 7.3
If it happens again, post the diagnostics.- constant read or write, Tried File Activity app
Boot in safe mode to rule out all plugins.- Machine takes a long time to start
You can try some other stuff before, like resetting CMOS, removing all add-on cards, etc- UNRAID 7.3.0 --> 7.3.1 array start/performance related issues
It''s definitely worth a try.- Nginx Returning 500 (And Localhost Not Loading in SafeMode)
Problem with the flash drive layout, 7.3 is more strict. Back up, recreate with the USB tool, and restore the config folder. - Online errors on cache drives.