proc

May 18, 2022

19 hours ago, ejwarrior said:

Hello everyone,

Hope you guys are doing well,

I have a quick question.

After following all the steps when I restart my system it gets stuck on STARTING KERNEL WITH USB.

Hope someone can point in the right direction.

Did you try find.synology.com?

You may find your Synology NAS via either of the following tools:

Web Assistant: Enter find.synology.com or synologynas:5000 (synologynas.local:5000 for Mac computers) in the address bar of your web browser.
Synology Assistant: Open Synology Assistant desktop utility. If Synology Assistant is not installed yet, go to Download Center > Desktop Utilities to download and install it on your computer first.

https://kb.synology.com/en-us/DSM/tutorial/Unable_to_Locate_NAS

May 15, 2022

8 hours ago, phone guy said:

I guess the lesson here is use at least an 8gb usb drive for creating a red pill loader 👍 Glad you got it working

FYI, this is my 4G usb drive.

If I extend sda1, after building apollolake-7.1.0-42661, it uses only 35M....

Disk /dev/sda: 3.76 GiB, 4037017600 bytes, 7884800 sectors
Disk model: Flash Disk      
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xf110ee87


tc@box:~$ df -h /dev/sda1
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda1        98M   35M   64M  36% /home/tc/redpill-load/localdiskp1

If I don't extend sda1, I get this error on two different computers. (Every time I use Rufus to re-write the usb drive before my tests. )

cp: error writing 'localdiskp1/zImage': No space left on device

tc@box:~$ df /home/tc/redpill-load/localdiskp1
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda1        48M   48M     0 100% /home/tc/redpill-load/localdiskp1

Maybe the temp files in sda1 are too big? No idea... but extending sda1 solved the problem on my computers.

Thank you! 🍻

May 15, 2022

4 hours ago, phone guy said:

What size is your usb drive? did you format or clean it between attempts? looks like the usb is out of space to complete the build.

It is a 4GB usb drive. I formatted it and re-wrote the image to it.

I tested it on another computer and got the same error(cp: error writing 'localdiskp1/zImage': No space left on device).

After expanding the space of the first partition of the usb drive to 98MB, now there is no error and I can see the Synology setup GUI lol

Thanks for everyone's help!

May 14, 2022

26 minutes ago, pocopico said:

Why are you using build two times ? one should be enough.

Oh, I thought we should build 7.01 and then 7.1.0...

But after the first build, I also got the "No space left on device" error.

tc@box:~$ ./rploader.sh build apollolake-7.0.1-42218

....

Mounting /dev/sda1 to localdiskp1

/dev/sda2 localdiskp2

cp: error writing 'localdiskp1/zImage': No space left on device

Creating tinycore entry

....

May 14, 2022

I just checked a brand new USB drive(without running any updates or scripts). It only has 35M free space.

tc@box:~$ df /home/tc/redpill-load/localdiskp1
Filesystem Size Used Avail Use% Mounted on
/dev/sda1 48M 14M 35M 29% /home/tc/redpill-load/localdiskp1

May 14, 2022

5 minutes ago, Peter Suh said:

@proc

Mount the space on the loader 1st partition like this and check it again

tc@box:~$ mkdir /home/tc/redpill-load/localdiskp1
mkdir: cannot create directory '/home/tc/redpill-load/localdiskp1': File exists
tc@box:~$ sudo mount /dev/sda1 /home/tc/redpill-load/localdiskp1
tc@box:~$ df /home/tc/redpill-load/localdiskp1
Filesystem Size Used Avail Use% Mounted on
/dev/sdb1 48M 39M 9.0M 82% /home/tc/redpill-load/localdiskp1

tc@box:~$ df /home/tc/redpill-load/localdiskp1
Filesystem Size Used Avail Use% Mounted on
/dev/sda1 48M 48M 0 100% /home/tc/redpill-load/localdiskp1

May 14, 2022

5 minutes ago, Peter Suh said:

There seems to be enough space, but the result of the df-h command is a little different from mine.

4.6 Is the image recording wrong with USB?

Or is it because the USB stick is damaged and the restoration of my data.tgz file is not working well?

For your information, I've used up to 8GB sticks, but there was no problem.

tc@box:~$ df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 14G 84M 14G 1% /
tmpfs 7.8G 0 7.8G 0% /dev/shm
/dev/sdb3 899M 459M 441M 51% /mnt/sdb3
/dev/loop0 24K 24K 0 100% /tmp/tcloop/attr
/dev/loop1 40K 40K 0 100% /tmp/tcloop/acl
/dev/loop2 252K 252K 0 100% /tmp/tcloop/ncursesw
/dev/loop3 144K 144K 0 100% /tmp/tcloop/readline
/dev/loop4 484K 484K 0 100% /tmp/tcloop/bash
/dev/loop5 5.3M 5.3M 0 100% /tmp/tcloop/binutils
/dev/loop6 32K 32K 0 100% /tmp/tcloop/bzip2-dev
/dev/loop7 1.8M 1.8M 0 100% /tmp/tcloop/openssl-1.1.1
/dev/loop8 148K 148K 0 100% /tmp/tcloop/ca-certificates
/dev/loop9 24K 24K 0 100% /tmp/tcloop/libcap
/dev/loop10 244K 244K 0 100% /tmp/tcloop/gmp
/dev/loop11 2.3M 2.3M 0 100% /tmp/tcloop/coreutils
/dev/loop12 88K 88K 0 100% /tmp/tcloop/cpio
/dev/loop13 284K 284K 0 100% /tmp/tcloop/curl
/dev/loop14 72K 72K 0 100% /tmp/tcloop/expat2
/dev/loop15 200K 200K 0 100% /tmp/tcloop/findutils
/dev/loop16 3.9M 3.9M 0 100% /tmp/tcloop/git
/dev/loop17 92K 92K 0 100% /tmp/tcloop/grep
/dev/loop18 48K 48K 0 100% /tmp/tcloop/gzip
/dev/loop19 816K 816K 0 100% /tmp/tcloop/isl
/dev/loop20 216K 216K 0 100% /tmp/tcloop/jq
/dev/loop21 68K 68K 0 100% /tmp/tcloop/jsoncpp
/dev/loop22 52K 52K 0 100% /tmp/tcloop/liblz4
/dev/loop23 308K 308K 0 100% /tmp/tcloop/libzstd
/dev/loop24 76K 76K 0 100% /tmp/tcloop/liblzma
/dev/loop25 600K 600K 0 100% /tmp/tcloop/libxml2
/dev/loop26 56K 56K 0 100% /tmp/tcloop/lzo
/dev/loop27 272K 272K 0 100% /tmp/tcloop/nettle3
/dev/loop28 384K 384K 0 100% /tmp/tcloop/libarchive
/dev/loop29 24K 24K 0 100% /tmp/tcloop/libpci
/dev/loop30 84K 84K 0 100% /tmp/tcloop/librhash
/dev/loop31 128K 128K 0 100% /tmp/tcloop/udev-lib
/dev/loop32 48K 48K 0 100% /tmp/tcloop/libusb
/dev/loop33 68K 68K 0 100% /tmp/tcloop/libuv
/dev/loop34 44K 44K 0 100% /tmp/tcloop/lsscsi
/dev/loop35 60K 60K 0 100% /tmp/tcloop/m4
/dev/loop36 104K 104K 0 100% /tmp/tcloop/make
/dev/loop37 492K 492K 0 100% /tmp/tcloop/raid-dm-5.10.3-tinycore64
/dev/loop38 352K 352K 0 100% /tmp/tcloop/mdadm
/dev/loop39 4.0K 4.0K 0 100% /tmp/tcloop/mirrors
/dev/loop40 232K 232K 0 100% /tmp/tcloop/mpfr
/dev/loop41 48K 48K 0 100% /tmp/tcloop/mpc
/dev/loop42 88K 88K 0 100% /tmp/tcloop/ncursesw-utils
/dev/loop43 740K 740K 0 100% /tmp/tcloop/ncursesw-terminfo
/dev/loop44 1.4M 1.4M 0 100% /tmp/tcloop/openssh
/dev/loop45 76K 76K 0 100% /tmp/tcloop/patch
/dev/loop46 276K 276K 0 100% /tmp/tcloop/pciutils
/dev/loop47 80K 80K 0 100% /tmp/tcloop/sed
/dev/loop48 220K 220K 0 100% /tmp/tcloop/tar
/dev/loop49 288K 288K 0 100% /tmp/tcloop/usb-utils
/dev/loop50 2.1M 2.1M 0 100% /tmp/tcloop/util-linux
/dev/loop51 52K 52K 0 100% /tmp/tcloop/xz

Sorry, I didn't upload the full log.

I tried 3 USB drives, so I don't think they are damaged.

tc@box:~$ df -h
Filesystem      Size  Used Avail Use% Mounted on
rootfs          3.4G   42M  3.4G   2% /
tmpfs           1.9G     0  1.9G   0% /dev/shm
/dev/sda3       899M   52M  847M   6% /mnt/sda3
/dev/loop0       24K   24K     0 100% /tmp/tcloop/attr
/dev/loop1       40K   40K     0 100% /tmp/tcloop/acl
/dev/loop2      252K  252K     0 100% /tmp/tcloop/ncursesw
/dev/loop3      144K  144K     0 100% /tmp/tcloop/readline
/dev/loop4      484K  484K     0 100% /tmp/tcloop/bash
/dev/loop5      5.3M  5.3M     0 100% /tmp/tcloop/binutils
/dev/loop6       32K   32K     0 100% /tmp/tcloop/bzip2-dev
/dev/loop7      1.8M  1.8M     0 100% /tmp/tcloop/openssl-1.1.1
/dev/loop8      148K  148K     0 100% /tmp/tcloop/ca-certificates
/dev/loop9       24K   24K     0 100% /tmp/tcloop/libcap
/dev/loop10     244K  244K     0 100% /tmp/tcloop/gmp
/dev/loop11     2.3M  2.3M     0 100% /tmp/tcloop/coreutils
/dev/loop12      88K   88K     0 100% /tmp/tcloop/cpio
/dev/loop13     284K  284K     0 100% /tmp/tcloop/curl
/dev/loop14      72K   72K     0 100% /tmp/tcloop/expat2
/dev/loop15     200K  200K     0 100% /tmp/tcloop/findutils
/dev/loop16     3.9M  3.9M     0 100% /tmp/tcloop/git
/dev/loop17      92K   92K     0 100% /tmp/tcloop/grep
/dev/loop18      48K   48K     0 100% /tmp/tcloop/gzip
/dev/loop19     816K  816K     0 100% /tmp/tcloop/isl
/dev/loop20     216K  216K     0 100% /tmp/tcloop/jq
/dev/loop21      68K   68K     0 100% /tmp/tcloop/jsoncpp
/dev/loop22      52K   52K     0 100% /tmp/tcloop/liblz4
/dev/loop23     308K  308K     0 100% /tmp/tcloop/libzstd
/dev/loop24      76K   76K     0 100% /tmp/tcloop/liblzma
/dev/loop25     600K  600K     0 100% /tmp/tcloop/libxml2
/dev/loop26      56K   56K     0 100% /tmp/tcloop/lzo
/dev/loop27     272K  272K     0 100% /tmp/tcloop/nettle3
/dev/loop28     384K  384K     0 100% /tmp/tcloop/libarchive
/dev/loop29      24K   24K     0 100% /tmp/tcloop/libpci
/dev/loop30      84K   84K     0 100% /tmp/tcloop/librhash
/dev/loop31     128K  128K     0 100% /tmp/tcloop/udev-lib
/dev/loop32      48K   48K     0 100% /tmp/tcloop/libusb
/dev/loop33      68K   68K     0 100% /tmp/tcloop/libuv
/dev/loop34      44K   44K     0 100% /tmp/tcloop/lsscsi
/dev/loop35      60K   60K     0 100% /tmp/tcloop/m4
/dev/loop36     104K  104K     0 100% /tmp/tcloop/make
/dev/loop37     492K  492K     0 100% /tmp/tcloop/raid-dm-5.10.3-tinycore64
/dev/loop38     352K  352K     0 100% /tmp/tcloop/mdadm
/dev/loop39     4.0K  4.0K     0 100% /tmp/tcloop/mirrors
/dev/loop40     232K  232K     0 100% /tmp/tcloop/mpfr
/dev/loop41      48K   48K     0 100% /tmp/tcloop/mpc
/dev/loop42      88K   88K     0 100% /tmp/tcloop/ncursesw-utils
/dev/loop43     740K  740K     0 100% /tmp/tcloop/ncursesw-terminfo
/dev/loop44     1.4M  1.4M     0 100% /tmp/tcloop/openssh
/dev/loop45      76K   76K     0 100% /tmp/tcloop/patch
/dev/loop46     276K  276K     0 100% /tmp/tcloop/pciutils
/dev/loop47      80K   80K     0 100% /tmp/tcloop/sed
/dev/loop48     220K  220K     0 100% /tmp/tcloop/tar
/dev/loop49     288K  288K     0 100% /tmp/tcloop/usb-utils
/dev/loop50     2.1M  2.1M     0 100% /tmp/tcloop/util-linux
/dev/loop51      52K   52K     0 100% /tmp/tcloop/xz

It has 2.73GB unallocated space, so 4GB should be enough. Maybe sda1 and sda2 are too small?

May 14, 2022

14 minutes ago, Peter Suh said:

It would be nice to receive and use the m-shell below that helps loader building in TC.
I often see some kind of low-space message
The m-shell appropriately uses clean to free up space for the build.

Thanks for your response!

I just tried "./my.sh DS918+". This script is powerful! But still got the same error.

Mounting /dev/sda1 to localdiskp1 
/dev/sda2 localdiskp2
cp: error writing 'localdiskp1/boot/grub/locale/ru.mo': No space left on device
cp: error writing 'localdiskp1/boot/grub/x86_64-efi/gcry_sha512.mod': No space left on device
cp: error writing 'localdiskp1/custom.gz': No space left on device
cp: error writing 'localdiskp1/rd.gz': No space left on device
cp: error writing 'localdiskp1/zImage': No space left on device
Creating tinycore entry
menuentry 'Tiny Core Image Build' {
        savedefault
        set root=(hd0,msdos3)
        echo Loading Linux...
        linux /vmlinuz64 loglevel=3 cde waitusb=5 vga=791
        echo Loading initramfs...
        initrd /corepure64.gz
        echo Booting TinyCore for loader creation
}
Entries in Localdisk bootloader : 
=======================================================================
menuentry 'RedPill DS918+ v7.1.0-42661 (USB, Verbose)' {
menuentry 'RedPill DS918+ v7.1.0-42661 (SATA, Verbose)' {
menuentry 'Tiny Core Image Build' {
Caching files for future use
Found /home/tc/redpill-load/cache/ds918p_42661.pat, copying to cache directory : /mnt/sda3/auxfiles 
Saving user session for future use. Saving current extensions  -> OK !
Saving current user_config.json  -> OK !

Backup in progress...

Clearing local redpill files
Please make sure you are using the latest 1GB img before using backup option
Current /home/tc size is 2.3M , try to keep it less than 1GB as it might not fit into your image
Should i update the sda with your current files [Yy/Nn]
Backing up home files to sda : Backing up files to /mnt/sda3//mydata.tgz  
Done.

tc@box:~$ df -h
Filesystem      Size  Used Avail Use% Mounted on
rootfs          3.4G   42M  3.4G   2% /
tmpfs           1.9G     0  1.9G   0% /dev/shm
/dev/sda3       899M   52M  847M   6% /mnt/sda3

It is a 4GB USB drive and I guess the space is enough...

May 14, 2022

Hi Peter,

I am trying to install 918+ 7.1 on a Lenovo pc, but keep getting these errors. Can you please help? Thank you!

I installed 7.1 on this same pc successfully last month.

No idea why I keep getting this error this time. Tried different USB drives, tried 920+, tried more than 10 times yerterday...no luck.

These are the latest outputs:

tc@box:~$ ./rploader.sh build apollolake-7.0.1-42218
....
Mounting /dev/sda1 to localdiskp1 
/dev/sda2 localdiskp2
cp: error writing 'localdiskp1/zImage': No space left on device
Creating tinycore entry
....

tc@box:~$ ./rploader.sh build apollolake-7.1.0-42661
...
Mounting /dev/sda1 to localdiskp1 
/dev/sda2 localdiskp2
cp: error writing 'localdiskp1/boot/grub/i386-pc/gcry_tiger.mod': No space left on device
cp: error writing 'localdiskp1/boot/grub/locale/ru.mo': No space left on device
cp: error writing 'localdiskp1/boot/grub/x86_64-efi/gcry_sha512.mod': No space left on device
cp: error writing 'localdiskp1/custom.gz': No space left on device
cp: error writing 'localdiskp1/rd.gz': No space left on device
cp: error writing 'localdiskp1/zImage': No space left on device
Creating tinycore entry
...

This pc has a 4G RAM. I used tinycore-redpill-uefi.v0.4.6.img and followed these steps:

./rploader.sh update now
./rploader.sh fullupgrade now
./rploader.sh serialgen DS918+
./rploader.sh identifyusb now
./rploader.sh satamap now
./rploader.sh build apollolake-7.0.1-42218
./rploader.sh clean now
./rploader.sh build apollolake-7.1.0-42661
./rploader.sh clean now; rm -rf /mnt/sdb3/auxfiles; rm -rf /home/tc/custom-module; ./rploader.sh backup now;

If I use this USB drive to boot the pc, I can see these outputs and then the pc reboots. And then "Booting RedPill" again, and then the pc reboots again. It is a loop.

Booting 'RedPill BS918+ v7.1.0-42261 (USB, Verbose)'
Loading Linux...
Loading initramfs...
Starting kernel with USB boot

Sign In

proc

Posts

Joined

Last visited

Content Type

Forums

Posts posted by proc

RedPill TinyCore Loader Installation Guide for DSM 7.1 BareMetal

RedPill TinyCore Loader Installation Guide for DSM 7.1 BareMetal

RedPill TinyCore Loader Installation Guide for DSM 7.1 BareMetal

RedPill TinyCore Loader Installation Guide for DSM 7.1 BareMetal

RedPill TinyCore Loader Installation Guide for DSM 7.1 BareMetal

RedPill TinyCore Loader Installation Guide for DSM 7.1 BareMetal

RedPill TinyCore Loader Installation Guide for DSM 7.1 BareMetal

RedPill TinyCore Loader Installation Guide for DSM 7.1 BareMetal

RedPill TinyCore Loader Installation Guide for DSM 7.1 BareMetal

Forums

What's new

MUST READ

Members