25.04-BETA.1 or 24.10.2 TrueNAS Scale for Homelab?

TrueNAS General
, ,
1

25.04-BETA.1 or 24.10.2 TrueNAS Scale for Homelab?

The BETA uses " Incus" is the newer virtualization hypervisor. I want to virtualize only NextCloud, possibly also a CoTURN server and a High Performance Back End server, both for the NextCloud Talk App. I think that the BETA might be better? Because I don’t want to make a kvm machine for NextCloud that can’t be supported in the next version or migrated or whatever? KVM VMs might not be compatible with Indictus…

EDID errors? Really?
I’ve installed TrueNAS Scale, on a new NAS build. I saw the infamous, “EDID block 0 is all zeroes” error messages and I decided not to debug / work around / fix that if I could avoid that…

So, I thought that the BETA release, 25.04-BETA.1 might have a bug fix for that. I tried the BETA, but it doesn’t have any bug fix. Apparently this is caused by i915 kernel modul for intel iGPUs? it might be a kernel vs os problem?

So, what should I do??? I’m leaning toward the BETA, so that I don’t get stuck with no upgrade path after KVM support ends. The BETA also seems less bothered by the EDID errors, although the problem is still there.

I also can’t get the SMB shares to work, as usual. 'Goodness. Do I really have to use the cli to solve the EDID / iGPU problems? I hate changing stuff that I won’t remember to unchange later, after a bug fix is part of an upgrade. Dear me. And the darn shares don’t work for me in either version. I’m not exactly a newbe, but I feel like one today…

Any thoughts? or advice? I’ll have a fresh start in the morning. Now is the time to try and to test trials. I’m not using the storage yet, so I can delete and remake primary pools without loss.

Thanks in advance. I’ll republish my system hardware/firmware spec.s when I can find them…

2

More on this might be useful.

1 Like
3

Thanks for the reply. I got the shares to work. I’m using fangtooth? The Beta…
The directory structure gui folders/paths/directories need work, they seem to duplicate the icon folders…so I had some weird pathways/directory structures and the shares were broken.

No matter. Now I’ve got to figure out how to change permissions on replicated data. Everything is read only after replication. Yikes!

Error removing file: Read-only file system

!

4

This is expected. replicated data should always be readonly. Making it rw will break your replication.

1 Like
5

Thanks again!

How / where do I change the permissions to read/write/execute, to make the data useful?
I appologize for my extreme ignorance in this matter! Ha!

Thanks again!

6

If you made a one-off replication task to transfer the data, you then edit dataset options and untick “read-only”.

1 Like
7

Thanks! I know what I did, can I undo that? The data is read-only.

I did use one-off replication tasks. They were set to Read-Only.
I’ve changed those replication tasks to IGNOR Read-only.

Should I run the replication tasks again?

How do I change the data to become read/write/modify/execute and etc. So that the shares can be modified by share users?

Thanks again!

Rick

8

If this was a one-off task (think migration), you can make them read-write. Then you’ll also have to probably redo permissions before making shares.

9

Thanks!

How? How do I make them Read/Write?

I can’t access the permissions editor via the share, because it is greyed-out/inoperable.

Do I have to un-mount the datasets to edit their permissions?

Eureka! Ah! 'Maybe I found it. Their is a toggle switch for read only in the share properties in the data set details under advanced options.

Let’s see if that’s it.

Thanks!