eebrains

I thought I'd post here instead of a new topic - Just wondering why cryptsetup is included with unRaid but doesn't work? I would like to set up encryption on some drives outside of the array, but the kernel doesn't support the encryption. I'm led to believe this is a simple thing to roll into the kernel, as others here have done said... why can't we get that by default when nearly every free distro supports it? Thanks. J

Well, turns out I had stuck bits in my DDR4. fun stuff.

I have the same problem, it appears. I was hoping to avoid a reboot, but it seems inevitable.

Got it working - thanks! The latest preview version I wanted to run wasn't pulling. I found a previous preview build that has the same features, and that pulls just fine. Cheers! J

This is covered in the readme linked in the first post of this thread. My apologies - it is possible I'm a complete moron. I explored the links on the first post, but I still don't see it...

I mount a ram disk (tmpfs) in my /boot/config/go file and point plex to the mount. Seems to work well for me. Is is possible to run the transcoding preview release on this docker? (v#.#.#.####) Just download the .deb and update the image manually?

After kernel panic, the system is frozen. I have to reboot... so where would I find a log when that happens?

Anyone ever see kernel panic when trying to dd if=/dev/zero of=/dev/sdX Simply running a zero (using dd) on any of the 4 disks connected to my motherboard SATA ports is causing kernel panic after 20 mins or so. I had initially tried to zero 4 disks at once. Then I tried two. Nope. Then I tried the other two. Every time it seems to crash after 10-20 mins. So I tried running the pre-clear disks tool from CA today: same story (I assume) - as I am remote and my server no longer responds. I was previously running unRAID for about a week without issues. I hadn't done much with it - still in trial mode, deciding what OS to use long term. Perhaps a clue is that my previously parity HDD reports 1400 relocated sectors in SMART. The other 3 disks report 0. I fear it is related to hardware since it is a newly built system, and is not completely vetted - Gigabyte Mobo Z170X chipset, i5-7500 (supported after BIOS reflash). The case uses a 8-bay hotswap SATA backplane (2x Dual sata ASM1061 cards, 4 useable SATA on mobo) Dual 256G m.2. cache drives (consume 2 SATA channels). The 4 disks are 4TB Seagate Ironwolf NAS drives. Perhaps I will try to boot another OS locally and see if the same thing happens. I could also try moving the disks to the other 4 bays in case it is a SATA controller issue on the mobo.

One reason I was set up to ssh remotely to the main system was to get plex running. I use plex-pass verison, and I am not yet familiar with docker (but will be someday soon). Anyhow the simplicity of Slackware packages makes it so easy to install plex natively... I was up an running in minutes. Now... I think I learned why not to do that... Another mistake - I had set up my array drives formatted as btrfs (thnking ahead to integrated snapshots). One of my shares was completely hanging on disk access due to some bad metadata checksums (presumably from plex running without the array online). So I nuked my array last night (I'm backed up), and started over. Today just for kicks I reformatted the USB to ext2, labeled it UNRAID. Copied everything I needed to it, and ran the install script. Rebooted... yep it doesn't work! I figure it failed because the default mount configuration assumes "-t vfat"... so no dice. I was doing it all remotely so I'll have to check it when I get home. Looks like I'll have to learn more about docker... but I definitely want to be able to do tweaks on my system from the shell. Thanks guys.

Yes, yes, yes. I get that its easy to get hung up on that... So I configured a non-root user with ssh key access so I can remote in without accessing root directly. Anyhow, nobody has addressed the actual question about changing default mounting permissions of /boot...

Lets say I have created a user eebrains on my unraid box. I can set up ssh keys to eebrains. This user cannot perform actions as root without the root password. Sorry if "privaleged" means something else, I'm not up to speed with lingo yet. If the user eebrains is logged in, they cannot write to anything they do not own, or have group/public permissions. I want to know if it is possible to change the permissions of /boot/ to be root owned, unwritable by others (ie 755). This would have to occur at the time of booting obviously.

Open to read/write access by what or who? You can control access to the boot device with regard to other computers on the network, for example. You can control what you allow dockers and VMs to have access to. Within the unRAID OS itself, everything is running as root. Example: I forward SSH over port X from my router to port Y on my unraid box. If my unprivileged user account is compromised via ssh (after all, passwords are sent in the clear), then said account would instantly have free will on my /boot/ directory. For that matter, everything in /mnt/ is also 777. Before I get the obvious "don't forward ssh to your router", I do understand the risk - so I have disable password auth and use only publickey auth. Perhaps there is a way to set up the initial mounting options somewhere to restrict ownership of /boot and /mnt... If the system is operating as root, then it wouldn't cause ownership issues, right? I know that FAT32 can't control ownership of individual files, but you can mount the device with specific ownership applied recursively to the mount point. Would there be a (safe) way to do this?

I just installed 2x of these SATA controller cards... IO Crest 2 Port SATA III PCI-Express x1 Card (SY-PEX40039) https://www.amazon.com/gp/product/B005B0A6ZS/ref=od_aui_detailpages00?ie=UTF8&psc=1 Each card has 2 SATA 3.0 ports. They use the ASM1061 chipset. Plug & Play with unraid 6.2 - work like a champ!

I'm new to unraid. I've had my rig going with 6.2 for about 5 days now. I am learning a lot about slackware and unraid - and I like it. Question: Can I install unraid to a boot USB that is formatted in ext2? or ext4? I don't like that the unraid boot disk (aka /boot/ ) mounts as vfat (ie. 100% open to read/write access), for obvious security reasons. Anyone successfully migrate the boot disk to another format? Thanks