Leaderboard

Thanks for helping! The error is from the menu: I suspect this may be related to your latest commit @Peter Suh? https://github.com/PeterSuh-Q3/tinycore-redpill/commit/708116888de6d9bb08b5b2fc1850c22fbba2011a I can see the file was changed so the md5 must have too. I am just not sure what is used to compare the md5s. Edit: nevermind, the issus is with the gz file which didn't change in 2 years...

Hi there. I´m trying to build a new test system on Virtualbox. I had tryied all models at m-shell, but I always get error on modules.alias.3.json.tgz checksun. Cloud you please verify if there is any mismatch? Best regards.

Нет. В Линуксе не силен. И при этом наверняка при подключении к нему Виндового компа - попросит дрова. А их нет. От слова совсем. Есть только 32 разрядные под WinXP. Я ставлю Хрюшу. Под него родные дрова. Чтоб впустую не печатать - вот оригинал: https://dzen.ru/a/YDKhWHVu6zHwlpph Работает.

Hi guys, Do you know if this Syno Community are reliable? https://github.com/syno-community/rr They seem to be posting the most recent RR builds.

Hi @Peter Suh I've been trying your build for the first time, using ESXI, with the latest version (v1.0.1.0.m-shell) and when building ds3622xsp_64570 (or later) I get: I couldn't find someone else with the same issue... any idea?

So far, so good! I can report that SA6400 with your current Loader w/Friend, it was effortless and largely flawless on the test XPS 8950. The only thing I could report at this time, was the screen resolution when booting into Friend, was lower than optimal, so I needed to resize and arrange the 4 windows a bit, but that's trivial. It recognized all 4 SSD installed, as well at the 2 x 256GB NVMe SSD installed for possible R/W cache options testing. Created a RAID F1 smoothly. Singular network connection, recognized as predicted and performing well thus far.

1st post here. Tags or Magick words related to this issue: Failed to install DSM, Error trying to load PAT at 55%, Prior things done/check Install TinyCore Boot USB to TinyCore Build with DS3622xs+ USB Kingston (good compatibility) Supermicro Board (good compatibility) Boot correctly into DSM Loader Problem: After loading PAT file (proper version) you get the message "Failed to install the file. The file is probably corrupted" Analyzis: After finding the serial console provided by TinyCore on http://<yourip>:7681 (user/pass root/<blank>). If you check with cat/vi the log file linuxrescue.... cat /var/log/*rc* You will see some error messages like this ... Still waiting for boot device (waited 28 of 30 seconds) Still waiting for boot device (waited 29 of 30 seconds) Still waiting for boot device (waited 30 of 30 seconds) ERROR: Timeout waiting for /dev/synoboot device to appear. Most likely your vid/pid configuration is not correct, or you don't have drivers needed for your USB/SATA controller ... If this is the case.... maybe (but maybe) DSM Loader cant find the USB drive, despite from the fact that you correctly set the PID VID on the config. *You can check also running df -h or any other commando showing that the USB stick wasnt mounted/detected Cause: This could be caused by many things, but the one I found in this case is that the USB is connected in another port not used by DSM. I will be as simple as posible... DSM 7.1 on 3622xs+ looks at firsts BUS/PCI combination for the USB VID/PID provided, so bad luck on my trying to boot. My hardware has the USB port on BUS/Device: 2-3 (Reference photo) Solution: Here comes the good part.. How can we specify a new BUS/Device location on 3622? no idea.... xD But i've found that models DS920+ and DS1621+ have some .dts files on the redpill github. And they show at the very bottom the following curious info usb_slot@1 { vbus {syno_gpio = <0x2a 0x1>;}; usb2 {usb_port = "1-2";}; usb3 {usb_port = "2-2";}; }; usb_slot@2 { vbus {syno_gpio = <0xb 0x1>;}; usb2 {usb_port = "3-1";}; usb3 {usb_port = "4-1";}; }; usb_slot@3 { vbus {syno_gpio = <0xc 0x1>;}; usb2 {usb_port = "1-3";}; usb3 {usb_port = "2-3";}; }; }; I guess you've realized were we are going. the rploader.sh script updates ONLY the line for usb_slot@1 on this file with the proper PID/VID of your USB stick. So what I did was, after runing identifyusb, I've changed manually the usb_port for usb2 on usb_slot@1 with the proper BUS/Device info obtain from the lsusb command on tinycore (where my usb were connected) Bonus: You can use 1Gb USB Stick with no problem Bonus2: I guess this applies to all DSMs and Loaders Hope this helps, took me 1 day to figure out.

I fixed this by editing my grb.cfg and adding disable_mtrr_trim