Jump to content
XPEnology Community

phone guy

Members
  • Posts

    308
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by phone guy

  1. I think its build manual ./rploader.sh <platform> build manual
  2. Sending a PM with a question, not to highjack the thread. Edit, ok maybe not, will not let me add text to the message? LOL. I tried repeatedly to pass through graphics of an i7-3770 in proxmox, and never got passed the error 43 or error 10? I cant remember which now, in Windows 10. The windows 10 vm saw the internal graphics, but would blue screen anytime trying to install drivers. If you can PM me, I would love to figure out what I did wrong? I couldn't actually type anything in a PM to you. Sorry for the off topic post.
  3. Satamap and diskidxmap do not influence the sas/hba ports. They simply appear after any ahci (sata) ports on the system, which are influenced and affected by satamap/diskidxmap. I didn't go back to see your original post, so sorry for that, but @flyride worked with me for about an hour recently, and explained this to me in detail... so this information is super reliable HERE is an article that explains those commands in more detail than I could provide, however FYI, there has been some updating recently to the way TCRP maps sata ports with that command.
  4. I do the same thing. Seems like anytime I tried to restoresession, the user_config.json doesn't restore, and I agree must be user (me) error. I also just re-added the needed exts again. I just keep backup of needed ext/commands in a text file and copy paste.
  5. Question for @pocopico@flyride or anyone else who can answer this. Once a loader is up and working, and a hw change is made, when you go back to TC to add the ext for new hardware, or change mac/serial, or whatever... when you recompile the loader (./rploader.sh build xxx) do you have to add the ext's you had working before this session, or does the tcrp usb have them cached and reuse those? LONGER: I had a working system, added the nic ext, the acpid ext.. everything worked. Then I added a HBA card. So I knew I need the mpt3sas ext, so I booted back to TC, if I would have only added the mpt3sas ext (or let the build process do it automatically) without again adding the 2 previous ext (nic and acpid) would they have been added from cache? So does tcrp remember the ext you added before? I never did a clean, but I did do update and fullupgrade before adding the mpt3sas and build.
  6. I thought you needed 4th gen Intel for 920 build? How did this work on 2nd gen Intel?
  7. Are you guys adding "netif_num=2" or however many nics you have, entry properly to the user_config.json before building command? The only other piece of advice is verify the nic in question (not showing up) is not listed as being on the USB bus with lspci (it might be lspci -nnq) I have a Nas box with 2 internal nic, 1 worked 1 didnt. Turned out 1 was attached to USB bus not the pci bus. Then after getting the driver to work the issue was dsm won't see hardly anything on a USB bus anymore since dsm7 and I had to use a patched driver for that onboard nic because they (manufacture) ran it through the USB bus .. Good luck[][
  8. I wanted to clear up a few things here for everyone new and experienced. @pocopico has updated the tcrp image from 0460 to 0800 -> 0802 after updates and upgrades. so around the 7th step screen above in the guide where it shows you how to get your tcrp loader, the links have changed due to version changes. Download tinycore-redpill.v0.8.0.0.img.gz from @pocopico Github HERE and you can manually enter the proper directory and upload the extracted img file to proxmox that way, nothing else changes. To use The CLI to automatically create the required dirs and download and extract the correct and newest tcrp image would now need to be (and by the way you can test or use either of the 3 listed builders if you see a reason or advantage, that is all up to you.) # set vm id to whatever it was at time of creation id=101 # create image directory, download and uncomporess mkdir -p /var/lib/vz/images/${id} curl --location https://github.com/pocopico/tinycore-redpill/raw/main/tinycore-redpill.v0.8.0.0.img.gz --output /var/lib/vz/images/${id}/tinycore-redpill.v0.8.0.0.img.gz gzip --decompress /var/lib/vz/images/${id}/tinycore-redpill.v0.8.0.0.img.gz --keep The next step of creating your virtual usb to boot your redpill xpenology from needs to be edited to, it should now read like this echo "args: -device 'nec-usb-xhci,id=usb-bus0,multifunction=on' -drive 'file=/var/lib/vz/images/101/tinycore-redpill.v0.8.0.0.img,media=disk,format=raw,if=none,id=drive-disk-bootloader' -device 'usb-storage,bus=usb-bus0.0,port=1,drive=drive-disk-bootloader,id=usb-disk-bootloader,bootindex=999,removable=on'" >> /etc/pve/qemu-server/101.conf This method makes your vm as close to a baremetal build as possible, even genuine syno boxes boot from a usb (for the most part)...This build is rock solid and has in my production environment being heavily as its become a huge backup for all my other nas's and servers. Then as I have said repeatedly for the actual building commands of ./rploader.sh so you build your redpill load, these commands are usually done via ssh putty/terminal a terrific detailed guide is available from @flyride He explains the options and process to build the loader, its straight forward and mosty automated for the vast majority of users, read his resource and you'll get it running in no time. The paravirtual ethernet ext drivers v9fs are everything the virtio drivers are (i.e. same) PLUS with the addition of v9 protocol on top, and the v9fs is the more recently compiled drivers and offers better compatibility with many of the newer current models/platforms, that comes from the main xpenology guys so use or not, up to you ;: Last, when you finish and successfully boot the loader, it will stay on the kernel booting..... That screen is success (hopefully). At this point, using another machine, open a browser and go to find.mysynology.com, or download the synology assistant on your phone or pc, and make sure you can see your network. Now, if you followed my directions above, you can scroll up a few lines in your console output and see what ip your nas got dhcp.
  9. To build DS920 or DS1621 you have to create and edit the dtc/dtb files to physically and manually map each port to a drive. They were working on a way to automate the process, but for now, as a beginner, the DS918 would be much easier to build as pretty much automated. Dont get caught up in the model numbers, unless a certain platform has a feature or compatibility issue with your hardware, in the end, they are all good choices. Check out @flyride installation guide for excellent loader instructions, and in his signature he has a link to choosing a loader based on hardware requirements IIRC.
  10. I wouldn't even know where to find the source. I started using the v9fs because you mentioned it everything in the virtio drivers + the v9 stuff. I just wanted to make sure the v9fs was and up to date as the virtio if I needed to switch, since I personally do not use the v9 protocol and only the virtio network drivers. Searching for Virtio drivers, I found the fedora redhat virtio drivers for windows vm HERE but never found anything specific for kernel 4.4.180, the closest I got was HERE and HERE Don't know if either of these are right or not.... Eitherway, thanks for the quick reply
  11. Is there any significant difference between virtio and v9fs driver ext's? It has been said v9fs is older and not updated or may be deprecated and virtio is the better option? @pocopico is that true? would you suggest using virtio or v9fs for virtualized network connections?
  12. I am looking for a better solution to Photos... I heard Piwigo is a good one? I am sure there are others... anybody using something better than photos? hopefully with better ai face detection.
  13. I think it has been mentioned here, that some S/N may be blocked by Synology, so I would assume if the serial (generated or real) is blocked or not blocked that may be contributing factor in success or failure.
  14. A synology acct is required for some of the apps to activate too, like advanced media extension, active backup for business and others. There are some work arounds to activate some apps like ABB for example, theres a thread here somewhere. Sorry chrome didnt work, thats how I got mine working.
  15. Try in Chrome. I tried to use firefox with my genuine synology nas and had issues, when you click synology account in control panel in chrome. the page loads correctly. That fixed it for me. [rant] honestly, while I do not like chrome, I prefer firefox, chrome seems to get along better with DSM. Thats been my experience, maybe my firefox is messed up? I dunno [/rant]
  16. Honestly having the satamap checkscsi acknowledge the existence of the HBA is useful, and will probably help more than hurt, as the example above illustrates. Just with the understanding by users the args in user_config.json are not influencing the HBA... Thats my opinion no one asked for
  17. Whats wrong with Active backup for business? its windows and linux only no mac yet, but its included in dsm and seems to work. Though I have never had to actually restore anything as yet.
  18. There were a couple of things posted that were miscommunications unfortunately. I do not do that 4 string command to clean and remove files and folders from the loader after its complete, I guess some do...? I leave everything in there in case I need to add a ext driver and re build the loader and I didn't think you were blaming me. I always try to help when I can! I Try to take some of load off all of your shoulders in the forums for you guys. if I know the answer or think I can help, I try to interact and help.
  19. You are limited to only the DS3622xs+ which is the most current for dsm7.1 and runs on that hardware. The other models require 4th intel (haswell) or better, so your choice is easy. Use and read flyrides tutorial. He explains everything and you will be up and running in no time. Or check my signture and you can use Proxmox too
  20. Because I use specific sn/macs on my builds, I keep track of them, and I notice that the user_config gets replaced with default during the updates. Thats why I warned him of that... I personally use update, fullupgrade then the rest of the commands, and just before building I edit the user_config.json if needed then I build the loader. I may not have known restoresession was an option? I dont know. I know it asks at some point do you want to use files found in old, and (for me) that didnt work it seems to start with the default config. It may have been user error by me - I admit that. Its a simple step to just verify the config before building. I also keep a local copy of my configs too. Just trying to help out
  21. The user config gets replaced when you clean, update or fullupgrade. So run those first and after you've got your TCRP fully updated, you can manually edit your user_config.json before doing the build command. This tutorial has everything you need to sort your issue
  22. I mention above this is not the only way to get redpill working in proxmox, its the way I get redpill working in proxmox. And because there was no easy english tutorial with pictures to follow I wrote this to help others. This method is more like a baremetal build IMHO. As for ext drivers, acpid works on some but not all platforms depending on repo source, but all ext seem to change almost regularly, the guys keeping this whole project running are working constantly to improve, mod, tweak the experience. fixing things as they are reported, updating things as needed so everyones individual results will vary slightly depending on current status of project and those ext's and individual hardware and use case, another reason VM is desirable as its results are more easily reproducible, following each step correctly. As for the tutorial @flyride created a great tutorial explaining in detail the process of building the loader.
  23. OH!? I did not even try it, as I am waiting until the .dts/dtb process for 920/1621 models improves - that was my big wish for jun mode, improved (automated) dts/dtb creation. So still no successful builds with tcrp + juns mode. Sorry to hear that, I thought it was working....
  24. Wait, to be clear, you guys are saying by building a 7.0-42218 loader using @jumkey juns old tricks loader you can simply upgrade from a 7.0 build to 7.1 build like a genuine syno-box (this I knew). But are we sure it will would take the next upgrade? I did not run Jun 104b dsm623 for long at all before joining the redpill faithful And I am assuming to use the jumkey juns old tricks buildroot method you have to be on q35 in proxmox?
×
×
  • Create New...