pocopico

Members
  • Content Count

    31
  • Joined

  • Last visited

  • Days Won

    1

pocopico last won the day on July 1 2020

pocopico had the most liked content!

Community Reputation

8 Neutral

1 Follower

About pocopico

  • Rank
    Junior Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Well first of all you shouldn't be seeing disk as virtual SATA drives, but rather something like the below list, where i have set the disks to RDM. Anyway i'm using the onboard HBA and so i had to use the SATA creation of RDMs using the CLI. Like i said this was never working in my Gen 8 microserver with ESXi. Maybe SMART data for SATA RDM disks is not working as it is on a SAS HBA with SAS disks that i have and i'm getting SMART data on my VM. This might help you a bit more :
  2. if you attach the RDM disks attached on a supported HBA then the smart data will be visible. If you attach unsupported disks (SATA attached on mainboard controller) using command line RDM files then you wont have SMART data.
  3. Smart data is visible via esxi RDM ... it think its safer to use RDM than use passthrough as HBA will be supported on esxi but that might not be the case for xpenololy. Also in case you want to attach it to a linux VM, or even windows with windows btrfs driver for data recovery it will still be easier
  4. If i understand correctly, you could just cut a spare micro USB wire on the micro usb end and keep the USB end. Check wires with a multimeter and find the pinout and connect the right wires to the board. It should not be that hard.
  5. Although i understand the concept for the shake of experimentation, i trully think its a waste since all the great tech behind Nimble arrays is wasted with DSM. Maybe a VM accessing the Nimble arrays would be a better approach ? Anyway i would also be interested on getting my hands on one of these how much do they sell ?
  6. IMHO, you dont need them as you will do not need to create the kernel itself but additional modules only. i remember i've tried QuTS before but i've got the no license ... i have to figure out why this is happening. It can be the CPU core count or something else.
  7. QuTS or QTS ? The standard kernel source will do fine for the module creation. If i remember correctly you download the git source and you check out on the kernel version of your kernel. Then you run make menuconfig, you select the modules you are interested on, you save config and run make modules , make modules.dep etc. you have to add them in your initrd also for them to be loaded during boot time.
  8. What about the license ? On a VM where i installed QuTS i get a no license error
  9. Hi all, I've been checking this thread from time to time, but i've been busy with other stuff recently and missed a few. I'm glad that some of you are making progress. Please note that from what i can remember QutsHero (Versions 4.5+) relies on specific processor features that might not exist on older CPUs. So if you get a fail to get an IP that might be the case. Try with older versions or other firmwares. I still have the kernel tree and can create additional modules. If you need them just drop a message and i'll try to compile them for you. I will have to
  10. The same process as above works for 4.5.0 version of QuTS if anyone is interested in checking the ZFS version. MODEL_TYPE="QZ601_Q0040_12_11 " PATCHED_FIRMWARE="TS-X83XU_20200520-h4.5.0.1308" DOWNLOAD_URL="https://download.qnap.com/Storage/QuTShero/TS-X83XU/" Models found in the firmware : Q00V1_Q00W0_11_11 = TS-2483XU QZ601_Q0040_12_11 = TS-1683XU QZ601_Q00M0_11_10 = TS-1283XU QZ601_Q00M1_11_10 = TS-883XU QZ602_Q00M0_12_10 = TS-1283XU TBJBOD_QW580_QW750_20_20 = TX-800P TBJBOD_QW580_QX180_20_20 = TX-500P Have fun
  11. Hi all, in an effort to simplify the process, I've done some work towards that, but i think there is a lot of room for improovement. So far what i've done : - Translated about 100% all disk, kept original and translated original on a separate folder - Cleaned up the firmware process and kept as much many as i could from initial scripts - Added an automated process to figure out as many devices as i could during model.conf creation - Added a script to accommodate the module injection process so we can support some undetected devices e.g. vmxnet3, e1000 etc - Adde
  12. Actually I think it’s important for the combination of DEV_BUS and DEV_PORT to not report conflicting info about the SLOT. I might have some conflict in the model.conf as I was really dizzy trying for two days to figure this out. If you dont mind, could you please share the python script ?
  13. I’ve also noticed that if you don’t have the correct [System Network X] defined then it will fail to get an IP. You should match the PCI bus id for all your network devices. See my answer above for modifying your initrd (ramdisk). The PCI bridge will be used only for additional devices you connect I guess, which actually makes no sense for a VM.