Jump to content
XPEnology Community

Leaderboard

Popular Content

Showing content with the highest reputation on 06/18/2021 in all areas

  1. If you want to modify your grub.cfg of your written boot stick or want to access the partitions (adding extra.lzma from @IG-88) you can use a free portable tool. Notes: - the grub.cfg is located in the folder "grub" on the first partition (15MB) - the extra.lzma is on the second partition (30MB) 1.) Download MiniTool Partition Wizard Free Edition (portable): https://www.partitionwizard.com/download/v12-portable/pw12-free-64bit.zip 2.) Unzip it and launch the "partitionwizard.exe" with administrative rights. 3.) Plug in your boot stick. Partition Wizard will automatically recognize the new drive. In this example it is drive no. 4. Now select the 1st partition of your stick (15MB) -> rightclick and select "Change Letter" in the context menu. 4.) Select a desired drive letter and click on "OK". 5.) In the lower left pane of the tool click on "Apply" and confirm the pending changes: If everything went OK you should see a success message: Now you have full access to the 1st partition with the Explorer or your favourite file manager. If you're done with any modifications it's advisable to unmount the drive letter. The steps are nearly the same. 6.) Right click the 1st partition again -> "Change Letter" -> select "New Drive Letter: none" -> "OK" -> click on "Apply" to the lower left and confirm the changes.
    1 point
  2. I ended up going with a virtual install on ESXi 6.7, using passthough mode for my LSI SAS controller. It's pretty quick and the install was more-or-less painless. What's kinda ironic is I had to insert network drivers into my esxi image anyway, however VMware had them available and it was an easy process. Thanks for the info!!
    1 point
  3. It seems to be a problem when sedding admin_center.js. Try again with the new version (v2.3.2-r01)
    1 point
  4. It seems to be a problem when getting AMD information. Try again with the new version (v2.3.2-r01)
    1 point
  5. Afaik the onboard networking device at A2SDi boards isn't supported at such old Linux Kernels. (Tested with old Debian releases.) Possible workaround: Install a hypervisor (i.e. Proxmox) and use XPE as guest system in a VM. No issues so far at 8C+ hardware. But it's only a small test VM...
    1 point
  6. Согласен полностью. Но увы, нет у простого пользователя инструментов по перемещению в FAQ, есть только у Админов. А у них своё понимание что есть FAQ, а что нет. Вроде бы злободневная тема, вроде бы её и надо выделить, но.... Так они, темы эти и будут по форуму гулять
    1 point
  7. Many Thanks, i tried with 3617 and i can confirm that now i have 4 core : root@NAS:~# cat /proc/cpuinfo | grep 'processor\|name\|cores' processor : 0 model name : Intel(R) Xeon(R) E-2224 CPU @ 3.40GHz cpu cores : 4 processor : 1 model name : Intel(R) Xeon(R) E-2224 CPU @ 3.40GHz cpu cores : 4 processor : 2 model name : Intel(R) Xeon(R) E-2224 CPU @ 3.40GHz cpu cores : 4 processor : 3 model name : Intel(R) Xeon(R) E-2224 CPU @ 3.40GHz cpu cores : 4 So it means that 918+ on gen10+ only used 1 core ? or this is only cosmetic ?
    1 point
×
×
  • Create New...