-
Posts
60374 -
Joined
-
Last visited
-
Days Won
630
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Report Comments posted by JorgeB
-
-
5 hours ago, bmartino1 said:
? may need to look into rasdaemon...
LT is already aware of this, I think they were looking to use rasdaemon for v6.13
-
1 minute ago, mgrinspan said:
but possibly 2 of them are on the "wrong" ports?
If there are 10 ports, 5 of them will from a SATA port multiplier, so with v6.12.9 you could only use 5 device tops, from what I've found, it was a change in the kernel that will make any devices connected to a SATA PM on these controllers unavailable, because apparently they don't report the PM as they should, this change has already been reverted, but it didn't make it to the kernel this release is using.
P.S. note that controllers with port multipliers are generally not recommended, but because of other issues that they can have, not this.
-
Same as this one:
Is this a 6 port controller or does it have more ports, i.e., it has a SATA port multiplier?
-
@blue8lucianis this a 6 port controller or does it have more ports, i.e., it has a SATA port multiplier?
-
OK, I see that @dlandonis already taking a look.
-
This looks like a controller/kernel issue, some of these controllers, despite having only 6 SATA ports, list much more in the kernel, example from your Asmedia1166 controller and v6.12.8, it's listing 30 good ports, just 2 dummy:
Mar 27 18:18:42 MedHP kernel: ata1: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc780100 irq 59 Mar 27 18:18:42 MedHP kernel: ata2: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc780180 irq 59 Mar 27 18:18:42 MedHP kernel: ata3: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc780200 irq 59 Mar 27 18:18:42 MedHP kernel: ata4: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc780280 irq 59 Mar 27 18:18:42 MedHP kernel: ata5: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc780300 irq 59 Mar 27 18:18:42 MedHP kernel: ata6: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc780380 irq 59 Mar 27 18:18:42 MedHP kernel: ata7: DUMMY Mar 27 18:18:42 MedHP kernel: ata8: DUMMY Mar 27 18:18:42 MedHP kernel: ata9: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc780500 irq 59 Mar 27 18:18:42 MedHP kernel: ata10: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc780580 irq 59 Mar 27 18:18:42 MedHP kernel: ata11: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc780600 irq 59 Mar 27 18:18:42 MedHP kernel: ata12: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc780680 irq 59 Mar 27 18:18:42 MedHP kernel: ata13: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc780700 irq 59 Mar 27 18:18:42 MedHP kernel: ata14: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc780780 irq 59 Mar 27 18:18:42 MedHP kernel: ata15: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc780800 irq 59 Mar 27 18:18:42 MedHP kernel: ata16: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc780880 irq 59 Mar 27 18:18:42 MedHP kernel: ata17: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc780900 irq 59 Mar 27 18:18:42 MedHP kernel: ata18: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc780980 irq 59 Mar 27 18:18:42 MedHP kernel: ata19: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc780a00 irq 59 Mar 27 18:18:42 MedHP kernel: ata20: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc780a80 irq 59 Mar 27 18:18:42 MedHP kernel: ata21: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc780b00 irq 59 Mar 27 18:18:42 MedHP kernel: ata22: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc780b80 irq 59 Mar 27 18:18:42 MedHP kernel: ata23: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc780c00 irq 59 Mar 27 18:18:42 MedHP kernel: ata24: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc780c80 irq 59 Mar 27 18:18:42 MedHP kernel: ata25: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc780d00 irq 59 Mar 27 18:18:42 MedHP kernel: ata26: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc780d80 irq 59 Mar 27 18:18:42 MedHP kernel: ata27: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc780e00 irq 59 Mar 27 18:18:42 MedHP kernel: ata28: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc780e80 irq 59 Mar 27 18:18:42 MedHP kernel: ata29: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc780f00 irq 59 Mar 27 18:18:42 MedHP kernel: ata30: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc780f80 irq 59 Mar 27 18:18:42 MedHP kernel: ata31: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc781000 irq 59 Mar 27 18:18:42 MedHP kernel: ata32: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc781080 irq 59
With 6.12.9 looks like the kernel is enforcing just 6 ports, so all ports after ATA6 are considered dummy ports:
Mar 27 18:13:36 MedHP kernel: ahci 0000:04:00.0: ASM1166 has only six ports Mar 27 18:13:36 MedHP kernel: ata1: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc780100 irq 62 Mar 27 18:13:36 MedHP kernel: ata2: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc780180 irq 62 Mar 27 18:13:36 MedHP kernel: ata3: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc780200 irq 62 Mar 27 18:13:36 MedHP kernel: ata4: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc780280 irq 62 Mar 27 18:13:36 MedHP kernel: ata5: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc780300 irq 62 Mar 27 18:13:36 MedHP kernel: ata6: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc780380 irq 62 Mar 27 18:13:36 MedHP kernel: ata7: DUMMY Mar 27 18:13:36 MedHP kernel: ata8: DUMMY Mar 27 18:13:36 MedHP kernel: ata9: DUMMY Mar 27 18:13:36 MedHP kernel: ata10: DUMMY Mar 27 18:13:36 MedHP kernel: ata11: DUMMY Mar 27 18:13:36 MedHP kernel: ata12: DUMMY Mar 27 18:13:36 MedHP kernel: ata13: DUMMY Mar 27 18:13:36 MedHP kernel: ata14: DUMMY Mar 27 18:13:36 MedHP kernel: ata15: DUMMY Mar 27 18:13:36 MedHP kernel: ata16: DUMMY Mar 27 18:13:36 MedHP kernel: ata17: DUMMY Mar 27 18:13:36 MedHP kernel: ata18: DUMMY Mar 27 18:13:36 MedHP kernel: ata19: DUMMY Mar 27 18:13:36 MedHP kernel: ata20: DUMMY Mar 27 18:13:36 MedHP kernel: ata21: DUMMY Mar 27 18:13:36 MedHP kernel: ata22: DUMMY Mar 27 18:13:36 MedHP kernel: ata23: DUMMY Mar 27 18:13:36 MedHP kernel: ata24: DUMMY Mar 27 18:13:36 MedHP kernel: ata25: DUMMY Mar 27 18:13:36 MedHP kernel: ata26: DUMMY Mar 27 18:13:36 MedHP kernel: ata27: DUMMY Mar 27 18:13:36 MedHP kernel: ata28: DUMMY Mar 27 18:13:36 MedHP kernel: ata29: DUMMY Mar 27 18:13:36 MedHP kernel: ata30: DUMMY Mar 27 18:13:36 MedHP kernel: ata31: DUMMY Mar 27 18:13:36 MedHP kernel: ata32: DUMMY
But your controller is using 4 of those dummy ports, ATA29, 30, 31 and 32.
So technically I think this is more a controller firmware issue, it should only indicate actual 6 ports, not 30, still the kernel should be able to use them, either by using a quirk or reverting this recent change, since I suspect a lot of users will be affected.
-
That should be reported in the UD plugin support thread.
-
Do you still get the crash without running hdsentinel?
-
Changed Status to Closed
Changed Priority to Other
-
11 hours ago, Justin F. said:
Also seeing possibly a related issue.
On 3/24/2024 at 5:54 PM, JorgeB said:There are macvlan call traces, change the docker network to ipvlan.
-
If it works in safe mode it suggests a plugin issue, you can uninstall or disabled the plugins, and then install/re-enable one by one.
-
If you really need macvlan you can still use if you disable bridging for eth0, see the 6.12.4 release notes.
-
There are macvlan call traces, change the docker network to ipvlan.
-
One thing you can try is to boot the server in safe mode with all docker containers/VMs disabled, let it run as a basic NAS for a few days, if it doesn't crash start turning on the other services one by one.
-
Try using a different browser, also make sure no ad-blockers are installed.
-
Do you have the zfs master plugin installed?
- 1
-
1 hour ago, Maik75 said:
Displaying "Healthy" for the drive in questions however seems like a serious UI bug, wouldn´t you agree?
I do, the only clue you get for now when a pool device drops, is that is stops showing the temp.
-
7 minutes ago, Maik75 said:
however what about the "SMART Healthy" information?
Since the device dropped offline there's no SMART, you need to reconnect the device to get that again.
-
15 minutes ago, Maik75 said:
Several ten thousands BTRFS errors..
Same issue, one of your devices dropped offline, Unraid does not currently monitor pool devices, it's an old feature request of mine, for now you see here for better pool monitoring.
-
Possibly a problem with one of the existing zfs filesystems, but since you have multiple, it may not be easy to find out which, I would probably start with the pool.
-
Quote
It turns out that only on 1 of the SSDs, the TXT file contains the SMART test report, on the other SSD the TXT file only contains
That, and all the other errors above, suggest the device dropped offline, please post the diagnostics.
-
11 hours ago, BillVR said:
since the workaround would not work for me
That is strange, any chance you saved the diagnostics?
-
It should be.
-
There's nothing logged in the syslog after 1:30AM, and the server rebooting on its own doesn't sound like an Unraid problem, but try downgrading back to v6.11 and retest.
[6.12.9] Can't start, update or remove containers - ZFS issue?
in Stable Releases
Posted
Did you try an image instead of a folder? If yes is it the same?