pocopico Posted January 19, 2022 Author Share #376 Posted January 19, 2022 2 minutes ago, Kaneske said: I have been happy to early… @pocopico Unfortunately my Install broke after playing with SATAportMap and DiskIdMap. Resetted all drives and was able to get to 6.2.3 again…as before. But installing 7.0.1 the same way isn’t possible, I can do what I want and tried everything to get my NAS recognized by find.syno… …but it is not seen. Compiled the TinyCore from scratch with ext add bromolow-7.0.1-42218 mpt2sas (link) and it’s been added. Hmmm…what to do now? the Build Command gets a lot of extensions by itself (mpt3sas for example)…can I exclude that? Maybe there’s a panic when mpt3 loads? You can remove the modules.alias.json file and it will be recreated. This way the wrong extension resolution will be solved. Now as for the SataPortMap and DiskIdxMap you have to try multiple settings and see how it goes for you. Can you send an lspci -nnq ? Quote Link to comment Share on other sites More sharing options...
Unregistrado Posted January 19, 2022 Share #377 Posted January 19, 2022 7 minutes ago, Kaneske said: I have been happy to early… @pocopico Unfortunately my Install broke after playing with SATAportMap and DiskIdMap. Resetted all drives and was able to get to 6.2.3 again…as before. But installing 7.0.1 the same way isn’t possible, I can do what I want and tried everything to get my NAS recognized by find.syno… …but it is not seen. Compiled the TinyCore from scratch with ext add bromolow-7.0.1-42218 mpt2sas (link) and it’s been added. Hmmm…what to do now? the Build Command gets a lot of extensions by itself (mpt3sas for example)…can I exclude that? Maybe there’s a panic when mpt3 loads? Weird as i just did the same. Some fiddling with sataportmap and diskidmap without any problem. Real weird because i believed that the DSM installation was written to a partition on every hard drive. And i also have them both mpt2sas and mpt3sas. Quote Link to comment Share on other sites More sharing options...
Kaneske Posted January 19, 2022 Share #378 Posted January 19, 2022 (edited) Will try in the evening, thanks for quick reply. lspci -nnq will be posted asap I’m at the Server. my thoughts about SATAPortMap an DiskIdxMap is: vmware has a Controller (tinyCore is on) Two LSI HBA with each 8 Ports sum 12 Disks (8+4) so I got thee Controllers: one with 1 Port (VMware) and two with 8 Port (LSI): SataPortMap: 188 To count them up: DiskIdxMap: 100800 or am I wrong? For debugging: in VMWare I can add an SerialPort, read that this Ports give Information about the Boot Process. How can I monitor it? Sorry totally new in this. Edited January 19, 2022 by Kaneske Quote Link to comment Share on other sites More sharing options...
Unregistrado Posted January 19, 2022 Share #379 Posted January 19, 2022 20 hours ago, Unregistrado said: Great job!!!!!! I am installing now and harddrives are already found. I just tested on a 3615. Installation went fast and without problems. Will test on 918 if this gives me also a good result. Tested with the ds918+ and this one doesn't find any harddrive with mpt2sas and mpt3sas. Quote Link to comment Share on other sites More sharing options...
Aigor Posted January 19, 2022 Share #380 Posted January 19, 2022 24 minutes ago, Kaneske said: For debugging: in VMWare I can add an SerialPort, read that this Ports give Information about the Boot Process. How can I monitor it? Sorry totally new in this. Vmware what? esxi is different than Workstation in workstation you have to add serial port and redirect output to a text file in esxi you have to add a port, setup as network pipe with like telnet://8765 simply telnetting on esxi ip and port configured, you can view serial port Quote Link to comment Share on other sites More sharing options...
Kaneske Posted January 19, 2022 Share #381 Posted January 19, 2022 I’m on ESXI 7 @Aigor Quote Link to comment Share on other sites More sharing options...
Aigor Posted January 19, 2022 Share #382 Posted January 19, 2022 7 minutes ago, Kaneske said: I’m on ESXI 7 @Aigor So you have to add serial port as network pipe Quote Link to comment Share on other sites More sharing options...
Unregistrado Posted January 19, 2022 Share #383 Posted January 19, 2022 I find this explanation logical so i will test this evening. Quote Link to comment Share on other sites More sharing options...
pocopico Posted January 19, 2022 Author Share #384 Posted January 19, 2022 1 hour ago, Kaneske said: Will try in the evening, thanks for quick reply. lspci -nnq will be posted asap I’m at the Server. my thoughts about SATAPortMap an DiskIdxMap is: vmware has a Controller (tinyCore is on) Two LSI HBA with each 8 Ports sum 12 Disks (8+4) so I got thee Controllers: one with 1 Port (VMware) and two with 8 Port (LSI): SataPortMap: 188 To count them up: DiskIdxMap: 100800 or am I wrong? For debugging: in VMWare I can add an SerialPort, read that this Ports give Information about the Boot Process. How can I monitor it? Sorry totally new in this. I Assume that is correct if you dont have any other controller. Thats the reason i would like to see the lspci -nnq output Quote Link to comment Share on other sites More sharing options...
Kaneske Posted January 19, 2022 Share #385 Posted January 19, 2022 (edited) I’m totally interested to get this solved and understand this. will report and come back with lspci -nnq output. EDIT: got it here on mobile, the one of the 6.2.3 install… @pocopico lspci -nnq 6.2.3.rtf Edited January 19, 2022 by Kaneske Quote Link to comment Share on other sites More sharing options...
Unregistrado Posted January 19, 2022 Share #386 Posted January 19, 2022 1 hour ago, Kaneske said: Will try in the evening, thanks for quick reply. lspci -nnq will be posted asap I’m at the Server. my thoughts about SATAPortMap an DiskIdxMap is: vmware has a Controller (tinyCore is on) Two LSI HBA with each 8 Ports sum 12 Disks (8+4) so I got thee Controllers: one with 1 Port (VMware) and two with 8 Port (LSI): SataPortMap: 188 To count them up: DiskIdxMap: 100800 or am I wrong? For debugging: in VMWare I can add an SerialPort, read that this Ports give Information about the Boot Process. How can I monitor it? Sorry totally new in this. Sataportmap first controller has 1 disk (synoboot) make this one invisible by making it the 17 disk so diskidxmap is 10 (hexadeximal disk with number 16 also counting disk 0). Second controller has (sataportmap) 8 disks and the first disk of this controller is disk number 9 (so diskidxmap is 08). Third controller has also (sataportmap) 8 disks and the first disk should start on number 0 (00 as diskidxmap). The question is which controller comes first? Or am i wrong? 1 Quote Link to comment Share on other sites More sharing options...
Kaneske Posted January 19, 2022 Share #387 Posted January 19, 2022 Jepp that’s my thoughts too. I read that the controller Syno Boots from comes first… Quote Link to comment Share on other sites More sharing options...
pocopico Posted January 19, 2022 Author Share #388 Posted January 19, 2022 (edited) 2 hours ago, Unregistrado said: Sataportmap first controller has 1 disk (synoboot) make this one invisible by making it the 17 disk so diskidxmap is 10 (hexadeximal disk with number 16 also counting disk 0). Second controller has (sataportmap) 8 disks and the first disk of this controller is disk number 9 (so diskidxmap is 08). Third controller has also (sataportmap) 8 disks and the first disk should start on number 0 (00 as diskidxmap). The question is which controller comes first? Or am i wrong? For VMware its a but confusing. In my case and on many test VMs that i have SATA0:0 is always on PCI 02:04.0 and SATA 1:0 is on PCI 02.01.0 Having the following set : dmesg |grep -ie "Index Map" -ie "Port Map" [ 0.000000] Disk Index Map: 001008 [ 0.000000] Sata Port Map: 818 i get the following disks : ./lsscsi [0:0:0:0] disk VMware Virtual SATA Hard Drive 0001 /dev/sda --------> SATA 1:0 , Data disk 1 [8:0:0:0] disk SATADOM- TYPE D 3SE 0001 /dev/synoboot ----------> Synoboot [9:0:0:0] disk VMware, VMware Virtual S 1.0 /dev/sdj ---------------> SCSI DISK 1 So counting the lspci -nnq output below, i conclude that the SATA devices come first on the list sorted by PCI bus and then the SCSI and SAS devices come next. ----------------------------- lspci -nnq | grep -ie SATA -ie SCSI -ie SAS ----------------------- 0000:00:10.0 SCSI storage controller [0100]: Broadcom / LSI 53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI [1000:0030] (rev 01) --> SCSI 0 0000:02:01.0 SATA controller [0106]: VMware SATA AHCI controller [15ad:07e0] --> SATA 1:0 0000:02:04.0 SATA controller [0106]: VMware SATA AHCI controller [15ad:07e0] --> SATA 0:0 0001:01:00.0 SATA controller [0106]: Marvell Technology Group Ltd. 88SE9215 PCIe 2.0 x1 4-port SATA 6 Gb/s Controller [1b4b:9215] (rev 11) ----> Redpill FAKE PCI devices 0001:02:00.0 SATA controller [0106]: Marvell Technology Group Ltd. 88SE9215 PCIe 2.0 x1 4-port SATA 6 Gb/s Controller [1b4b:9215] (rev 11)----> Redpill FAKE PCI devices 0001:08: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)----> Redpill FAKE PCI devices ------------------------------------------------------------------------------------------------- So with my settings Sata Port Map: 818 Disk Index Map: 001008 i get the following when i run lsscsi inside DSM. [0:0:0:0] disk VMware Virtual SATA Hard Drive 0001 /dev/sda [8:0:0:0] disk SATADOM- TYPE D 3SE 0001 /dev/synoboot [9:0:0:0] disk VMware, VMware Virtual S 1.0 /dev/sdj 8 disks for controller 02.01.0 SATA 1:0 --> Disk starting at 00 sda (1st disk) 1 disk for controller 02.04.0 SATA 0:0 --> Disk starting at 10 hex 8 disks for controller 00.10.0 SCSI 0 --> Disk starting at 08 sdj And that matches the output of lsscsi -Hv as well. sh-4.4# ./lsscsi -Hv |grep devices device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:01.0/ata1/host0 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:01.0/ata2/host1 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:01.0/ata3/host2 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:01.0/ata4/host3 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:01.0/ata5/host4 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:01.0/ata6/host5 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:01.0/ata7/host6 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:01.0/ata8/host7 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata9/host8 device dir: /sys/devices/pci0000:00/0000:00:10.0/host9 ------------------------------------------------------------ Same system with SataPortMap=1 and DiskIdxMap=00, also proves that SataPortMap acts also as a limit to the number of available ports. So if you set it wrong you might leave some disks outside. ./lsscsi -Hv |grep dev device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:01.0/ata1/host0 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata2/host1 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata3/host2 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata4/host3 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata5/host4 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata6/host5 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata7/host6 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata8/host7 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata9/host8 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata10/host9 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata11/host10 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata12/host11 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata13/host12 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata14/host13 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata15/host14 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata16/host15 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata17/host16 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata18/host17 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata19/host18 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata20/host19 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata21/host20 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata22/host21 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata23/host22 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata24/host23 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata25/host24 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata26/host25 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata27/host26 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata28/host27 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata29/host28 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata30/host29 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata31/host30 device dir: /sys/devices/pci0000:00/0000:00:10.0/host31 Edited January 19, 2022 by pocopico 2 Quote Link to comment Share on other sites More sharing options...
Kaneske Posted January 19, 2022 Share #389 Posted January 19, 2022 (edited) So, got the Serial output of a fresh TinyCore Image, trying to boot up and install… …end of the Lines say: fixing recursive fault but reboot is needed …what to do now? What´s really confusing: i changed nothing to the Version, that booted up yesterday! @pocopico is there something new in the Package, that can cause my Problem? Edited January 19, 2022 by Kaneske Quote Link to comment Share on other sites More sharing options...
Unregistrado Posted January 19, 2022 Share #390 Posted January 19, 2022 2 hours ago, pocopico said: For VMware its a but confusing. In my case and on many test VMs that i have SATA0:0 is always on PCI 02:04.0 and SATA 1:0 is on PCI 02.01.0 Having the following set : dmesg |grep -ie "Index Map" -ie "Port Map" [ 0.000000] Disk Index Map: 001008 [ 0.000000] Sata Port Map: 818 i get the following disks : ./lsscsi [0:0:0:0] disk VMware Virtual SATA Hard Drive 0001 /dev/sda --------> SATA 1:0 , Data disk 1 [8:0:0:0] disk SATADOM- TYPE D 3SE 0001 /dev/synoboot ----------> Synoboot [9:0:0:0] disk VMware, VMware Virtual S 1.0 /dev/sdj ---------------> SCSI DISK 1 So counting the lspci -nnq output below, i conclude that the SATA devices come first on the list sorted by PCI bus and then the SCSI and SAS devices come next. ----------------------------- lspci -nnq | grep -ie SATA -ie SCSI -ie SAS ----------------------- 0000:00:10.0 SCSI storage controller [0100]: Broadcom / LSI 53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI [1000:0030] (rev 01) --> SCSI 0 0000:02:01.0 SATA controller [0106]: VMware SATA AHCI controller [15ad:07e0] --> SATA 1:0 0000:02:04.0 SATA controller [0106]: VMware SATA AHCI controller [15ad:07e0] --> SATA 0:0 0001:01:00.0 SATA controller [0106]: Marvell Technology Group Ltd. 88SE9215 PCIe 2.0 x1 4-port SATA 6 Gb/s Controller [1b4b:9215] (rev 11) ----> Redpill FAKE PCI devices 0001:02:00.0 SATA controller [0106]: Marvell Technology Group Ltd. 88SE9215 PCIe 2.0 x1 4-port SATA 6 Gb/s Controller [1b4b:9215] (rev 11)----> Redpill FAKE PCI devices 0001:08: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)----> Redpill FAKE PCI devices ------------------------------------------------------------------------------------------------- So with my settings Sata Port Map: 818 Disk Index Map: 001008 i get the following when i run lsscsi inside DSM. [0:0:0:0] disk VMware Virtual SATA Hard Drive 0001 /dev/sda [8:0:0:0] disk SATADOM- TYPE D 3SE 0001 /dev/synoboot [9:0:0:0] disk VMware, VMware Virtual S 1.0 /dev/sdj 8 disks for controller 02.01.0 SATA 1:0 --> Disk starting at 00 sda (1st disk) 1 disk for controller 02.04.0 SATA 0:0 --> Disk starting at 10 hex 8 disks for controller 00.10.0 SCSI 0 --> Disk starting at 08 sdj And that matches the output of lsscsi -Hv as well. sh-4.4# ./lsscsi -Hv |grep devices device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:01.0/ata1/host0 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:01.0/ata2/host1 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:01.0/ata3/host2 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:01.0/ata4/host3 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:01.0/ata5/host4 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:01.0/ata6/host5 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:01.0/ata7/host6 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:01.0/ata8/host7 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata9/host8 device dir: /sys/devices/pci0000:00/0000:00:10.0/host9 ------------------------------------------------------------ Same system with SataPortMap=1 and DiskIdxMap=00, also proves that SataPortMap acts also as a limit to the number of available ports. So if you set it wrong you might leave some disks outside. ./lsscsi -Hv |grep dev device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:01.0/ata1/host0 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata2/host1 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata3/host2 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata4/host3 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata5/host4 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata6/host5 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata7/host6 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata8/host7 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata9/host8 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata10/host9 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata11/host10 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata12/host11 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata13/host12 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata14/host13 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata15/host14 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata16/host15 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata17/host16 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata18/host17 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata19/host18 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata20/host19 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata21/host20 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata22/host21 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata23/host22 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata24/host23 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata25/host24 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata26/host25 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata27/host26 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata28/host27 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata29/host28 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata30/host29 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata31/host30 device dir: /sys/devices/pci0000:00/0000:00:10.0/host31 Pocopico thank you for the effort you put in. This will help a lot of people to understand values needed for sataportmap and diskidxmap. 1 Quote Link to comment Share on other sites More sharing options...
killseeker Posted January 19, 2022 Share #391 Posted January 19, 2022 (edited) Really appreciate all the information you guys have posted over the last few hours. I've been wracking my brain over my test system. Its a basic system with 1 Sata Controller and 6 Sata Ports. I have 2 disks connected to the sata controller and my USB Thumb drive The whole time I've been using sataportmap=61 with an sataidxmap=0006 The system will boot to the installer, but constantly give me an error on disks 2,3,4,6 message. logging in via telnet (thanks for that tip to run: http://IPADDRESS:5000/webman/start_telnet.cgi - so amazing) , I could see my drives were still being detected, but it was giving me the error on the non connected drives. So that made me think I need to remove them from the sataidxmap (only counting the number of drives connected to the controllers) dmesg |grep sd [ 0.000000] ACPI: SSDT 0x00000000DD16F460 03493 (v01 SaSsdt SaSsdt 00003000 INTL 20091112) [ 1.540586] sd 0:0:0:0: [sda] 7814037168 512-byte logical blocks: (4.00 TB/3.63 TiB) [ 1.544529] sd 1:0:0:0: [sdb] 7814037168 512-byte logical blocks: (4.00 TB/3.63 TiB) [ 1.544530] sd 1:0:0:0: [sdb] 4096-byte physical blocks [ 1.544558] sd 1:0:0:0: [sdb] Write Protect is off [ 1.544559] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00 [ 1.544572] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 1.588987] sd 0:0:0:0: [sda] 4096-byte physical blocks [ 1.594283] sd 0:0:0:0: [sda] Write Protect is off [ 1.599081] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [ 1.604159] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 1.604214] sdb: sdb1 sdb2 sdb5 [ 1.604620] sd 1:0:0:0: [sdb] Attached SCSI disk [ 1.689131] sda: sda1 sda2 sda5 [ 1.692694] sd 0:0:0:0: [sda] Attached SCSI disk [ 20.320275] sd 2:0:0:0: [synoboot] 30031872 512-byte logical blocks: (15.3 GB/14.3 GiB) [ 20.328828] sd 2:0:0:0: [synoboot] Write Protect is off [ 20.334054] sd 2:0:0:0: [synoboot] Mode Sense: 43 00 00 00 [ 20.339787] sd 2:0:0:0: [synoboot] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [ 20.357773] sd 2:0:0:0: [synoboot] Attached SCSI removable disk So after trying many other different configurations, I tried using: sataportmap=61 and sataidxmap=0002 EG: 2 disks starting at 00 on the first controller, and 1 USB starting at 02 = 0002 BAM It worked! it detected and installed DSM 7.0 I do have a system partition failed message, but otherwise my 2 disk array is operational. Which is easily fixed. Is this the correct way to assign the sataidxmaps? I thought it needed to include all possible numbers of drives which could eventually be connected to the controllers. All night I thought I needed to use 0006 and above. Its 2:20am now and I'm pretty tired, hopefully this might help someone or be some useful findings. IF you want some other dumps from the test NAS let me know. Edited January 19, 2022 by killseeker 1 Quote Link to comment Share on other sites More sharing options...
Kaneske Posted January 19, 2022 Share #392 Posted January 19, 2022 Yes, that helps. I think I got that. pocopico thanks for your Time and Help. I am stuck. Can’t get find.synology.com show my rig anymore…no chance tried everything… Quote Link to comment Share on other sites More sharing options...
Invaliduser Posted January 19, 2022 Share #393 Posted January 19, 2022 12 minutes ago, Kaneske said: Yes, that helps. I think I got that. pocopico thanks for your Time and Help. I am stuck. Can’t get find.synology.com show my rig anymore…no chance tried everything… If you are able to connect via serial, you will see the IP Address being assigned. Quote Link to comment Share on other sites More sharing options...
Kaneske Posted January 19, 2022 Share #394 Posted January 19, 2022 (edited) There is none assigned. It ends with the Notification (Serial Output): fixing recursive fault but reboot is needed See attachment serial.rtf Edited January 19, 2022 by Kaneske Quote Link to comment Share on other sites More sharing options...
kiberboi Posted January 19, 2022 Share #395 Posted January 19, 2022 Installation is successfull on I3 2nd gen bare metal but the nas cannot be found. Do you know what might be the issue here? Quote Link to comment Share on other sites More sharing options...
pocopico Posted January 19, 2022 Author Share #396 Posted January 19, 2022 3 hours ago, Kaneske said: There is none assigned. It ends with the Notification (Serial Output): fixing recursive fault but reboot is needed See attachment serial.rtf 55.56 kB · 7 downloads You are getting a system panic. It’s equivalent to blue screen on windows. Can you remove ixgbe driver and try again ? Quote Link to comment Share on other sites More sharing options...
Kaneske Posted January 19, 2022 Share #397 Posted January 19, 2022 (edited) 8 hours ago, pocopico said: I Assume that is correct if you dont have any other controller. Thats the reason i would like to see the lspci -nnq output Here´s the 7.0.1 lspci -nnq finally got it up again...dont ask me how...everything from scratch... ...this time intel driver wasn't added automaticly as before it went lspci -nnq 7.0.1.rtf grep grep sd.rtf Edited January 19, 2022 by Kaneske 1 Quote Link to comment Share on other sites More sharing options...
Kaneske Posted January 19, 2022 Share #398 Posted January 19, 2022 1 hour ago, pocopico said: Can you remove ixgbe driver and try again ? HOW??? Quote Link to comment Share on other sites More sharing options...
Dvalin21 Posted January 19, 2022 Share #399 Posted January 19, 2022 Hey, what is the best way to pull the pat file from the cache folder? I've done the build, backed up everything and then placed the usb at another computer to extract it. The cache folder is not there. Quote Link to comment Share on other sites More sharing options...
Invaliduser Posted January 19, 2022 Share #400 Posted January 19, 2022 23 minutes ago, Dvalin21 said: Hey, what is the best way to pull the pat file from the cache folder? I've done the build, backed up everything and then placed the usb at another computer to extract it. The cache folder is not there. GUI - use Winscp, filezilla, or similar to extract immediately after building. Or something like sshfs via command line. 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.