Jump to content
XPEnology Community

maxime

Member
 View Profile  See their activity

  • Posts

    151

  • Joined

  • Last visited

 Content Type 

Posts posted by maxime

    RedPill - the new loader for 6.2.4 - Discussion

    in Developer Discussion Room

    Posted

    20 hours ago, ikky_phoenix said:

    It's easy to overcome that problem. Install with SataPortMap=1 (or 2), after successful installation, delete SataPortMap option and add sata_remap=4\>2:5\>3 option. Your disks will show 1, 2, 3 and 4

    Thanks! I installed it with SataPortMap=2 and it worked. 🙂
    Now, how can I "    delete SataPortMap option and add sata_remap=4\>2:5\>3 option"? Sorry for the stupid question, but I can't understand how to do it 😥

    RedPill TinyCore Loader Installation Guide for DSM 7.1 BareMetal

    in Tutorials and Guides

    Posted

    Probably I'm stupid, but I can't understand how to upgrade working DS3622xs+ 7.0.1-42218 to DSM 7.1.0-42661 😥 
    Can someone help me to understand? If I understand, I should do this:
    1. manual update DSM to 7.1.0-42661 (within DSM)

    2. reboot the XPEnology server and choose TinyCore on startup (3rd menù item)
    3. execute this commands:

    ./rploader.sh clean now
    ./rploader.sh ext broadwellnk-7.1.0-42661 add https://github.com/jimmyGALLAND/redpill-ext/raw/master/acpid/rpext-index.json

    ./rploader.sh build bromolow-7.1.0-42661

    ./rploader.sh clean now; rm -rf /mnt/sdb3/auxfiles; rm -rf /home/tc/custom-module; ./rploader.sh backup now
    4. reboot DSM
    5. manual update DSM to 7.1.0-42661-1 (within DSM)
    6. reboot DSM
    7. manual update DSM to 7.1.0-42661-2 (within DSM)

    Is this correct? Thanks to all! 

    RedPill - the new loader for 6.2.4 - Discussion

    in Developer Discussion Room

    Posted

    11 minutes ago, flyride said:

    Awesome, you have the new satamap code that looks for bad ports.  Thanks for posting that screen.

     

    Ports 3 and 4 on your system need to be set to hotplug.

     

    If you can't do that, then override the number of ports to 2 and then you are limited to 2 disks on that system.

     
    My mainboard has only 4 sata ports, I don't understand why the system find 6 ports! All the 4 sata ports are set as hotplug; I think that pots 3 and 4 are the "ghost ports" the system is detecting... 

    IMG_20220610_155022.jpg

    RedPill - the new loader for 6.2.4 - Discussion

    in Developer Discussion Room

    Posted

    Anyone can help me with sata controller?
    My mainboard has 4 sata ports on board and actually I'm trying to install DSM 7.01 on only one disk.

    satamap.thumb.png.6eacceab7576aca2ee86cb42fb4abaa9.png

      

    tc@box:~$ ls -la /sys/block
total 0
drwxr-xr-x  2 root root 0 Jun 10 14:46 ./
dr-xr-xr-x 13 root root 0 Jun 10 14:45 ../
lrwxrwxrwx  1 root root 0 Jun 10 14:46 loop0 -> ../devices/virtual/block/loop0
lrwxrwxrwx  1 root root 0 Jun 10 14:46 loop1 -> ../devices/virtual/block/loop1
lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop10 -> ../devices/virtual/block/loop10
lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop11 -> ../devices/virtual/block/loop11
lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop12 -> ../devices/virtual/block/loop12
lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop13 -> ../devices/virtual/block/loop13
lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop14 -> ../devices/virtual/block/loop14
lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop15 -> ../devices/virtual/block/loop15
lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop16 -> ../devices/virtual/block/loop16
lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop17 -> ../devices/virtual/block/loop17
lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop18 -> ../devices/virtual/block/loop18
lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop19 -> ../devices/virtual/block/loop19
lrwxrwxrwx  1 root root 0 Jun 10 14:46 loop2 -> ../devices/virtual/block/loop2
lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop20 -> ../devices/virtual/block/loop20
lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop21 -> ../devices/virtual/block/loop21
lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop22 -> ../devices/virtual/block/loop22
lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop23 -> ../devices/virtual/block/loop23
lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop24 -> ../devices/virtual/block/loop24
lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop25 -> ../devices/virtual/block/loop25
lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop26 -> ../devices/virtual/block/loop26
lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop27 -> ../devices/virtual/block/loop27
lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop28 -> ../devices/virtual/block/loop28
lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop29 -> ../devices/virtual/block/loop29
lrwxrwxrwx  1 root root 0 Jun 10 14:46 loop3 -> ../devices/virtual/block/loop3
lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop30 -> ../devices/virtual/block/loop30
lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop31 -> ../devices/virtual/block/loop31
lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop32 -> ../devices/virtual/block/loop32
lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop33 -> ../devices/virtual/block/loop33
lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop34 -> ../devices/virtual/block/loop34
lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop35 -> ../devices/virtual/block/loop35
lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop36 -> ../devices/virtual/block/loop36
lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop37 -> ../devices/virtual/block/loop37
lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop38 -> ../devices/virtual/block/loop38
lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop39 -> ../devices/virtual/block/loop39
lrwxrwxrwx  1 root root 0 Jun 10 14:46 loop4 -> ../devices/virtual/block/loop4
lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop40 -> ../devices/virtual/block/loop40
lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop41 -> ../devices/virtual/block/loop41
lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop42 -> ../devices/virtual/block/loop42
lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop43 -> ../devices/virtual/block/loop43
lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop44 -> ../devices/virtual/block/loop44
lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop45 -> ../devices/virtual/block/loop45
lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop46 -> ../devices/virtual/block/loop46
lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop47 -> ../devices/virtual/block/loop47
lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop48 -> ../devices/virtual/block/loop48
lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop49 -> ../devices/virtual/block/loop49
lrwxrwxrwx  1 root root 0 Jun 10 14:46 loop5 -> ../devices/virtual/block/loop5
lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop50 -> ../devices/virtual/block/loop50
lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop51 -> ../devices/virtual/block/loop51
lrwxrwxrwx  1 root root 0 Jun 10 14:46 loop6 -> ../devices/virtual/block/loop6
lrwxrwxrwx  1 root root 0 Jun 10 14:46 loop7 -> ../devices/virtual/block/loop7
lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop8 -> ../devices/virtual/block/loop8
lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop9 -> ../devices/virtual/block/loop9
lrwxrwxrwx  1 root root 0 Jun 10 14:46 ram0 -> ../devices/virtual/block/ram0
lrwxrwxrwx  1 root root 0 Jun 10 14:46 ram1 -> ../devices/virtual/block/ram1
lrwxrwxrwx  1 root root 0 Jun 10 14:46 ram2 -> ../devices/virtual/block/ram2
lrwxrwxrwx  1 root root 0 Jun 10 14:46 ram3 -> ../devices/virtual/block/ram3
lrwxrwxrwx  1 root root 0 Jun 10 14:46 ram4 -> ../devices/virtual/block/ram4
lrwxrwxrwx  1 root root 0 Jun 10 14:46 ram5 -> ../devices/virtual/block/ram5
lrwxrwxrwx  1 root root 0 Jun 10 14:46 ram6 -> ../devices/virtual/block/ram6
lrwxrwxrwx  1 root root 0 Jun 10 14:46 ram7 -> ../devices/virtual/block/ram7
lrwxrwxrwx  1 root root 0 Jun 10 14:46 sda -> ../devices/pci0000:00/0000:00:1f.2/       ata1/host0/target0:0:0/0:0:0:0/block/sda
lrwxrwxrwx  1 root root 0 Jun 10 14:46 sdb -> ../devices/pci0000:00/0000:00:1d.0/       usb2/2-1/2-1.3/2-1.3:1.0/host6/target6:0:0/6:0:0:0/block/sdb
lrwxrwxrwx  1 root root 0 Jun 10 14:46 zram0 -> ../devices/virtual/block/zram0
tc@box:~$ tc@box:~$ ls -la /sys/block
-sh: tc@box:~$: not found
tc@box:~$ total 0
-sh: total: not found
tc@box:~$ drwxr-xr-x  2 root root 0 Jun 10 14:46 ./
-sh: drwxr-xr-x: not found
tc@box:~$ dr-xr-xr-x 13 root root 0 Jun 10 14:45 ../
-sh: dr-xr-xr-x: not found
tc@box:~$ lrwxrwxrwx  1 root root 0 Jun 10 14:46 loop0 -> ../devices/virtual/block/loop0
-sh: can't create ../devices/virtual/block/loop0: nonexistent directory
tc@box:~$ lrwxrwxrwx  1 root root 0 Jun 10 14:46 loop1 -> ../devices/virtual/block/loop1
-sh: can't create ../devices/virtual/block/loop1: nonexistent directory
tc@box:~$ lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop10 -> ../devices/virtual/block/loop
10
-sh: can't create ../devices/virtual/block/loop10: nonexistent directory
tc@box:~$ lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop11 -> ../devices/virtual/block/loop
11
o-sh: can't create ../devices/virtual/block/loop11: nonexistent directory
tc@box:~$ lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop12 -> ../devices/virtual/block/loop
12
-sh: can't create ../devices/virtual/block/loop12: nonexistent directory
tc@box:~$ lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop13 -> ../devices/virtual/block/loop
13
-sh: can't create ../devices/virtual/block/loop13: nonexistent directory
tc@box:~$ lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop14 -> ../devices/virtual/block/loop
14
rwx-sh: can't create ../devices/virtual/block/loop14: nonexistent directory
tc@box:~$ lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop15 -> ../devices/virtual/block/loop
15
wxrwxr-sh: can't create ../devices/virtual/block/loop15: nonexistent directory
tc@box:~$ lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop16 -> ../devices/virtual/block/loop
16
-sh: can't create ../devices/virtual/block/loop16: nonexistent directory
tc@box:~$ lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop17 -> ../devices/virtual/block/loop
17
-sh: can't create ../devices/virtual/block/loop17: nonexistent directory
tc@box:~$ lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop18 -> ../devices/virtual/block/loop
18
b ->-sh: can't create ../devices/virtual/block/loop18: nonexistent directory
tc@box:~$ lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop19 -> ../devices/virtual/block/loop
19
6-sh: can't create ../devices/virtual/block/loop19: nonexistent directory
tc@box:~$ lrwxrwxrwx  1 root root 0 Jun 10 14:46 loop2 -> ../devices/virtual/block/loop2
-sh: can't create ../devices/virtual/block/loop2: nonexistent directory
tc@box:~$ lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop20 -> ../devices/virtual/block/loop
20
-sh: can't create ../devices/virtual/block/loop20: nonexistent directory
tc@box:~$ lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop21 -> ../devices/virtual/block/loop
21
-sh: can't create ../devices/virtual/block/loop21: nonexistent directory
tc@box:~$ lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop22 -> ../devices/virtual/block/loop
22
-sh: can't create ../devices/virtual/block/loop22: nonexistent directory
tc@box:~$ lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop23 -> ../devices/virtual/block/loop
23
-sh: can't create ../devices/virtual/block/loop23: nonexistent directory
tc@box:~$ lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop24 -> ../devices/virtual/block/loop
24
-sh: can't create ../devices/virtual/block/loop24: nonexistent directory
tc@box:~$ lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop25 -> ../devices/virtual/block/loop
25
-sh: can't create ../devices/virtual/block/loop25: nonexistent directory
tc@box:~$ lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop26 -> ../devices/virtual/block/loop
26
-sh: can't create ../devices/virtual/block/loop26: nonexistent directory
tc@box:~$ lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop27 -> ../devices/virtual/block/loop
27
-sh: can't create ../devices/virtual/block/loop27: nonexistent directory
tc@box:~$ lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop28 -> ../devices/virtual/block/loop
28
-sh: can't create ../devices/virtual/block/loop28: nonexistent directory
tc@box:~$ lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop29 -> ../devices/virtual/block/loop
29
-sh: can't create ../devices/virtual/block/loop29: nonexistent directory
tc@box:~$ lrwxrwxrwx  1 root root 0 Jun 10 14:46 loop3 -> ../devices/virtual/block/loop3
-sh: can't create ../devices/virtual/block/loop3: nonexistent directory
tc@box:~$ lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop30 -> ../devices/virtual/block/loop
30
-sh: can't create ../devices/virtual/block/loop30: nonexistent directory
tc@box:~$ lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop31 -> ../devices/virtual/block/loop
31
-sh: can't create ../devices/virtual/block/loop31: nonexistent directory
tc@box:~$ lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop32 -> ../devices/virtual/block/loop
32
-sh: can't create ../devices/virtual/block/loop32: nonexistent directory
tc@box:~$ lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop33 -> ../devices/virtual/block/loop
33
-sh: can't create ../devices/virtual/block/loop33: nonexistent directory
tc@box:~$ lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop34 -> ../devices/virtual/block/loop
34
-sh: can't create ../devices/virtual/block/loop34: nonexistent directory
tc@box:~$ lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop35 -> ../devices/virtual/block/loop
35
-sh: can't create ../devices/virtual/block/loop35: nonexistent directory
tc@box:~$ lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop36 -> ../devices/virtual/block/loop
36
-sh: can't create ../devices/virtual/block/loop36: nonexistent directory
tc@box:~$ lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop37 -> ../devices/virtual/block/loop
37
-sh: can't create ../devices/virtual/block/loop37: nonexistent directory
tc@box:~$ lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop38 -> ../devices/virtual/block/loop
38
-sh: can't create ../devices/virtual/block/loop38: nonexistent directory
tc@box:~$ lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop39 -> ../devices/virtual/block/loop
39
-sh: can't create ../devices/virtual/block/loop39: nonexistent directory
tc@box:~$ lrwxrwxrwx  1 root root 0 Jun 10 14:46 loop4 -> ../devices/virtual/block/loop4
-sh: can't create ../devices/virtual/block/loop4: nonexistent directory
tc@box:~$ lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop40 -> ../devices/virtual/block/loop
40
-sh: can't create ../devices/virtual/block/loop40: nonexistent directory
tc@box:~$ lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop41 -> ../devices/virtual/block/loop
41
-sh: can't create ../devices/virtual/block/loop41: nonexistent directory
tc@box:~$ lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop42 -> ../devices/virtual/block/loop
42
-sh: can't create ../devices/virtual/block/loop42: nonexistent directory
tc@box:~$ lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop43 -> ../devices/virtual/block/loop
43
-sh: can't create ../devices/virtual/block/loop43: nonexistent directory
tc@box:~$ lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop44 -> ../devices/virtual/block/loop
44
-sh: can't create ../devices/virtual/block/loop44: nonexistent directory
tc@box:~$ lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop45 -> ../devices/virtual/block/loop
45
-sh: can't create ../devices/virtual/block/loop45: nonexistent directory
tc@box:~$ lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop46 -> ../devices/virtual/block/loop
46
-sh: can't create ../devices/virtual/block/loop46: nonexistent directory
tc@box:~$ lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop47 -> ../devices/virtual/block/loop
47
-sh: can't create ../devices/virtual/block/loop47: nonexistent directory
tc@box:~$ lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop48 -> ../devices/virtual/block/loop
48
-sh: can't create ../devices/virtual/block/loop48: nonexistent directory
tc@box:~$ lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop49 -> ../devices/virtual/block/loop
49
-sh: can't create ../devices/virtual/block/loop49: nonexistent directory
tc@box:~$ lrwxrwxrwx  1 root root 0 Jun 10 14:46 loop5 -> ../devices/virtual/block/loop5
-sh: can't create ../devices/virtual/block/loop5: nonexistent directory
tc@box:~$ lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop50 -> ../devices/virtual/block/loop
50
-sh: can't create ../devices/virtual/block/loop50: nonexistent directory
tc@box:~$ lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop51 -> ../devices/virtual/block/loop
51
-sh: can't create ../devices/virtual/block/loop51: nonexistent directory
tc@box:~$ lrwxrwxrwx  1 root root 0 Jun 10 14:46 loop6 -> ../devices/virtual/block/loop6
-sh: can't create ../devices/virtual/block/loop6: nonexistent directory
tc@box:~$ lrwxrwxrwx  1 root root 0 Jun 10 14:46 loop7 -> ../devices/virtual/block/loop7
-sh: can't create ../devices/virtual/block/loop7: nonexistent directory
tc@box:~$ lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop8 -> ../devices/virtual/block/loop8
-sh: can't create ../devices/virtual/block/loop8: nonexistent directory
tc@box:~$ lrwxrwxrwx  1 root root 0 Jun 10 14:58 loop9 -> ../devices/virtual/block/loop9
-sh: can't create ../devices/virtual/block/loop9: nonexistent directory
tc@box:~$ lrwxrwxrwx  1 root root 0 Jun 10 14:46 ram0 -> ../devices/virtual/block/ram0
-sh: can't create ../devices/virtual/block/ram0: nonexistent directory
tc@box:~$ lrwxrwxrwx  1 root root 0 Jun 10 14:46 ram1 -> ../devices/virtual/block/ram1
-sh: can't create ../devices/virtual/block/ram1: nonexistent directory
tc@box:~$ lrwxrwxrwx  1 root root 0 Jun 10 14:46 ram2 -> ../devices/virtual/block/ram2
-sh: can't create ../devices/virtual/block/ram2: nonexistent directory
tc@box:~$ lrwxrwxrwx  1 root root 0 Jun 10 14:46 ram3 -> ../devices/virtual/block/ram3
-sh: can't create ../devices/virtual/block/ram3: nonexistent directory
tc@box:~$ lrwxrwxrwx  1 root root 0 Jun 10 14:46 ram4 -> ../devices/virtual/block/ram4
-sh: can't create ../devices/virtual/block/ram4: nonexistent directory
tc@box:~$ lrwxrwxrwx  1 root root 0 Jun 10 14:46 ram5 -> ../devices/virtual/block/ram5
-sh: can't create ../devices/virtual/block/ram5: nonexistent directory
tc@box:~$ lrwxrwxrwx  1 root root 0 Jun 10 14:46 ram6 -> ../devices/virtual/block/ram6
-sh: can't create ../devices/virtual/block/ram6: nonexistent directory
tc@box:~$ lrwxrwxrwx  1 root root 0 Jun 10 14:46 ram7 -> ../devices/virtual/block/ram7
-sh: can't create ../devices/virtual/block/ram7: nonexistent directory
tc@box:~$ lrwxrwxrwx  1 root root 0 Jun 10 14:46 sda -> ../devices/pci0000:00/0000:00:1f
.2/       ata1/host0/target0:0:0/0:0:0:0/block/sda
-sh: can't create ../devices/pci0000:00/0000:00:1f.2/: nonexistent directory
tc@box:~$ lrwxrwxrwx  1 root root 0 Jun 10 14:46 sdb -> ../devices/pci0000:00/0000:00:1d
.0/       usb2/2-1/2-1.3/2-1.3:1.0/host6/target6:0:0/6:0:0:0/block/sdb
-sh: can't create ../devices/pci0000:00/0000:00:1d.0/: nonexistent directory
tc@box:~$ lrwxrwxrwx  1 root root 0 Jun 10 14:46 zram0 -> ../devices/virtual/block/zram0
-sh: can't create ../devices/virtual/block/zram0: nonexistent directory
tc@box:~$ tc@box:~$
-sh: tc@box:~$: not found
tc@box:~$

     

    TinyCore RedPill Loader (TCRP)

    in Loaders

    Posted

    On 25/2/2022 at 14:55, Orphée said:

    È già stato spiegato più volte.

     

    SataPortMap definisce il numero di porte contenute in ciascun controller SATA. impostato su 1 cifra.

    58 significa: il primo controller SATA ha 5 porte (5 dischi SATA collegabili), il secondo controller SATA ha 8 porte (8 dischi SATA collegabili)

     

    DiskIdxMap definisce la posizione iniziale della mappatura del disco per ogni controller, impostata su 2 cifre.

    00 = / sviluppo / sda

    01 = /dev/sdb

    eccetera...

     

    quindi 0A00 significa :

    - Le prime 2 cifre sono 0A: è l'undicesima posizione: /dev/sdk

    - La seconda cifra è 00: è la prima pozione: /dev/sda

     

    Quindi i primi dischi del controller inizieranno da sdk a sdo

    e il secondo disco del controller partirà da sda a sdh

     

    A seconda di quanti controller SATA hai sulla tua scheda madre (sono tutti sulla scheda madre, o hai una scheda PCI, o nmve... ecc...) il numero può essere diverso da una configurazione all'altra.

     

    Considerando che su ESXi si definiscono i numeri del controller SATA (come SATA0:0 per il caricatore e SATA1:x per i dischi DATA)

    di solito usando le impostazioni di cui sopra, puoi impostare SataPortMap = 18 e DiskIdxMap su qualcosa come 1000

    Poiché hai solo il caricatore impostato su SATA0, puoi avere la prima cifra impostata solo su 1, dove il secondo numero sarà 8 per poter avere 8 dischi (virtuali o RDM) collegati al controller SATA 1.


    Then if I have a mainboard with only one controller, 4 sata ports, only one drive connected (on sata0 illustrated on the mainboard), it should be:
    SataPortMap=4
    DiskIdxMap=00
    Is it right? Why did not works?!? 
     

    TinyCore RedPill Loader (TCRP)

    in Loaders

    Posted

    9 minutes ago, Orphée said:

    @maxime your real mac address is the one you have when booting on tinycore OS.

    It is fake only when loading DSM loader.

     
    Why I see the fake Mac Address in the bios? mac on Bios and mac on DSM are the same! I expeted to have REAL mac on bios and fake mac on DSM... 🤔

    TinyCore RedPill Loader (TCRP)

    in Loaders

    Posted

    Hi! I finaly have my DS918+ working! There are many "problems" that I can't understand; sorry for this long pot, I hope you can help me.

    1. My mainboard has 6 onboard sata ports; I tried to install Xpenology connecting only one HDD, but in this situation I was not able to install DSM. When I connected all 6 HDD, I was able to succesfully install DSM. Why? How can I solve this problem? I'm asking this because if I will need to run the system without a (broken) HDD, I'm afraid I will could not.
    https://www.dropbox.com/s/fa3wrzhr3ft3emf/sataerror.jpg?dl=0

    https://www.dropbox.com/s/gizgdli6quz7pxg/satamap.jpg?dl=0
     

    2. If I leave connected my SD Card reader, I can't write USB vendor ID on grub.cfg file. I had to fisically disconnect my SD card reader for correctly use my Sandisk USB pendrive
    https://www.dropbox.com/s/037cjtuayhptqi3/usbboot.jpg?dl=0

    3. I'm not able to know which is the REAL Mac Address of my integrated lan NIC, because FAKE Synology Mac Adress is displayed. How can I know the REAL Mac Address? I have to use it for DHCP server prenotation and WOL
    https://www.dropbox.com/s/1requw76g5hskvk/macaddress.jpg?dl=0
    https://www.dropbox.com/s/6xvlacqlmhpavs6/vendor.png?dl=0

    This is my grub.cfg file:
      

    #
# ### !!! WARNING - READ ME !!! ###
#
# DO NOT edit this file. This file has been generated automatically by the loader generator.
# If you were asked to use a pre-made image and asked by someone to edit this file DO NOT do it. The only
# supported method of obtaining the loader image is generating it using the loader generator provided.
#

terminal_output console
if serial --unit=0 --speed=115200; then
    terminal_input --append serial_com0
    terminal_output --append serial_com0
fi

set default="0"
set timeout="5"
set timeout_style="menu"

if [ -s $prefix/grubenv ]; then
    load_env --file $prefix/grubenv --skip-sig
    set has_env="1"
    if [ -n "${saved_entry}" ]; then
        set default="${saved_entry}"
    fi
else
    set has_env="0"
    echo "WARN: failed to load env. Default choice will NOT be saved!"
fi


function savedefault {
    saved_entry="${chosen}"
    save_env --file $prefix/grubenv saved_entry
}


insmod usb_keyboard
insmod part_msdos
insmod ext2
insmod fat
insmod linux
insmod gzio

set gfxmode=auto
insmod vbe
insmod vga

# UEFI
insmod efi_gop
insmod efi_uga

insmod font
if loadfont ${prefix}/unicode.pf2
then
    insmod gfxterm
    set gfxmode=auto
    set gfxpayload=keep
    terminal_output gfxterm
fi

menuentry 'RedPill DS918+ v7.0.1-42218 (USB, Verbose)' {
	savedefault
	set root=(hd0,msdos1)
	echo Loading Linux...
	linux /zImage withefi earlyprintk syno_hw_version=DS918+ console=ttyS0,115200n8 netif_num=1 pid=0x5583 earlycon=uart8250,io,0x3f8,115200n8 syno_port_thaw=1 mac1=0011322A7C48 sn=1790PDN025020 vid=0x0781 elevator=elevator loglevel=15 HddHotplug=0 DiskIdxMap=00 syno_hdd_detect=0 vender_format_version=2 syno_hdd_powerup_seq=1 log_buf_len=32M root=/dev/md0 SataPortMap=6 
	echo Loading initramfs...
	initrd /rd.gz /custom.gz
	echo Starting kernel with USB boot
}

menuentry 'RedPill DS918+ v7.0.1-42218 (SATA, Verbose)' {
	savedefault
	set root=(hd0,msdos1)
	echo Loading Linux...
	linux /zImage withefi earlyprintk syno_hw_version=DS918+ console=ttyS0,115200n8 netif_num=1 pid=0x5583 earlycon=uart8250,io,0x3f8,115200n8 synoboot_satadom=2 syno_port_thaw=1 mac1=0011322AXXXX sn=1790PDN02XXXX vid=0x0781 elevator=elevator loglevel=15 HddHotplug=0 DiskIdxMap=00 syno_hdd_detect=0 vender_format_version=2 syno_hdd_powerup_seq=1 log_buf_len=32M root=/dev/md0 SataPortMap=6 
	echo Loading initramfs...
	initrd /rd.gz /custom.gz
	echo Starting kernel with SATA boot
	echo WARNING: SATA boot support on this platform is experimental!
}


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
}

     

    TinyCore RedPill Loader (TCRP)

    in Loaders

    Posted

    14 hours ago, pocopico said:


    i always like to start with SataPortMap=58 and DiskIdxMap=0800 and evaluate results accordingly 

     

    10 hours ago, Dvalin21 said:

    I started at default 58 and 0A00 and it worked for me

     

    Please, is there a guide for this? I can't understand the logic behind SataPortMap and DiskIdxMap values

    TinyCore RedPill Loader (TCRP)

    in Loaders

    Posted

    11 hours ago, altas said:

    cool thx !

     

    so then i can confirm that my Test migration from DS3617xs to DS3622xs+ was successfully (Baremetal)

    i used 1 HDD with some Test Data and everything was still available.

     

    Steps i did

     

    1. block internet to DS3617xs

    2 turn off the DS

    3 switch the Loader (USB Stick)

    4 Boot up and wait until the DS come up and reachable in the Network (ping)

    5 use the pat file from the tinyloader and start migration, i used the Option dont keep settings( 2.Option), maybe someone can use NR1 as test :)

    6 wait until the migration process has reached 100%, then the DS should rest as usual,

    7 wait until the DS is back online and you can process with DSM7 Wizard to complet.

     

    Thanks for the info. In case the migration process went wrong, do you think that putting the usb pendrive (with the bootloader of the DS3617xs) back,  would be working again? Or could the data have been compromised?

    TinyCore RedPill Loader (TCRP)

    in Loaders

    Posted

    8 hours ago, pocopico said:

     

    Its a typical SataPortMap and DiskIdxMap issue... Search the forum for that 

    I can't find a solution... I can't understand the logic behind SataPortMap and DiskIdxMap values 😔
    If anyone of you could give me an help, I would really appreciate it.

    TinyCore RedPill Loader (TCRP)

    in Loaders

    Posted

    On 1/24/2022 at 11:59 PM, kami001 said:

    I managed to run DS3615xs on BareMetal having my NIC recognised after having included all the Realtek extensions (r8169, r8168, r8152, r8125, r8101).

     

     

    My hardware build:

    Motherboard: Asus P8H61-I LX

    CPU: Intel i3 3245

     

     

    Hi Kami! Could you please explain me how to add Realtek extension? Thank you very much!

    Change disks order

    in General Questions

    Posted

    Hi everyone! I'm planning to change hardware configuration of my XPEnology. I would make the new build and move my 6 HDDs from the old configuration; the problem is that I don't know how to to preserve the order of the HDDs. May be a problem invert the HDDs order?
    Thanks for your support!

    The New Active Backup

    in Synology Packages

    Posted · Edited by maxime

    On 11/21/2020 at 12:14 AM, EXPLOit said:

    Have you done LOG IN before ?

    https://URL:PORT /webapi/auth.cgi?api=SYNO.API.Auth&method=Login&version=1&account=USER&passwd=PASS

    Yes. And it works
    Only when I try this  

    http://URL:PORT/webapi/entry.cgi?api=SYNO.ActiveBackup.Activation&method=set&version=1&activated=true&serial_number="SERIALNUMBER"


    I receive the error

    DSM 6.x Proxmox Backup Template

    in DSM 6.x

    Posted

    On 11/21/2020 at 6:23 PM, codedmind said:

    Hello, after restore i start the vm went to find.synology setup the account then try update but always get corrupted file... is that normal?

     

    I don't pretend keep the vm online, should i change mac and serial number, vid/pid?

     

    @arkilee how can i know the vid/pid after the backup restore?

     

    Thanks

    Before update you have at least to create a volume. Did you do it?

×
×
  • Create New...