phone guy

Members
  • Content Count

    273
  • Joined

  • Last visited

  • Days Won

    2

phone guy last won the day on May 16

phone guy had the most liked content!

Community Reputation

53 Excellent

About phone guy

  • Rank
    Super Member

Recent Profile Visitors

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

  1. Anyone with experience have any suggestions for a Mini ITX board and chip combo that is going to live its life as an 8 bay hotswappable xpenology box? I would like the option to add a graphics card in case it becomes a DVA3221, but thats not a deal breaker. Most of what I am finding is < = 3rd gen Intel, so that eliminates 918/920/3221 and QSv HW transcoding. Not sure I want to do that. Also most of these boards have 2-4 sata, some have m.2 slots... so I have seen these m.2 pcie to sata boards Even some little 2 port ones.... But I have no experience with these, and I have
  2. P20. google your hba and P20 IT MODE, there are literally hundreds of guides... many will have img/iso with all required files. I just went down that rabbit hole myself. Which card exactly do you have? Here is a starting point for you, but trust me google will have all the directions you'll need.
  3. No problem here. Running DS3622xs+ build DSM 7.1 42661 in VM with LSI 9211 8i pci pass thru with 5x 4tb ironwolf no issues here root@DS3622:~# fdisk -l |grep Disk |grep sd Disk /dev/sda: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors Disk /dev/sdb: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors Disk /dev/sdc: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors Disk /dev/sdd: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors Disk /dev/sde: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors root@DS3622:~#
  4. I was going to reply to another thread with this question, but I felt it needed its own post to generate some discussion, as I am very interested to see the responses and opinions of the other people building these types of devices, so Please post any responses and opinions I really want to get opinions on this and maybe learn something in the process. How important is cpu computing power and ram overall in a DSM build, whichever platform. I have to guess if storage is the end goal, not much? in other words, if your DSM/NAS/TrueNAS/UnRAID/OMV/etc is basically a hard drive on the e
  5. wow! I would have sworn I build a DS918 on this board before, obviously I was wrong! Must have been the i7 4790 box I have? oh well...So it must be 4th gen or newer right? (to be compatible with 918/920/3221) Man, I just bought all that server hardware to build that proxmox server <- disappointed.
  6. Still failed. I removed the scsi emu hdd, added 2 sata emu hdd as sata 1 and 2, q35 system, kvm64 host type, tried 42218 since I am able to see serial console, these are the results.
  7. - Outcome of the update: SUCCESSFUL - DSM version prior update: NONE - fresh install - Loader version and model: redpill.v0.4.6.img DS3622xs+ DSM 7.1.0-42661u1 - Using custom extra.lzma: NO (added ext drivers manually) - Installation type: VM Proxmox v7.2: cpu: E3-1270v2 mobo: SuperMicro X9-SCM-F - Additional comments: Successful as Q35 and i440fx system. PCIe/PCI Pass Thru LSI HBA controller (Dell H710 flashed IT MODE ver P20) using ext MPT3SAS. Paravirtual nic using ext V9FS. ACPI working using ext https://raw.githubusercontent.com/dodo-dk/rp-ext/main/acpid/rpext-ind
  8. I tried so many things yesterday... q35, i440fx, changing cpu type from default kvm64 all the way to host (e3-1270v2), 2 cores, 4 cores, 2gb ram, 8gb ram, nothing worked. emu hdd was set to scsi and 50gb, I will try later on with virtual sata and those port mappings and report back later.
  9. @pocopico there seems to be an issue with the v9fs drivers and ds918 (42218 and 42661). it gives a recipe error when adding that ext and building the loader. someone has that issue in the proxmox thread. just letting you know.
  10. @pocopico I was able to duplicate this error, something is wrong when adding v9fs for apollolake 42218 and 42661, gives a recipe error. @luutuananh until @pocopico fixes the issue with the v9fs drivers, use the virtio drivers and you will have success.. I just tested them myself and both 42218 and 42661 build successfully. To build DS918+ DSM 7.0.1-42218 ./rploader.sh clean now ./rploader.sh update now ./rploader.sh fullupgrade now ./rploader.sh serialgen DS918+ ./rploader.sh identifyusb now ./rploader.sh satamap now ./rploader.sh ext apollolake-7.0.1-42218 add https://raw.github
  11. Yes, with 42661 the console no longer displays booting process as shown here Loading Linux... Loading initramfs... Starting kernel with USB boot So I have no way to know how far the booting process got before it died...but again, because of how instantly proxmox is quitting that vm instances, I know its locked in kernel panic. ?????? Anything else I can try? Seems to work with ESXi ???
  12. From the research, the only difference is a slight performance hit of about 25%. I am not saying thats not important, but could you elaborate as to why stick with q35?
  13. It downloaded the 42118 pat, but this is as far as the booting goes, having the serial console opened while booted in tiny core, then clicking reset to boot the loader... This is a loader with only these commands ./rploader.sh ext denverton-7.0.1-42218 add https://raw.githubusercontent.com/pocopico/rp-ext/master/v9fs/rpext-index.json ./rploader.sh build denverton-7.0.1-42218 Resulting in this from the console... obviously its hung here. Tried again with system set as q35 same results. Any suggestions?
  14. I have tried all nic adapters available in proxmox. virtio, e1000, r8139, vmware ... no connection. I have added ext for each except the r8139 as I did not find a link to it on @pocopicogit hub, but the builder auto added it https://github.com/pocopico/rp-ext/tree/main/8139cp Still no connection, and based on how quickly proxmox shutsdown the vm, I am assuming it crashed (kernel panic?) somewhere because it closes the vm almost instantly, where other vms take several seconds to close. I tried to build 7.0.1 42218 and got this error #############################