pocopico 554 Posted October 16, 2021 Share Posted October 16, 2021 (edited) You may also use INSTALL_MOD_STRIP=1 make flag while installing but IDK sometimes it strips sometimes it doesn’t. I’ll also try your solution and update you if it works or not Edited October 16, 2021 by pocopico Quote Link to post Share on other sites
donxu 0 Posted October 16, 2021 Share Posted October 16, 2021 I extend the capacity of boot-image-template.img.gz, now the total is 256M, 177M for the 1st partition and 75M for the 2nd partition. https://github.com/Donxu82/redpill-load/tree/develop/ext It works fine. Anyone who wants have a try, edit the global_config.json as follows: "redpill_load": { "source_url": "https://github.com/Donxu82/redpill-load.git", "branch": "develop" Quote Link to post Share on other sites
pocopico 554 Posted October 16, 2021 Share Posted October 16, 2021 (edited) For everyone that customises the boot-image-template.img please beware that the image detection mechanism for SATAdom in RP code will seek for images smaller than 1GB. This might change so I would just stick to the standard template until beta release. Edited October 16, 2021 by pocopico 2 Quote Link to post Share on other sites
snowfox 4 Posted October 16, 2021 Share Posted October 16, 2021 3 hours ago, haydibe said: A VPN is not required. With the level of provided details: I have no idea. I can say that "auto" will not work if you require a http_proxy or https_proxy to access the internet (which almost no one uses in their home environment). You can also try to check if things remedy after restarting the docker service (it was the solution to a couple of docker related problems in this thread). thank you. let me try again. Quote Link to post Share on other sites
snowfox 4 Posted October 16, 2021 Share Posted October 16, 2021 4 hours ago, haydibe said: A VPN is not required. With the level of provided details: I have no idea. I can say that "auto" will not work if you require a http_proxy or https_proxy to access the internet (which almost no one uses in their home environment). You can also try to check if things remedy after restarting the docker service (it was the solution to a couple of docker related problems in this thread). when i run ./redpill_tool_chain.sh auto apollolake-7.0.1-42218，this error occurs： curl: (7) Failed to connect to raw.githubusercontent.com port 443: Connection refused [!] Failed to download https://raw.githubusercontent.com/tossp/rp-ext/master/redpill-boot-wait/rpext-index.json to /opt/redpill-load/custom/extensions/_new_ext_index.tmp_json *** Process will exit *** [!] Failed to add "https://raw.githubusercontent.com/tossp/rp-ext/master/redpill-boot-wait/rpext-index.json" as an extension: , *** Process will exit *** [!] Failed to install thethorgroup.boot-wait bundled extension - see errors above *** Process will exit *** Quote Link to post Share on other sites
tcs 7 Posted October 16, 2021 Share Posted October 16, 2021 16 minutes ago, snowfox said: when i run ./redpill_tool_chain.sh auto apollolake-7.0.1-42218，this error occurs： curl: (7) Failed to connect to raw.githubusercontent.com port 443: Connection refused [!] Failed to download https://raw.githubusercontent.com/tossp/rp-ext/master/redpill-boot-wait/rpext-index.json to /opt/redpill-load/custom/extensions/_new_ext_index.tmp_json *** Process will exit *** [!] Failed to add "https://raw.githubusercontent.com/tossp/rp-ext/master/redpill-boot-wait/rpext-index.json" as an extension: , *** Process will exit *** [!] Failed to install thethorgroup.boot-wait bundled extension - see errors above *** Process will exit *** Do you have a firewall running on the box you have the container on? That’s telling you it can’t make an https connection to GitHub. Can you get to the address from a web browser? Either you’re in a country that is blocking GitHub entirely or something local to your system is doing it. Quote Link to post Share on other sites
haydibe 310 Posted October 16, 2021 Share Posted October 16, 2021 23 minutes ago, snowfox said: when i run ./redpill_tool_chain.sh auto apollolake-7.0.1-42218，this error occurs： curl: (7) Failed to connect to raw.githubusercontent.com port 443: Connection refused [!] Failed to download https://raw.githubusercontent.com/tossp/rp-ext/master/redpill-boot-wait/rpext-index.json to /opt/redpill-load/custom/extensions/_new_ext_index.tmp_json *** Process will exit *** [!] Failed to add "https://raw.githubusercontent.com/tossp/rp-ext/master/redpill-boot-wait/rpext-index.json" as an extension: , *** Process will exit *** [!] Failed to install thethorgroup.boot-wait bundled extension - see errors above *** Process will exit *** I am not sure what is wrong with trying to download the rpext-index.json from tossp's repository. Please always try first if the offical TTG build configs work, in order to isolate if there is a generall problem, or the problem is introduced due to using 3rd part repo. Also, It is kind of confusing that the error message of your last post is not present in this error message. Quote Link to post Share on other sites
snowfox 4 Posted October 16, 2021 Share Posted October 16, 2021 26 minutes ago, haydibe said: I am not sure what is wrong with trying to download the rpext-index.json from tossp's repository. Please always try first if the offical TTG build configs work, in order to isolate if there is a generall problem, or the problem is introduced due to using 3rd part repo. Also, It is kind of confusing that the error message of your last post is not present in this error message. I repeatedly run ./redpill_tool_chain.sh auto apollolake-7.0.1-42218, and finally the first error does not appear, but the second error appears. Quote Link to post Share on other sites
snowfox 4 Posted October 16, 2021 Share Posted October 16, 2021 44 minutes ago, tcs said: Do you have a firewall running on the box you have the container on? That’s telling you it can’t make an https connection to GitHub. Can you get to the address from a web browser? Either you’re in a country that is blocking GitHub entirely or something local to your system is doing it. no firewall, ping https://raw.githubusercontent.com is ok, and can be seen in the browser. Quote Link to post Share on other sites
haydibe 310 Posted October 16, 2021 Share Posted October 16, 2021 If you run Docker Desktop or docker in WSL2, try to shutdown the WSL2 base vm with `wsl --shutdown` and retry again. If it's another Linux distro try to restart the docker engine with `service docker restart`. Appearently you are not using Synology Docker, as you showed that a link on the host(?) works without issues. Appart from that: No idea. Not reproducable for me. Quote Link to post Share on other sites
snowfox 4 Posted October 16, 2021 Share Posted October 16, 2021 11 minutes ago, haydibe said: If you run Docker Desktop or docker in WSL2, try to shutdown the WSL2 base vm with `wsl --shutdown` and retry again. If it's another Linux distro try to restart the docker engine with `service docker restart`. Appearently you are not using Synology Docker, as you showed that a link on the host(?) works without issues. Appart from that: No idea. Not reproducable for me. thank you again. I run docker in Ubuntu 20.04 in VMware Workstation in win10, not WSL2. Quote Link to post Share on other sites
tcs 7 Posted October 16, 2021 Share Posted October 16, 2021 3 minutes ago, snowfox said: thank you again. I run docker in Ubuntu 20.04 in VMware Workstation in win10, not WSL2. can you ping github from within the container? What happens when you manually curl the file from inside the container? Quote Link to post Share on other sites
lzxx 0 Posted October 16, 2021 Share Posted October 16, 2021 On 9/6/2021 at 9:40 AM, Orphée said: I added the vmxnet3.ko in /usr/lib/modules added in line 285 insmod /lib/modules/vmxnet3.ko But it does not seems to add it... Not loaded No network access if I do after with telnet : insmod /usr/lib/modules/vmxnet3.ko : # insmod vmxnet3.ko [ 379.994870] VMware vmxnet3 virtual NIC driver - version 1.1.30.0-k-NAPI [ 379.996016] vmxnet3 0000:03:00.0: # of Tx queues : 2, # of Rx queues : 2 [ 379.997886] vmxnet3 0000:03:00.0: irq 74 for MSI/MSI-X [ 379.998765] vmxnet3 0000:03:00.0: irq 75 for MSI/MSI-X [ 379.999805] vmxnet3 0000:03:00.0: irq 76 for MSI/MSI-X [ 380.001417] vmxnet3 0000:03:00.0 eth0: NIC Link is Up 10000 Mbps but can't activate dhcp # dhclient eth0 [ 439.463738] type=1400 audit(1630939202.680:8): apparmor="DENIED" operation="mknod" parent=13865 profile="/usr/sbin/dhclient" name="/var/db/dhclient.leases" pid=13866 comm="dhclient" requested_mask="c" denied_mask="c" fsuid=0 ouid=0 [ 439.467297] type=1400 audit(1630939202.684:9): apparmor="DENIED" operation="exec" parent=13866 profile="/usr/sbin/dhclient" name="/etc/dhclient/dhclient-script" pid=13867 comm="dhclient" requested_mask="x" denied_mask="x" fsuid=0 ouid=0 I wrote the following script (adapted from others) and put it in /usr/local/etc/rc.d folder, and then the vmxnet3 works well. You could modify the path variables and have a try. If you want to use dhcp instead of manual ip, just use synonet --dhcp ethX. #!/bin/sh MODULES_DIR="/usr/lib/modules" MODULES_START="vmxnet3.ko" MODULES_STOP="vmxnet3.ko" start_modules() { echo "--- Load modules ---" for i in $MODULES_START; do echo "Loading $i" insmod $MODULES_DIR/$i done ifconfig eth1 up synonet --manual eth1 192.168.211.2 255.255.255.0 } stop_modules() { echo "--- Unload modules ---" for i in $MODULES_STOP; do echo "Unloading $i" rmmod $MODULES_DIR/$i done } case "$1" in start) start_modules ;; stop) stop_modules ;; *) echo "usage: $0 { start | stop }" >&2 exit 1 ;; esac Quote Link to post Share on other sites
progressives 0 Posted October 16, 2021 Share Posted October 16, 2021 Is this the correct status of bootloader GRUB? Quote Link to post Share on other sites
ed_co 14 Posted October 16, 2021 Share Posted October 16, 2021 (edited) Looks very nice. When are you putting this project in the loader section? It looks like the first page is not edited since a long time. If there are new changes/features/updates/faqs/links to builds, should be great to have it edited in the first page (like version history/time-lined...). Is very hard to follow through that huge unorganized thread right now. Just my opinion. Such a great job! Thanks Edited October 16, 2021 by ed_co 3 Quote Link to post Share on other sites
messica 0 Posted October 17, 2021 Share Posted October 17, 2021 On 10/13/2021 at 7:06 PM, RedwinX said: Hey, Have a little pb with a baremetal. It boot correctly (918+ 7.0 redpill repo), status : not installed Install ok, reboot and then : status not installed... didn't have serial outpout. Any idea ? Have the same problem, have you solved it? Quote Link to post Share on other sites
RedwinX 37 Posted October 17, 2021 Share Posted October 17, 2021 (edited) 52 minutes ago, messica said: Have the same problem, have you solved it? internalportcfg="0xfff" in your user_config.json Edited October 17, 2021 by RedwinX Quote Link to post Share on other sites
progressives 0 Posted October 17, 2021 Share Posted October 17, 2021 How can you plant GRUB in partition 1 and make it possible to boot? If you create an image file with the loader now, it won't boot. Quote Link to post Share on other sites
pocopico 554 Posted October 17, 2021 Share Posted October 17, 2021 On 10/16/2021 at 1:01 PM, s2k7 said: you can try following command after compiling: # strip --strip-unneeded virtio.ko So far, only the strip --strip-debug works for the compiled modules. All other tries failed. So i have stripped the modules, recreated the extensions and push them again to the repository. You can try and let me know 1 Quote Link to post Share on other sites
pigr8 30 Posted October 17, 2021 Share Posted October 17, 2021 (edited) i made some tests with the 6.2.4 loader for ds3615xs, that is based on 3.10.105 like 6.2.3 so the kernel "should" be the same? using the stock mpt2sas.ko that comes with dsm the hba loads, all disks can be seen but still not more than 2tb and fdisk gives the same error "fdisk: device has more than 2^32 sectors, can't use all of them"... and the "want_idx 1 index N" spam error after every disk detect is still there. so i tried to load the mpt2sas.ko that comes with 6.2.3 currently in use with jun's loader DiskStation> insmod mpt2sas.ko [ 405.096449] mpt2sas: Unknown symbol syno_disk_start_time_set (err 0) insmod: can't insert 'mpt2sas.ko': unknown symbol in module, or unknown parameter so i guess that's a fail too.. last i tried to use the new @pocopico mpt2sas.ko compiled on v14.1 (240kb module or so), but on 6.2.4 it crashes Loading kmod #0 "mpt2sas.ko" for pocopico.mpt2sas (args: ) [ 2.836262] mpt2sas version 14.100.00.00 loaded [ 2.837953] scsi1 : Fusion MPT SAS Host [ 2.841747] mpt2sas0: 64 BIT PCI BUS DMA ADDRESSING SUPPORTED, total mem (6084704 kB) [ 2.843552] mpt2sas 0000:0b:00.0: irq 73 for MSI/MSI-X [ 2.844836] mpt2sas0-msix0: PCI-MSI-X enabled: IRQ 73 [ 2.846311] mpt2sas0: iomem(0x00000000fd3f0000), mapped(0xffffc90008160000), size(65536) [ 2.846815] mpt2sas0: ioport(0x0000000000005000), size(256) [ 2.962906] mpt2sas0: Allocated physical memory: size(7418 kB) [ 2.963909] mpt2sas0: Current Controller Queue Depth(3307), Max Controller Queue Depth(3432) [ 2.965323] mpt2sas0: Scatter Gather Elements per IO(128) [ 3.024478] mpt2sas0: LSISAS2008: FWVersion(16.00.00.00), ChipRevision(0x03), BiosVersion(00.00.00.00) [ 3.025410] mpt2sas0: Dell 6Gbps SAS HBA: Vendor(0x1000), Device(0x0072), SSVID(0x1028), SSDID(0x1F1C) [ 3.026746] mpt2sas0: Protocol=(Initiator,Target), Capabilities=(TLR,EEDP,Snapshot Buffer,Diag Trace Buffer,Task Set Full,NCQ) [ 3.028508] mpt2sas0: sending port enable !! [ 3.035735] mpt2sas0: host_add: handle(0x0001), sas_addr(0x590b11c027f7ff00), phys(8) [ 3.042340] scsi 1:0:0:0: Direct-Access WDC WD30EFRX-68EUZN0 0A82 PQ: 0 ANSI: 6 [ 3.044192] scsi 1:0:0:0: SATA: handle(0x0009), sas_addr(0x4433221100000000), phy(0), device_name(0x50014ee26320545e) [ 3.046965] scsi 1:0:0:0: SATA: enclosure_logical_id(0x590b11c027f7ff00), slot(3) [ 3.049091] scsi 1:0:0:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y) [ 3.050033] scsi 1:0:0:0: qdepth(32), tagged(1), simple(0), ordered(0), scsi_level(7), cmd_que(1) [ 3.052209] BUG: unable to handle kernel paging request at ffffffffa00cd238 [ 3.053086] IP: [<ffffffff8136d4f0>] syno_sata_pmp_read_emid+0x1f0/0x1f0 [ 3.053896] PGD 1810067 PUD 1811063 PMD 1b4946067 PTE 0 [ 3.054984] Oops: 0000 [#1] SMP [ 3.055004] Modules linked in: mpt2sas(OF+) usb_storage xhci_hcd uhci_hcd ehci_pci ehci_hcd usbcore usb_common [ 3.057984] CPU: 0 PID: 19 Comm: kworker/u4:1 Tainted: GF O 3.10.105 #25556 his mpt2sas.ko works ok for 7.0 and 7.0.1 (3.10.108) and does not have the "want_idx 1 index N" error while loading the disks on boot, but still not more than 2tb. Loading kmod #0 "mpt2sas.ko" for pocopico.mpt2sas (args: ) [ 1.999107] mpt2sas version 14.100.00.00 loaded [ 2.000670] scsi1 : Fusion MPT SAS Host [ 2.004494] mpt2sas0: 64 BIT PCI BUS DMA ADDRESSING SUPPORTED, total mem (6084496 kB) [ 2.005976] mpt2sas 0000:0b:00.0: irq 73 for MSI/MSI-X [ 2.007928] mpt2sas0-msix0: PCI-MSI-X enabled: IRQ 73 [ 2.008930] mpt2sas0: iomem(0x00000000fd3f0000), mapped(0xffffc90008360000), size(65536) [ 2.010764] mpt2sas0: ioport(0x0000000000005000), size(256) [ 2.025982] tsc: Refined TSC clocksource calibration: 2394.551 MHz [ 2.027356] Switching to clocksource tsc [ 2.128032] mpt2sas0: Allocated physical memory: size(7418 kB) [ 2.129031] mpt2sas0: Current Controller Queue Depth(3307), Max Controller Queue Depth(3432) [ 2.130888] mpt2sas0: Scatter Gather Elements per IO(128) [ 2.190638] mpt2sas0: LSISAS2008: FWVersion(16.00.00.00), ChipRevision(0x03), BiosVersion(00.00.00.00) [ 2.192069] mpt2sas0: Dell 6Gbps SAS HBA: Vendor(0x1000), Device(0x0072), SSVID(0x1028), SSDID(0x1F1C) [ 2.194285] mpt2sas0: Protocol=(Initiator,Target), Capabilities=(TLR,EEDP,Snapshot Buffer,Diag Trace Buffer,Task Set Full,NCQ) [ 2.198186] mpt2sas0: sending port enable !! [ 2.205992] mpt2sas0: host_add: handle(0x0001), sas_addr(0x590b11c027f7ff00), phys(8) [ 2.212685] scsi 1:0:0:0: Direct-Access WDC WD30EFRX-68EUZN0 0A82 PQ: 0 ANSI: 6 [ 2.214318] scsi 1:0:0:0: SATA: handle(0x0009), sas_addr(0x4433221100000000), phy(0), device_name(0x50014ee26320545e) [ 2.217098] scsi 1:0:0:0: SATA: enclosure_logical_id(0x590b11c027f7ff00), slot(3) [ 2.217308] scsi 1:0:0:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y) [ 2.218117] scsi 1:0:0:0: qdepth(32), tagged(1), simple(0), ordered(0), scsi_level(7), cmd_que(1) [ 2.219936] sd 1:0:0:0: [sdb] 5860533168 512-byte logical blocks: (3.00 TB/2.72 TiB) [ 2.221619] sd 1:0:0:0: [sdb] 4096-byte physical blocks [ 2.225891] sd 1:0:0:0: [sdb] Write Protect is off [ 2.227269] sd 1:0:0:0: [sdb] Mode Sense: 7f 00 10 08 [ 2.229265] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA [ 2.454299] mpt2sas0: port enable: SUCCESS :: Loading kernel modules from extensions ... [ OK ] :: Executing "on_boot" custom scripts ... Running "check-mpt2sas.sh" for pocopico.mpt2sas->on_boot Loading module MPT 2 SAS -> Module MPT 2 SAS loaded succesfully Ran "check-mpt2sas.sh" for pocopico.mpt2sas->on_boot - exit=0 Running "boot-wait.sh" for thethorgroup.boot-wait->on_boot Confirmed a valid-looking /dev/synoboot device Ran "boot-wait.sh" for thethorgroup.boot-wait->on_boot - exit=0 Running "load-builtin-sas.sh" for thethorgroup.sas-activator->on_boot Loading SAS controller(s) driver(s) Ran "load-builtin-sas.sh" for thethorgroup.sas-activator->on_boot - exit=0 DiskStation> fdisk -l Disk /dev/synoboot: 128 MB, 134217728 bytes, 262144 sectors 16 cylinders, 255 heads, 63 sectors/track Units: sectors of 1 * 512 = 512 bytes Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type /dev/synoboot1 0,32,33 6,62,56 2048 100351 98304 48.0M 83 Linux /dev/synoboot2 6,62,57 15,205,62 100352 253951 153600 75.0M 83 Linux /dev/synoboot3 15,205,63 16,81,1 253952 262143 8192 4096K 83 Linux fdisk: device has more than 2^32 sectors, can't use all of them Disk /dev/sdb: 2048 GB, 2199023255040 bytes, 4294967295 sectors 267349 cylinders, 255 heads, 63 sectors/track Units: sectors of 1 * 512 = 512 bytes Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type /dev/sdb1 0,0,1 1023,254,63 1 4294967295 4294967295 2047G ee EFI GPT fdisk: device has more than 2^32 sectors, can't use all of them Edited October 17, 2021 by pigr8 Quote Link to post Share on other sites
seanone 5 Posted October 18, 2021 Share Posted October 18, 2021 16 hours ago, pocopico said: So far, only the strip --strip-debug works for the compiled modules. All other tries failed. So i have stripped the modules, recreated the extensions and push them again to the repository. You can try and let me know Can you add asr-78165 and AQC107 driver to rp-ext please? Below is asr-78165 driver source: https://storage.microsemi.com/en-us/support/raid/sas_raid/asr-78165/ Quote Link to post Share on other sites
pocopico 554 Posted October 18, 2021 Share Posted October 18, 2021 4 hours ago, seanone said: Can you add asr-78165 and AQC107 driver to rp-ext please? Below is asr-78165 driver source: https://storage.microsemi.com/en-us/support/raid/sas_raid/asr-78165/ You can try : https://raw.githubusercontent.com/pocopico/rp-ext/master/aacraid/rpext-index.json and https://raw.githubusercontent.com/pocopico/rp-ext/master/atlantic/rpext-index.json Quote Link to post Share on other sites
xPalito93 0 Posted October 18, 2021 Share Posted October 18, 2021 (edited) Can somebody explain how to insert Drivers? I only played around with the v0.8-0.11 toolchain without using the ext-manager, so I only used the Build & Auto command. I'm trying to learn as much as possible but it's not that easy lol. I have a Fujitsu Server at work which i've been using to play around. It has a Fujitsu D2607-A21 GS2 SAS card in it, which has a LSI SAS 2008 chip on it. What would my steps be to create an image with those drivers in it? Can i do it with the 0.11 toolchain? I hope someone has time to guide me through it I forgot to add: I was able to create an image with 3615 on it, but it never finds any drives. That's the issue i'm facing and why i wanted to ask how to add drivers Edited October 18, 2021 by xPalito93 added details Quote Link to post Share on other sites
tcs 7 Posted October 18, 2021 Share Posted October 18, 2021 1 hour ago, xPalito93 said: Can somebody explain how to insert Drivers? I only played around with the v0.8-0.11 toolchain without using the ext-manager, so I only used the Build & Auto command. I'm trying to learn as much as possible but it's not that easy lol. I have a Fujitsu Server at work which i've been using to play around. It has a Fujitsu D2607-A21 GS2 SAS card in it, which has a LSI SAS 2008 chip on it. What would my steps be to create an image with those drivers in it? Can i do it with the 0.11 toolchain? I hope someone has time to guide me through it I forgot to add: I was able to create an image with 3615 on it, but it never finds any drives. That's the issue i'm facing and why i wanted to ask how to add drivers After you do redpill run, you go into redpill-load and edit bundled-exts.json to add whatever extensions you need. If you need more guidance than that, you should probably hold off running this until it's in a more stable state. Quote Link to post Share on other sites
pocopico 554 Posted October 18, 2021 Share Posted October 18, 2021 21 hours ago, pigr8 said: i made some tests with the 6.2.4 loader for ds3615xs, that is based on 3.10.105 like 6.2.3 so the kernel "should" be the same? using the stock mpt2sas.ko that comes with dsm the hba loads, all disks can be seen but still not more than 2tb and fdisk gives the same error "fdisk: device has more than 2^32 sectors, can't use all of them"... and the "want_idx 1 index N" spam error after every disk detect is still there. so i tried to load the mpt2sas.ko that comes with 6.2.3 currently in use with jun's loader DiskStation> insmod mpt2sas.ko [ 405.096449] mpt2sas: Unknown symbol syno_disk_start_time_set (err 0) insmod: can't insert 'mpt2sas.ko': unknown symbol in module, or unknown parameter so i guess that's a fail too.. last i tried to use the new @pocopico mpt2sas.ko compiled on v14.1 (240kb module or so), but on 6.2.4 it crashes Loading kmod #0 "mpt2sas.ko" for pocopico.mpt2sas (args: ) [ 2.836262] mpt2sas version 14.100.00.00 loaded [ 2.837953] scsi1 : Fusion MPT SAS Host [ 2.841747] mpt2sas0: 64 BIT PCI BUS DMA ADDRESSING SUPPORTED, total mem (6084704 kB) [ 2.843552] mpt2sas 0000:0b:00.0: irq 73 for MSI/MSI-X [ 2.844836] mpt2sas0-msix0: PCI-MSI-X enabled: IRQ 73 [ 2.846311] mpt2sas0: iomem(0x00000000fd3f0000), mapped(0xffffc90008160000), size(65536) [ 2.846815] mpt2sas0: ioport(0x0000000000005000), size(256) [ 2.962906] mpt2sas0: Allocated physical memory: size(7418 kB) [ 2.963909] mpt2sas0: Current Controller Queue Depth(3307), Max Controller Queue Depth(3432) [ 2.965323] mpt2sas0: Scatter Gather Elements per IO(128) [ 3.024478] mpt2sas0: LSISAS2008: FWVersion(16.00.00.00), ChipRevision(0x03), BiosVersion(00.00.00.00) [ 3.025410] mpt2sas0: Dell 6Gbps SAS HBA: Vendor(0x1000), Device(0x0072), SSVID(0x1028), SSDID(0x1F1C) [ 3.026746] mpt2sas0: Protocol=(Initiator,Target), Capabilities=(TLR,EEDP,Snapshot Buffer,Diag Trace Buffer,Task Set Full,NCQ) [ 3.028508] mpt2sas0: sending port enable !! [ 3.035735] mpt2sas0: host_add: handle(0x0001), sas_addr(0x590b11c027f7ff00), phys(8) [ 3.042340] scsi 1:0:0:0: Direct-Access WDC WD30EFRX-68EUZN0 0A82 PQ: 0 ANSI: 6 [ 3.044192] scsi 1:0:0:0: SATA: handle(0x0009), sas_addr(0x4433221100000000), phy(0), device_name(0x50014ee26320545e) [ 3.046965] scsi 1:0:0:0: SATA: enclosure_logical_id(0x590b11c027f7ff00), slot(3) [ 3.049091] scsi 1:0:0:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y) [ 3.050033] scsi 1:0:0:0: qdepth(32), tagged(1), simple(0), ordered(0), scsi_level(7), cmd_que(1) [ 3.052209] BUG: unable to handle kernel paging request at ffffffffa00cd238 [ 3.053086] IP: [<ffffffff8136d4f0>] syno_sata_pmp_read_emid+0x1f0/0x1f0 [ 3.053896] PGD 1810067 PUD 1811063 PMD 1b4946067 PTE 0 [ 3.054984] Oops: 0000 [#1] SMP [ 3.055004] Modules linked in: mpt2sas(OF+) usb_storage xhci_hcd uhci_hcd ehci_pci ehci_hcd usbcore usb_common [ 3.057984] CPU: 0 PID: 19 Comm: kworker/u4:1 Tainted: GF O 3.10.105 #25556 his mpt2sas.ko works ok for 7.0 and 7.0.1 (3.10.108) and does not have the "want_idx 1 index N" error while loading the disks on boot, but still not more than 2tb. Loading kmod #0 "mpt2sas.ko" for pocopico.mpt2sas (args: ) [ 1.999107] mpt2sas version 14.100.00.00 loaded [ 2.000670] scsi1 : Fusion MPT SAS Host [ 2.004494] mpt2sas0: 64 BIT PCI BUS DMA ADDRESSING SUPPORTED, total mem (6084496 kB) [ 2.005976] mpt2sas 0000:0b:00.0: irq 73 for MSI/MSI-X [ 2.007928] mpt2sas0-msix0: PCI-MSI-X enabled: IRQ 73 [ 2.008930] mpt2sas0: iomem(0x00000000fd3f0000), mapped(0xffffc90008360000), size(65536) [ 2.010764] mpt2sas0: ioport(0x0000000000005000), size(256) [ 2.025982] tsc: Refined TSC clocksource calibration: 2394.551 MHz [ 2.027356] Switching to clocksource tsc [ 2.128032] mpt2sas0: Allocated physical memory: size(7418 kB) [ 2.129031] mpt2sas0: Current Controller Queue Depth(3307), Max Controller Queue Depth(3432) [ 2.130888] mpt2sas0: Scatter Gather Elements per IO(128) [ 2.190638] mpt2sas0: LSISAS2008: FWVersion(16.00.00.00), ChipRevision(0x03), BiosVersion(00.00.00.00) [ 2.192069] mpt2sas0: Dell 6Gbps SAS HBA: Vendor(0x1000), Device(0x0072), SSVID(0x1028), SSDID(0x1F1C) [ 2.194285] mpt2sas0: Protocol=(Initiator,Target), Capabilities=(TLR,EEDP,Snapshot Buffer,Diag Trace Buffer,Task Set Full,NCQ) [ 2.198186] mpt2sas0: sending port enable !! [ 2.205992] mpt2sas0: host_add: handle(0x0001), sas_addr(0x590b11c027f7ff00), phys(8) [ 2.212685] scsi 1:0:0:0: Direct-Access WDC WD30EFRX-68EUZN0 0A82 PQ: 0 ANSI: 6 [ 2.214318] scsi 1:0:0:0: SATA: handle(0x0009), sas_addr(0x4433221100000000), phy(0), device_name(0x50014ee26320545e) [ 2.217098] scsi 1:0:0:0: SATA: enclosure_logical_id(0x590b11c027f7ff00), slot(3) [ 2.217308] scsi 1:0:0:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y) [ 2.218117] scsi 1:0:0:0: qdepth(32), tagged(1), simple(0), ordered(0), scsi_level(7), cmd_que(1) [ 2.219936] sd 1:0:0:0: [sdb] 5860533168 512-byte logical blocks: (3.00 TB/2.72 TiB) [ 2.221619] sd 1:0:0:0: [sdb] 4096-byte physical blocks [ 2.225891] sd 1:0:0:0: [sdb] Write Protect is off [ 2.227269] sd 1:0:0:0: [sdb] Mode Sense: 7f 00 10 08 [ 2.229265] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA [ 2.454299] mpt2sas0: port enable: SUCCESS :: Loading kernel modules from extensions ... [ OK ] :: Executing "on_boot" custom scripts ... Running "check-mpt2sas.sh" for pocopico.mpt2sas->on_boot Loading module MPT 2 SAS -> Module MPT 2 SAS loaded succesfully Ran "check-mpt2sas.sh" for pocopico.mpt2sas->on_boot - exit=0 Running "boot-wait.sh" for thethorgroup.boot-wait->on_boot Confirmed a valid-looking /dev/synoboot device Ran "boot-wait.sh" for thethorgroup.boot-wait->on_boot - exit=0 Running "load-builtin-sas.sh" for thethorgroup.sas-activator->on_boot Loading SAS controller(s) driver(s) Ran "load-builtin-sas.sh" for thethorgroup.sas-activator->on_boot - exit=0 DiskStation> fdisk -l Disk /dev/synoboot: 128 MB, 134217728 bytes, 262144 sectors 16 cylinders, 255 heads, 63 sectors/track Units: sectors of 1 * 512 = 512 bytes Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type /dev/synoboot1 0,32,33 6,62,56 2048 100351 98304 48.0M 83 Linux /dev/synoboot2 6,62,57 15,205,62 100352 253951 153600 75.0M 83 Linux /dev/synoboot3 15,205,63 16,81,1 253952 262143 8192 4096K 83 Linux fdisk: device has more than 2^32 sectors, can't use all of them Disk /dev/sdb: 2048 GB, 2199023255040 bytes, 4294967295 sectors 267349 cylinders, 255 heads, 63 sectors/track Units: sectors of 1 * 512 = 512 bytes Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type /dev/sdb1 0,0,1 1023,254,63 1 4294967295 4294967295 2047G ee EFI GPT fdisk: device has more than 2^32 sectors, can't use all of them I've recompiled, recreated extension and tested, as i dont have any mpt2sas you retry please ? 1 Quote Link to post Share on other sites
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.