flyride Posted May 19, 2022 Share #3476 Posted May 19, 2022 30 minutes ago, phone guy said: Found "00:1f.2 SATA controller: Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 6 port SATA Controller [AHCI mode] (rev 02)" (1 drive(s) connected) How many ports should be mapped for this controller? [0-9] <1> 0 This is not your hypervisor boot disk. The SATA controller you see here is virtualized and part of your VM. That means your VM has an embedded disk device that we haven't accounted for. 1 Quote Link to comment Share on other sites More sharing options...
phone guy Posted May 19, 2022 Share #3477 Posted May 19, 2022 3 minutes ago, flyride said: This is not your hypervisor boot disk. The SATA controller you see here is virtualized and part of your VM. That means your VM has an embedded disk device that we haven't accounted for. Like you said, I guess its a proxmox thing? Maybe when you get bored you can try out proxmox and see? I obviously do not know 9 minutes ago, flyride said: Just to assuage my curiosity, run this when you have a moment - at this point I'm betting that it is just a kernel stub and not an actual device, but to see it mapped to Class 106 is odd (on all my systems it doesn't show a class). lspci -kvd 1b4b:9235 Here are those results root@DS3622:~# lspci -kvd 1b4b:9235 0001:09:00.0 Class 0106: Device 1b4b:9235 (rev 11) (prog-if 01) Flags: fast devsel 0001:0c:00.0 Class 0106: Device 1b4b:9235 (rev 11) (prog-if 01) Flags: fast devsel root@DS3622:~# Quote Link to comment Share on other sites More sharing options...
phone guy Posted May 19, 2022 Share #3478 Posted May 19, 2022 @flyride If you want any other information, I will be happy to provide or test at your discretion. Thank you again for taking the time to try and help! I really appreciate it! Quote Link to comment Share on other sites More sharing options...
flyride Posted May 19, 2022 Share #3479 Posted May 19, 2022 Well I did have a suggestion about that unknown disk device. I'm guessing it's a 32GB VMDK (pic from your tutorial): If you can verify this, and then rerun ./rploader.sh satamap now and accept it into the system, I think you may find it's mapped to /dev/sda where that slot is empty now. If that's the case, we may be able to map it outside the usable range and let your LSI start with the first slot. But it's up to you. Quote Link to comment Share on other sites More sharing options...
phone guy Posted May 19, 2022 Share #3480 Posted May 19, 2022 2 minutes ago, flyride said: Well I did have a suggestion about that unknown disk device. I'm guessing it's a 32GB VMDK (pic from your tutorial): If you can verify this, and then rerun ./rploader.sh satamap now and accept it into the system, I think you may find it's mapped to /dev/sda where that slot is empty now. If that's the case, we may be able to map it outside the usable range and let your LSI start with the first slot. But it's up to you. Thats not the VM I am running as my dsm, that was just one I did for the tutorial with everything default to make it less confusing for others. My personal VM, doesnt have any emu hdd as you see above in that picture. Mine looks like this: I will re-build loader. and let rploader satamap set its defaults (which were 1 on sata connection 1 which is the built in sata ports on the motherboard, and 5 on sata connection 2 which is the hba card. as I only have 5 hdds connected at this time (waiting on the PSU power cable 😛 ) I'll post results in a minute Quote Link to comment Share on other sites More sharing options...
flyride Posted May 19, 2022 Share #3481 Posted May 19, 2022 7 minutes ago, phone guy said: (which were 1 on sata connection 1 which is the built in sata ports on the motherboar Again, on this we disagree. Your motherboard SATA is Cougar Point (C204) which is PCI ID 8086.1c02. That isn't what's coming back attached to that disk. https://pci-ids.ucw.cz/read/PC/8086/1c02 Quote Link to comment Share on other sites More sharing options...
phone guy Posted May 19, 2022 Share #3482 Posted May 19, 2022 10 minutes ago, flyride said: Well I did have a suggestion about that unknown disk device. I'm guessing it's a 32GB VMDK (pic from your tutorial): If you can verify this, and then rerun ./rploader.sh satamap now and accept it into the system, I think you may find it's mapped to /dev/sda where that slot is empty now. If that's the case, we may be able to map it outside the usable range and let your LSI start with the first slot. But it's up to you. Ok, rebuilding loader again. Just to be thorough, first I run update now and fullupgrade now Then satamap now I left defaults in place, which were 1 for first controller and 5 for next controller tc@box:~$ ./rploader.sh satamap now Machine is VIRTUAL Hypervisor=KVM Found SCSI HBAs, We need to install the SCSI modules Downloading: scsi-5.10.3-tinycore64.tcz Connecting to repo.tinycorelinux.net (89.22.99.37:80) saving to 'scsi-5.10.3-tinycore64.tcz' scsi-5.10.3-tinycore 100% |*******************************************************************************************| 2632k 0:00:00 ETA 'scsi-5.10.3-tinycore64.tcz' saved scsi-5.10.3-tinycore64.tcz: OK Succesfully installed SCSI modules Found "00:1f.2 SATA controller: Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 6 port SATA Controller [AHCI mode] (rev 02)" (1 drive(s) connected) How many ports should be mapped for this controller? [0-9] <1> Found "01:00.0 Serial Attached SCSI controller: LSI Logic / Symbios Logic SAS2308 PCI-Express Fusion-MPT SAS-2 (rev 01)" (5 drive(s) connected) How many ports should be mapped for this controller? [0-9] <5> SataPortMap=15 DiskIdxMap=0001 Should i update the user_config.json with these values ? [Yy/Nn] y Done. Then added ext for acpi, v9fs and misc. Then ./rploader.sh build broadwellnk-7.1.0-42661 and reboot, select usb verbose from tcrp menu. and here I am back to dsm with disks on hba starting on slot #2. Quote Link to comment Share on other sites More sharing options...
flyride Posted May 19, 2022 Share #3483 Posted May 19, 2022 Is there an unused disk in slot #1? Quote Link to comment Share on other sites More sharing options...
phone guy Posted May 19, 2022 Share #3484 Posted May 19, 2022 3 minutes ago, flyride said: Again, on this we disagree. Your motherboard SATA is Cougar Point (C204) which is PCI ID 8086.1c02. That isn't what's coming back attached to that disk. https://pci-ids.ucw.cz/read/PC/8086/1c02 Ok, so I just rebuild the loader, using ./rploader.sh satamap now defauts, which were 1 and 5 (1 for first sata controller and 5 for second sata controller) which added this to user_config.json "SataPortMap": "15", "DiskIdxMap": "0001" But still HBA drives start at position #2 Quote Link to comment Share on other sites More sharing options...
phone guy Posted May 19, 2022 Share #3485 Posted May 19, 2022 Just now, flyride said: Is there an unused disk in slot #1? Yes unused slot 1, just like all the other pics Quote Link to comment Share on other sites More sharing options...
flyride Posted May 19, 2022 Share #3486 Posted May 19, 2022 ls -la /sys/class/scsi_disk ls -la /sys/block/s* Quote Link to comment Share on other sites More sharing options...
phone guy Posted May 19, 2022 Share #3487 Posted May 19, 2022 1 minute ago, flyride said: ls -la /sys/class/scsi_disk ls -la /sys/block/s* Here you go root@DS3622:~# ls -la /sys/class/scsi_disk total 0 drwxr-xr-x 2 root root 0 May 18 20:55 . drwxr-xr-x 60 root root 0 May 18 20:55 .. lrwxrwxrwx 1 root root 0 May 18 20:55 1:0:0:0 -> ../../devices/pci0000:00/0000:00:1c.0/0000:01:00.0/host1/port-1:0/end_device-1:0/target1:0:0/1:0:0:0/scsi_disk/1:0:0:0 lrwxrwxrwx 1 root root 0 May 18 20:55 1:0:1:0 -> ../../devices/pci0000:00/0000:00:1c.0/0000:01:00.0/host1/port-1:1/end_device-1:1/target1:0:1/1:0:1:0/scsi_disk/1:0:1:0 lrwxrwxrwx 1 root root 0 May 18 20:55 1:0:2:0 -> ../../devices/pci0000:00/0000:00:1c.0/0000:01:00.0/host1/port-1:2/end_device-1:2/target1:0:2/1:0:2:0/scsi_disk/1:0:2:0 lrwxrwxrwx 1 root root 0 May 18 20:55 1:0:3:0 -> ../../devices/pci0000:00/0000:00:1c.0/0000:01:00.0/host1/port-1:3/end_device-1:3/target1:0:3/1:0:3:0/scsi_disk/1:0:3:0 lrwxrwxrwx 1 root root 0 May 18 20:55 1:0:4:0 -> ../../devices/pci0000:00/0000:00:1c.0/0000:01:00.0/host1/port-1:4/end_device-1:4/target1:0:4/1:0:4:0/scsi_disk/1:0:4:0 lrwxrwxrwx 1 root root 0 May 18 20:55 2:0:0:0 -> ../../devices/pci0000:00/0000:00:02.0/usb4/4-1/4-1:1.0/host2/target2:0:0/2:0:0:0/scsi_disk/2:0:0:0 root@DS3622:~# ls -la /sys/block/s* lrwxrwxrwx 1 root root 0 May 18 20:55 /sys/block/sdb -> ../devices/pci0000:00/0000:00:1c.0/0000:01:00.0/host1/port-1:0/end_device-1:0/target1:0:0/1:0:0:0/block/sdb lrwxrwxrwx 1 root root 0 May 18 20:55 /sys/block/sdc -> ../devices/pci0000:00/0000:00:1c.0/0000:01:00.0/host1/port-1:1/end_device-1:1/target1:0:1/1:0:1:0/block/sdc lrwxrwxrwx 1 root root 0 May 18 20:55 /sys/block/sdd -> ../devices/pci0000:00/0000:00:1c.0/0000:01:00.0/host1/port-1:2/end_device-1:2/target1:0:2/1:0:2:0/block/sdd lrwxrwxrwx 1 root root 0 May 18 20:55 /sys/block/sde -> ../devices/pci0000:00/0000:00:1c.0/0000:01:00.0/host1/port-1:3/end_device-1:3/target1:0:3/1:0:3:0/block/sde lrwxrwxrwx 1 root root 0 May 18 20:55 /sys/block/sdf -> ../devices/pci0000:00/0000:00:1c.0/0000:01:00.0/host1/port-1:4/end_device-1:4/target1:0:4/1:0:4:0/block/sdf lrwxrwxrwx 1 root root 0 May 18 20:55 /sys/block/synoboot -> ../devices/pci0000:00/0000:00:02.0/usb4/4-1/4-1:1.0/host2/target2:0:0/2:0:0:0/block/synoboot root@DS3622:~# We really need a terminal or shell prompt loadable from dsm to issue commands without ssh Quote Link to comment Share on other sites More sharing options...
flyride Posted May 19, 2022 Share #3488 Posted May 19, 2022 Please go back into TInyCore and repeat the two ls commands from there. That's probably my last ask for today. You probably are getting tired of this, and that is ok to stop, but I am learning things about Proxmox which will help in the future. Quote Link to comment Share on other sites More sharing options...
phone guy Posted May 19, 2022 Share #3489 Posted May 19, 2022 1 minute ago, flyride said: Please go back into TInyCore and repeat the two ls commands from there. That's probably my last ask for today. You probably are getting tired of this, and that is ok to stop, but I am learning things about Proxmox which will help in the future. I am NOT tired of this, I figured you were I am willing to continue as long as you are! Booting back to tcrp, give me a second. Quote Link to comment Share on other sites More sharing options...
phone guy Posted May 19, 2022 Share #3490 Posted May 19, 2022 5 minutes ago, flyride said: Please go back into TInyCore and repeat the two ls commands from there. That's probably my last ask for today. You probably are getting tired of this, and that is ok to stop, but I am learning things about Proxmox which will help in the future. From SSH while tiny core is loaded. tc@box:~$ ls -la /sys/class/scsi_disk total 0 drwxr-xr-x 2 root root 0 May 19 02:12 ./ drwxr-xr-x 61 root root 0 May 19 02:12 ../ lrwxrwxrwx 1 root root 0 May 19 02:12 6:0:0:0 -> ../../devices/pci0000:00/0000:00:02.0/usb10/10-1/10-1:1.0/host6/target6:0:0/6:0:0:0/scsi_disk/6:0:0:0 tc@box:~$ ls -la /sys/block/s* lrwxrwxrwx 1 root root 0 May 19 02:12 /sys/block/sda -> ../devices/pci0000:00/0000:00:02.0/usb10/10-1/10-1:1.0/host6/target6:0:0/6:0:0:0/block/sda lrwxrwxrwx 1 root root 0 May 19 02:12 /sys/block/sr0 -> ../devices/pci0000:00/0000:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sr0 tc@box:~$ Quote Link to comment Share on other sites More sharing options...
flyride Posted May 19, 2022 Share #3491 Posted May 19, 2022 Thank you. We cleared something up - that is the device that satamap sees attached to your virtual SATA controller is the virtual CD-ROM. I'll have to code that out. I've loaded Proxmox on a VM and will work on a solution. 1 Quote Link to comment Share on other sites More sharing options...
phone guy Posted May 19, 2022 Share #3492 Posted May 19, 2022 2 minutes ago, flyride said: Thank you. We cleared something up - that is the device that satamap sees attached to your virtual SATA controller is the virtual CD-ROM. I'll have to code that out. I've loaded Proxmox on a VM and will work on a solution. Excellent. I can't wait to try it! Quote Link to comment Share on other sites More sharing options...
naan Posted May 19, 2022 Share #3493 Posted May 19, 2022 Hi, Why the 6.2.4 is not available ? Quote Link to comment Share on other sites More sharing options...
phone guy Posted May 19, 2022 Share #3494 Posted May 19, 2022 20 hours ago, Bullseye said: Ok i have last question, i have my old J3455 NAS with 6.2.3 Update3 Juns Loader 918+ (CPU is apollo lake), if i want update that system to 7.1 what i should do to not lost all of my data and config (anyway i make full backup on external disk) ? First update system to latest version from DSM and restart, then take off my USB and burn tinycore-redpill and build for latest 7.1 918+ wih my old SN that i have on 6.2.3 JUNs ? First, always make a backup of your data because you never know! be safe and backup data before starting to be safe. You should be able to make new loader for bare metal (GUIDE) Doesn't matter if you use same serial or not. It should not matter. After you successfully make new loader with TCRP for 42661 (DSM7.1) you should see option to migrate disks when you load your dsm page in browser. Just select your migration option and install dsm from .pat downloaded directly from synology web site of whichever platform you build new 7.1 loader for. (DS918 if you choose that platform) and thats it. Good Luck. Quote Link to comment Share on other sites More sharing options...
phone guy Posted May 19, 2022 Share #3495 Posted May 19, 2022 9 minutes ago, naan said: Hi, Why the 6.2.4 is not available ? Most everybody wants to migrate to newest DSM7.x platforms now Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted May 19, 2022 Share #3496 Posted May 19, 2022 (edited) 1 hour ago, phone guy said: Most everybody wants to migrate to newest DSM7.x platforms now Actually, that topic was also for discussion of DSM 6.2.4. Recently, it has become a topic for discussion of DSM 7. Edited May 19, 2022 by Peter Suh Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted May 19, 2022 Share #3497 Posted May 19, 2022 (edited) Users who want to stay on DSM 6.2.4 may be afraid that what works well in DSM 6 may not work in DSM 7. Jun Loader and RedPill may experience difficulties because there is a slight difference in the SataportMap setting. And, I think that this part may be a barrier because a little knowledge of Linux, which was not required in Jun loader, may be required in Redpill. However, as convenient and easily accessible tools such as Tinycore RedPill have been developed and provided, I believe this can be offset. Edited May 19, 2022 by Peter Suh Quote Link to comment Share on other sites More sharing options...
Brunox Posted May 19, 2022 Share #3498 Posted May 19, 2022 Today I tried again to build a DS3622xs+ 7.0.1-42218 loader with Tc 0.7.1.5 (broadwellnk-7.0.1-42218-JUN) The build process runs without any problems on my test system, if I boot from RedPill DS3622xs+ 7.0.1-42218 (USB, Verbose) I can install the *pat file, but after a restart it says restore every time, I can't get any further! If I boot from Yet Anoter Jun`s Mod x RedPill……..(USB, Verbos) no network connection is established at all, I don’t get a link to my switch and the Synology is not found in the Synology Assistant either. The test system that I use always works perfectly and with e.g. TC 0.7.1.0 everything worked perfectly. I have already built a good 50 different loaders with it and have never had any problems with it. What's been wrong lately? Quote Link to comment Share on other sites More sharing options...
Bullseye Posted May 19, 2022 Share #3499 Posted May 19, 2022 3 hours ago, phone guy said: First, always make a backup of your data because you never know! be safe and backup data before starting to be safe. You should be able to make new loader for bare metal (GUIDE) Doesn't matter if you use same serial or not. It should not matter. After you successfully make new loader with TCRP for 42661 (DSM7.1) you should see option to migrate disks when you load your dsm page in browser. Just select your migration option and install dsm from .pat downloaded directly from synology web site of whichever platform you build new 7.1 loader for. (DS918 if you choose that platform) and thats it. Good Luck. I always have backup on minimum 2 HDDs Quote Link to comment Share on other sites More sharing options...
pocopico Posted May 19, 2022 Author Share #3500 Posted May 19, 2022 (edited) 6 hours ago, flyride said: Just to assuage my curiosity, run this when you have a moment - at this point I'm betting that it is just a kernel stub and not an actual device, but to see it mapped to Class 106 is odd (on all my systems it doesn't show a class). The creation of these two Marvell SATA controllers are part of the redpill magic. 0001:09:00.0 SATA controller [0106]: Marvell Technology Group Ltd. 88SE9235 PCIe 2.0 x2 4-port SATA 6 Gb/s Controller [1b4b:9235] (rev 11) 0001:0c:00.0 SATA controller [0106]: Marvell Technology Group Ltd. 88SE9235 PCIe 2.0 x2 4-port SATA 6 Gb/s Controller [1b4b:9235] (rev 11) Its on all redpill systems. Have a look : https://github.com/RedPill-TTG/redpill-lkm/blob/master/shim/pci_shim.c and https://github.com/RedPill-TTG/redpill-lkm/blob/master/config/platforms.h Edited May 19, 2022 by pocopico 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.