unRAID NAS Server Pro 6.12.8 Crack

6,584 views次阅读
没有评论

unRAID NAS Server Pro 6.12.8 Crack

特别鸣谢

PRYANIK@softoroom

下载地址:(解压密码:hopol)

unRAID_Server_Pro_6.12.8.7z

https://mega.nz/file/hR5nGZyD#B3ItB4xPg8y5inywb4KvcACwRZOM7mm7jemIldhcXe4

 

临时下载链接:

https://pan.hopolcn.com/s/NOh2

 

学习方法

If you have just updated:

Take unraider from the unraider-for-update and replace it on your flash drive in the /config folder.
Use it.

If you have just decided to start using:

Put the unraider and hook.co files in /config.
Replace the go file in the folder in /config with the following.

#!/bin/bash
export UNRAID_GUID=(!)HERE IS YOUR GUID
export UNRAID_NAME=Tower
export UNRAID_DATE=1654646400
export UNRAID_VERSION=Pro
/lib64/ld-linux-x86-64.so.2 /boot/config/unraider
# Start the Management Utility
/usr/local/sbin/emhttp & 

Save
Use.

 

更新日志:

Version 6.12.6 2023-12-01
Upgrade notes
This release includes bug fixes and an important patch release of OpenZFS. All users are encouraged to upgrade.

Known issues
Out of date plugins
Out of date plugins can cause problems, we recommend they be kept current.

Call traces and crashes related to macvlan
If you are getting call traces related to macvlan (or any unexplained crashes, really), as a first step we'd recommend navigating to Settings > Docker, switching to advanced view, and changing the Docker custom network type from macvlan to ipvlan. This is the default configuration that Unraid has shipped with since version 6.11.5 and should work for most systems.

Note that some users have reported issues with port forwarding from certain routers (Fritzbox) and reduced functionality with advanced network management tools (Ubiquity) when in ipvlan mode. If this affects you, see the alterate solution available since Unraid 6.12.4.

Network problems due to jumbo frames
If you are having network issues of any kind, confirm that you haven't enabled jumbo frames. Navigate to Settings > Network Settings > eth0 and confirm the Desired MTU is 1500. For more information see the Fix Common Problems warning for jumbo frames.

Problems due to Realtek network cards
Stock Realtek drivers in the latest Linux kernels are causing network and stability issues. If you are having issues and Tools > System Devices shows that you have a Realtek ethernet controller, grab the part number shown and search Community Apps to see if there is a Realtek driver plugin for that device. For more information, see the support page for Realtek driver plugins.

Adaptec 7 Series HBA not compatible
If you have an Adaptec 7 Series HBA that uses the aacraid driver, we'd recommend staying on 6.12.4 for now as there is a regression in the driver in the latest kernels. For more information see this bug report in the Linux kernel

Other issues?
We highly recommend installing the Fix Common Problems plugin as it will warn you of common configuration problems.

Having other crashes or stability issues? Navigate to Settings > Syslog Server and enable Mirror syslog to flash. This will cause additional wear and tear on the flash drive but is useful in the short term for gathering logs after a crash. After the next reboot, navigate to Tools > Diagnostics and download your anonymized diagnostics (as of 6.12.5, diagnostics automatically include logs that were mirrored to the flash drive). Then start a new topic under General Support and provide all the details of the issue. Once the issue is resolved, be sure to disable Mirror syslog to flash.

Rolling back
If rolling back earlier than 6.12.4, also see the 6.12.4 release notes.

Changes vs. 6.12.5
Bug fixes and improvements
modprobe.d/zfs.conf: remove zfs_dmu_offset_next_sync=0 mitigation - no longer needed

network: Fix IPv6 static address assignment

The workaround for crashes related to the i915 driver on Rocket Lake systems is no longer needed. After upgrading, feel free to open a webterminal and type this, then reboot:

rm /boot/config/modprobe.d/i915.conf

Package updates
nvme-cli: version 2.6
zfs: version 2.1.14
Linux kernel
version 6.1.64

 

正文完
 0
HopoL
版权声明:本站原创文章,由 HopoL 于2024-03-20发表,共计3325字。
转载说明:除特殊说明外本站文章皆由CC-4.0协议发布,转载请注明出处。
评论(没有评论)

HopoL's Blog

文章搜索
最新评论
Metaldololity Metaldololity Whoa, that's really simple. You just save my time a lot. Thankyou!
HopoL HopoL Since you’ve got the backup, it’s actually pretty simple. Just restore the backup files to your new flash drive, then head over to the /config directory and edit the go file. Look for export UNRAID_GUID=xxxxxxxxxxxxxx and swap it with your new drive's GUID. That should do the trick!
Metaldololity Metaldololity Really apreciate for your fast respond, mate. I actually have the backup of the flashdrive (from regular unraid backup). The problem is, when i search on youtube tutorial about changing the failed flashdrive, the process need some sort of confirmation with an account in unraid (blacklist the old one -> whitelist the new one). Since i have a cracked unraid, i don't know how to register my new flashdrive as the correct one (and the system not asking me for the old failed flashdrive). Thanks in advance
HopoL HopoL Man, that's a tough spot to be in. Regularly backing up your /boot folder is super important for exactly this reason. If you don't have a backup and your flash drive is completely fried, your best bet is to Google some specific recovery guides or check the Unraid forums. There are ways to rebuild your config by identifying your parity and data drives, but it can be a bit of a process. Hope you can get it sorted!
Metaldololity Metaldololity Hi! Huge thanks for the update on 7.2.0. I have question here, my flashdrive corrupted. how do i install it on the new flashdrive without losing all my configuration?