RedPill - the new loader for 6.2.4 - Discussion


Recommended Posts

HI,

this days i have created a test nas V7.0.1-42218 (DS918+)

VM on  Proxmox, V7.0-11

Boot from USB with args.

Machine Q35

CPU: KVM

UEFI Boot

Virtio NW 

Virtio SCSI

Build and boot are successfull with one disk (Disk id 8? with 4 slots?)

i tried to add a second disk and add it to the SHR Volume for testing. But i cannot add this disk, because it does not meet the requirements (screenshot attached).

 

i tried to change from VirtiO SCSI to Virtio SCSI-Single. Does not change the issue, but i observed one thing:

 

When starting Vm with VirtIO SCSI and 2 Disk i see following messages in serial console, but not after changing to VirtIO SCSI Single.

[    5.533294] sd 7:0:0:0: [synoboot] Attached SCSI disk
[    6.271152] want_idx 6 index 7
[    6.271551] want_idx 6 index 7. delay and reget
[    7.272150] want_idx 6 index 7
[    7.272549] want_idx 6 index 7. delay and reget
[    8.273154] want_idx 6 index 7
[    8.273567] want_idx 6 index 7. delay and reget
[    9.274128] want_idx 6 index 7
[    9.274574] want_idx 6 index 7. delay and reget
[   10.275084] want_idx 6 index 7
[   10.275584] want_idx 6 index 7. delay and reget
[   11.276094] want_idx 6 index 7
[   11.276645] want_idx 6 index 7. delay and reget
[   12.277102] want_idx 6 index 7
[   12.277644] want_idx 6 index 7. delay and reget
[   13.278149] want_idx 6 index 7
[   13.278689] want_idx 6 index 7. delay and reget
[   14.279161] want_idx 6 index 7
[   14.279705] want_idx 6 index 7. delay and reget
[   15.280132] want_idx 6 index 7
[   15.280661] want_idx 6 index 7. delay and reget
[   16.281095] want_idx 6 index 7
[   16.281579] want_idx 6 index 7. delay and reget

 

is this a known behavior, or is there maybe some solution for this issue?

br

Chris

 

requirements.PNG

HDD Info.PNG

Link to post
Share on other sites

@Mixpower  use other USB Stick, to check if you get same error with the VID/PID
i had one what gives me Errors on Gen8, after switch to another USB Stick with different VID/PID it boots up

Edited by altas
Link to post
Share on other sites
1 hour ago, altas said:

@Mixpower  use other USB Stick, to check if you get same error with the VID/PID
i had one what gives me Errors on Gen8, after switch to another USB Stick with different VID/PID it boots up

Thanks, I'll try that!

 

EDIT: That seemed to be the problem indeed! Now I have a whole different problem maybe @pocopicocan shine a light on it?

:: Loading kernel modules from extensions ...
Loading kmod #0 "libphy.ko" for pocopico.tg3 (args: )
[    8.231694] WARNING: module 'libphy' built without retpoline-enabled compiler, may affect Spectre v2 mitigation
[    8.282067] BUG: unable to handle kernel paging request at 0000005500000018
[    8.316277] IP: [<ffffffff81094f80>] load_module+0x1f80/0x2510
[    8.344935] PGD 101e6d067 PUD 0
[    8.360818] Oops: 0000 [#1] SMP
[    8.376451] Modules linked in: libphy(F+) usb_storage xhci_hcd uhci_hcd ehci_pci ehci_hcd usbcore usb_common redpill(OF)
[    8.429358] CPU: 2 PID: 3789 Comm: insmod Tainted: GF          O 3.10.108 #41222
[    8.465782] Hardware name: HP ProLiant MicroServer Gen8, BIOS J06 04/04/2019
[    8.500201] task: ffff8801017f9040 ti: ffff8801014d8000 task.ti: ffff8801014d8000
[    8.536745] RIP: 0010:[<ffffffff81094f80>]  [<ffffffff81094f80>] load_module+0x1f80/0x2510
[    8.576842] RSP: 0018:ffff8801014dbdb8  EFLAGS: 00010286
[    8.602492] RAX: 0000005500000000 RBX: ffff8801014dbec8 RCX: ffff880101f83ae1
[    8.637361] RDX: ffff880101f83b50 RSI: 0000000000000000 RDI: ffffffff818367a0
[    8.672025] RBP: ffff8801014dbeb8 R08: ffff880101f83ae0 R09: ffff880101f83990
[    8.706741] R10: 000000000000000a R11: ffffffff81700dbc R12: ffffffffa00c2bd0
[    8.741616] R13: ffffffffa00c2b98 R14: 00000054fffffff0 R15: ffffffffa00c2b80
[    8.776219] FS:  00007f9e9891f740(0000) GS:ffff880109a80000(0000) knlGS:0000000000000000
[    8.816226] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[    8.844139] CR2: 0000005500000018 CR3: 000000010165e000 CR4: 00000000001607e0
[    8.878529] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[    8.913327] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[    8.948091] Stack:
[    8.957807]  ffffffff812a0a40 00007ffffffff000 ffff8801014dbec8 ffff8801014dbed0
[    8.995341]  ffff8801017f9040 ffff8801017f9040 000000000170c9c0 ffffffff8160eed0
[    9.031274]  ffff8801014dbe50 ffffffffa00c5068 ffffffffa00c2d78 ffffffffa00c2d78
[    9.067290] Call Trace:
[    9.079362]  [<ffffffff812a0a40>] ? ddebug_proc_write+0xf0/0xf0
[    9.108381]  [<ffffffff810956ad>] ? SYSC_finit_module+0x7d/0xc0
[    9.137362]  [<ffffffff814aaf3e>] ? system_call_fastpath+0x1c/0x21
[    9.149752] scsi 6:0:0:0: Direct-Access     SanDisk  Ultra                    1.00 PQ: 0 ANSI: 6
[    9.149859] <redpill/scsi_notifier.c:65> Probing SCSI device using sd_probe_shim
[    9.149860] <redpill/scsi_notifier.c:77> Triggering SCSI_EVT_DEV_PROBING notifications
[    9.149861] <redpill/scsi_notifier.c:87> Calling original sd_probe()
[    9.149919] <redpill/scsi_notifier.c:91> Triggering SCSI_EVT_DEV_PROBED notifications - sd_probe() exit=0
[    9.150511] sd 6:0:0:0: [synoboot] 120127488 512-byte logical blocks: (61.5 GB/57.2 GiB)
[    9.151761] sd 6:0:0:0: [synoboot] Write Protect is off
[    9.151763] sd 6:0:0:0: [synoboot] Mode Sense: 43 00 00 00
[    9.152757] sd 6:0:0:0: [synoboot] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[    9.158265]  synoboot: synoboot1 synoboot2 synoboot3
[    9.161529] sd 6:0:0:0: [synoboot] Attached SCSI removable disk
[    9.201684] scsi 7:0:0:0: Direct-Access     HP iLO   Internal SD-CARD         2.10 PQ: 0 ANSI: 0
[    9.201796] <redpill/scsi_notifier.c:65> Probing SCSI device using sd_probe_shim
[    9.201797] <redpill/scsi_notifier.c:77> Triggering SCSI_EVT_DEV_PROBING notifications
[    9.201798] <redpill/scsi_notifier.c:87> Calling original sd_probe()
[    9.201862] <redpill/scsi_notifier.c:91> Triggering SCSI_EVT_DEV_PROBED notifications - sd_probe() exit=0
[    9.202694] sd 7:0:0:0: [sdu] 30253056 512-byte logical blocks: (15.4 GB/14.4 GiB)
[    9.204082] sd 7:0:0:0: [sdu] Write Protect is off
[    9.204083] sd 7:0:0:0: [sdu] Mode Sense: 23 00 00 00
[    9.205317] sd 7:0:0:0: [sdu] No Caching mode page found
[    9.205318] sd 7:0:0:0: [sdu] Assuming drive cache: write through
[    9.208693] sd 7:0:0:0: [sdu] No Caching mode page found
[    9.208694] sd 7:0:0:0: [sdu] Assuming drive cache: write through
[    9.225477]  sdu: sdu1 sdu2 sdu3
[    9.229474] sd 7:0:0:0: [sdu] No Caching mode page found
[    9.229476] sd 7:0:0:0: [sdu] Assuming drive cache: write through
[    9.229477] sd 7:0:0:0: [sdu] Attached SCSI disk
[   10.039575] Code: 5c 24 68 0f 85 70 fb ff ff 48 c7 c7 a0 67 83 81 e8 b6 97 40 00 49 8b 87 f8 01 00 00 4c 8d 70 f0 49 8d 46 10 48 39 44 24 58 74 20 <49> 8b 46 28 4c 89 ea 4c 89 e6 48 8b b8 c0 00 00 00 e8 ea f3 10
[   10.132585] RIP  [<ffffffff81094f80>] load_module+0x1f80/0x2510
[   10.161573]  RSP <ffff8801014dbdb8>
[   10.178632] CR2: 0000005500000018
[   10.195198] ---[ end trace 5876837e43c70db5 ]---
Killed
ERROR: kernel extensions "libphy.ko" from pocopico.tg3 failed to load
Exit on error [99] rp ext init exec failure...
Tue Oct  5 08:18:27 UTC 2021
none /sys/kernel/debug debugfs rw,relatime 0 0
sys /sys sysfs rw,relatime 0 0
none /dev devtmpfs rw,relatime,size=1978620k,nr_inodes=494655,mode=755 0 0
proc /proc proc rw,relatime 0 0
umount: /etc/mtab: No such file or directory
kill: invalid number ''
kill: invalid number ''
linuxrc.syno failed on 99
starting pid 4059, tty '': '/etc/rc'
:: Starting /etc/rc
:: Mounting procfs ... [  OK  ]
:: Mounting tmpfs ... [  OK  ]
:: Mounting devtmpfs ... [  OK  ]
:: Mounting devpts ... [  OK  ]
:: Mounting sysfs ... [  OK  ]
:: Loading module sg

I have used the ext-manager to bundle your tg3 driver but is it different from the one you posted earlier for Gen8?

Als it now just hangs on Loading module sg.

Edited by Mixpower
Link to post
Share on other sites
12 hours ago, Mixpower said:

EDIT2: It just does this over and over and over, tried different usb ports but it does not matter it keeps doing this, I checked the VID and PID again and there are correct anyone has a clue?

 

If I unplug the usbdrive and plug it back in it does this but then goes back to the same again.

 

Glad you sorted out the serial port thing.

 

Re. the USB, I can't see anything wrong there. All the mentions of devices with a VID of 0x03f0 are it testing HP devices inside your machine and it failing (as they don't match the VID/PID you specified), which is to be expected.

 

It finally finds... 

Device <vid=26bd, pid=9917>

...(an Integral Memory USB stick) and mounts the synoboot partitions.

 

I've a feeling this may be fixed by the boot-wait extension when the extensions are up and running

 

Catching up! I see you sorted the USB boot thing with another stick.

 

FWIW, I had problems with the tg3 drivers pocopico has in his rp-ext repo on my baremetal Gen8.

 

Try these instead (they work on my 7.0.1-42218 system with a 3.10.108 kernel):

 

Edited by WiteWulf
  • Like 1
Link to post
Share on other sites
1 minute ago, WiteWulf said:

Glad you sorted out the serial port thing.

 

Re. the USB, I can't see anything wrong there. All the mentions of devices with a VID of 0x03f0 are it testing HP devices inside your machine and it failing (as they don't match the VID/PID you specified), which is to be expected.

 

It finally finds... 


Device <vid=26bd, pid=9917>

...(an Integral Memory USB stick) and mounts the synoboot partitions.

 

I've a feeling this may be fixed by the boot-wait extension when the extensions are up and running

Thanks, I don't have this behavior anymore after using a different usb stick as you can see in my post above you.

It does now do other things but it still does not boot.

Link to post
Share on other sites
10 minutes ago, Mixpower said:

Thanks, I don't have this behavior anymore after using a different usb stick as you can see in my post above you.

It does now do other things but it still does not boot.

Can you remind us your loader and DSM version ?

Link to post
Share on other sites
19 minutes ago, Orphée said:

Can you remind us your loader and DSM version ?

I am using the redpill-tool-chain v0.11 to build the image for ds3615xs 7.0-41222 and have used the local_rp_load_path to use a local redpill-load folder and use ext-manager to load SAS Activator and your tg3 extension.

 

18 minutes ago, WiteWulf said:

@Mixpower sorry, catching up posts in corder :) I've editted my original post above.

No worries, thanks again for that! :) Will try those now!

 

 

EDIT: That seems to be the fix @WiteWulf Thanks again for those tg3 drivers, I used them before but i didn't know I had the USB problem until I check VSP on my Gen8 thanks again for point that out in this topic it's a really handy tool for debugging! :)

 

IT IS NOW BOOTED!!! :D

 

@pocopicoCan't you use the tg3 drivers you posted before as WiteWulf mentioned in your extensions? Or maybe create a different build for Gen8 users? Thanks again for your great work! :) 

 

Edited by Mixpower
  • Like 1
Link to post
Share on other sites
23 minutes ago, scoobdriver said:

@Mixpower I used this with success previously to load the tg3 drivers on my Gen8 with onboard NIC 

 

I've been on holiday, so I have not had the opportunity to try the new Extensions as yet. Just catching up on all the developments . 

Thanks, WiteWulf mentioned that driver and it works now! :) 

Link to post
Share on other sites
50 minutes ago, altas said:

@Mixpower so then time to check this Driver also on my GEN8 :)
current i use the Intel NIC

Yes this driver works great so far!

 

@WiteWulfI did a migration which went fine and on boot all 4 drives seem detected but in DSM only one drive is detected for some reason.

Is it possible to save this or start from scratch?

Link to post
Share on other sites
6 minutes ago, Mixpower said:

@WiteWulfI did a migration which went fine and on boot all 4 drives seem detected but in DSM only one drive is detected for some reason.

Is it possible to save this or start from scratch?

I don't know, that's very strange. I've only heard this happening with additional SATA/SAS HBA cards installed. Go back to basics: check all the cables are connected internally, that the BIOS is seeing all drives, then have a look through the console output as it's booting up to see if there's anything obvious.

Link to post
Share on other sites

I'm playing with DS918+ loader 6.2.4 on VMWare Workstation.

 

It works, I installed Moments to check face detection...

 

Do you know what it means ? :

 

Quote

2021-10-05T12:55:44+02:00 DS918 synophoto-concept: /source/synophoto-plugin-detection/src/detection/detector.cpp:134 Error: (detection plugin) [IeNetwork] Init network failed
2021-10-05T12:55:44+02:00 DS918 synophoto-concept: uncaught thread task exception /source/synophoto/src/daemon/plugin/plugin_worker.cpp:102 plugin init failed: /var/packages/SynologyMoments/target/usr/lib/libsynophoto-plugin-detection.so

 

Link to post
Share on other sites
44 minutes ago, WiteWulf said:

I don't know, that's very strange. I've only heard this happening with additional SATA/SAS HBA cards installed. Go back to basics: check all the cables are connected internally, that the BIOS is seeing all drives, then have a look through the console output as it's booting up to see if there's anything obvious.

Yes, everything worked fine with Jun's loader and the onboard B120i is not used so that should not be the problem.

As said the drives are detected from what I can see, here is the output on boot. (I have masked the drive serial numbers)

Running "load-builtin-sas.sh" for thethorgroup.sas-activator->on_boot
Loading SAS controller(s) driver(s)
Loading LSI SAS 6Gb driver from /lib/modules/mpt2sas.ko
[    9.585349] mpt2sas version 20.00.00.00 loaded
[    9.607238] scsi7 : Fusion MPT SAS Host
[    9.626264] mpt2sas0: 64 BIT PCI BUS DMA ADDRESSING SUPPORTED, total mem (4048632 kB)
[    9.737263] mpt2sas0: MSI-X vectors supported: 16, no of cores: 8, max_msix_vectors: -1
[    9.775982] mpt2sas 0000:07:00.0: irq 52 for MSI/MSI-X
[    9.800697] mpt2sas 0000:07:00.0: irq 53 for MSI/MSI-X
[    9.825709] mpt2sas 0000:07:00.0: irq 54 for MSI/MSI-X
[    9.851153] mpt2sas 0000:07:00.0: irq 55 for MSI/MSI-X
[    9.876566] mpt2sas 0000:07:00.0: irq 56 for MSI/MSI-X
[    9.901752] mpt2sas 0000:07:00.0: irq 57 for MSI/MSI-X
[    9.926564] mpt2sas 0000:07:00.0: irq 58 for MSI/MSI-X
[    9.951804] mpt2sas 0000:07:00.0: irq 59 for MSI/MSI-X
[    9.976817] mpt2sas0-msix0: PCI-MSI-X enabled: IRQ 52
[   10.001662] mpt2sas0-msix1: PCI-MSI-X enabled: IRQ 53
[   10.026363] mpt2sas0-msix2: PCI-MSI-X enabled: IRQ 54
[   10.050820] mpt2sas0-msix3: PCI-MSI-X enabled: IRQ 55
[   10.074640] mpt2sas0-msix4: PCI-MSI-X enabled: IRQ 56
[   10.099318] mpt2sas0-msix5: PCI-MSI-X enabled: IRQ 57
[   10.124109] mpt2sas0-msix6: PCI-MSI-X enabled: IRQ 58
[   10.148593] mpt2sas0-msix7: PCI-MSI-X enabled: IRQ 59
[   10.173487] mpt2sas0: iomem(0x00000000fbff0000), mapped(0xffffc90004440000), size(65536)
[   10.212615] mpt2sas0: ioport(0x0000000000005000), size(256)
[   10.311909] mpt2sas0: sending message unit reset !!
[   10.336936] mpt2sas0: message unit reset: SUCCESS
[   10.423096] mpt2sas0: Allocated physical memory: size(17329 kB)
[   10.451988] mpt2sas0: Current Controller Queue Depth(9977), Max Controller Queue Depth(10240)
[   10.493322] mpt2sas0: Scatter Gather Elements per IO(128)
[   10.578600] mpt2sas0: LSISAS2308: FWVersion(18.00.00.00), ChipRevision(0x05), BiosVersion(07.39.00.00)
[   10.624376] mpt2sas0: Protocol=(Initiator,Target), Capabilities=(TLR,EEDP,Snapshot Buffer,Diag Trace Buffer,Task Set Full,NCQ)
[   10.680069] mpt2sas0: sending port enable !!
[   12.216206] mpt2sas0: host_add: handle(0x0001), sas_addr(0x500605b008d3ce90), phys(8)
[   12.254762] mpt2sas0: detecting: handle(0x0009), sas_address(0x4433221104000000), phy(4)
[   12.294241] mpt2sas0: REPORT_LUNS: handle(0x0009), retries(0)
[   12.714166] mpt2sas0: TEST_UNIT_READY: handle(0x0009), lun(0)
[   13.045042] mpt2sas0: REPORT_LUNS: handle(0x0009), retries(0)
[   13.072888] mpt2sas0: TEST_UNIT_READY: handle(0x0009), lun(0)
[   13.106705] scsi 7:0:0:0: Direct-Access     WDC      WD2005FBYZ-01YCBB2       RR07 PQ: 0 ANSI: 6
[   13.150299] scsi 7:0:0:0: SATA: handle(0x0009), sas_addr(0x4433221104000000), phy(4), device_name(0x0000000000000000)
[   13.201640] scsi 7:0:0:0: SATA: enclosure_logical_id(0x500605b008d3ce90), slot(3)
[   13.238627] scsi 7:0:0:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y)
[   13.280908] scsi 7:0:0:0: serial_number(     WD-XXXXXXXXXXXX)
[   13.308786] scsi 7:0:0:0: qdepth(32), tagged(1), simple(0), ordered(0), scsi_level(7), cmd_que(1)
[   13.351903] <redpill/scsi_notifier.c:65> Probing SCSI device using sd_probe_shim
[   13.387979] <redpill/scsi_notifier.c:77> Triggering SCSI_EVT_DEV_PROBING notifications
[   13.426806] <redpill/sata_port_shim.c:66> Found new disk vendor="WDC     WD2005FBYZ-0    RR07     WD-WMC6N0H2EJSM" model="WD2005FBYZ-01YCBB2      " connected to "Fusion MPT SAS Host" HBA over non-SATA port (type=3) - fixing to SATA port (type=1)
[   13.532072] <redpill/scsi_notifier.c:87> Calling original sd_probe()
[   13.562986] <redpill/scsi_notifier.c:91> Triggering SCSI_EVT_DEV_PROBED notifications - sd_probe() exit=0
[   13.564179] sd 7:0:0:0: [sdh] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
[   13.570573] sd 7:0:0:0: [sdh] Write Protect is off
[   13.570574] sd 7:0:0:0: [sdh] Mode Sense: 7f 00 10 08
[   13.572650] sd 7:0:0:0: [sdh] Write cache: enabled, read cache: enabled, supports DPO and FUA
[   13.736135] mpt2sas0: detecting: handle(0x000a), sas_address(0x4433221105000000), phy(5)
[   13.775241] mpt2sas0: REPORT_LUNS: handle(0x000a), retries(0)
[   13.803147]  sdh: sdh1 sdh2 sdh3
[   13.832207] sd 7:0:0:0: [sdh] Attached SCSI disk
[   13.965461] mpt2sas0: TEST_UNIT_READY: handle(0x000a), lun(0)
[   14.297472] mpt2sas0: REPORT_LUNS: handle(0x000a), retries(0)
[   14.325069] mpt2sas0: TEST_UNIT_READY: handle(0x000a), lun(0)
[   14.358911] scsi 7:0:1:0: Direct-Access     WDC      WD2005FBYZ-01YCBB2       RR07 PQ: 0 ANSI: 6
[   14.402753] scsi 7:0:1:0: SATA: handle(0x000a), sas_addr(0x4433221105000000), phy(5), device_name(0x0000000000000000)
[   14.454440] scsi 7:0:1:0: SATA: enclosure_logical_id(0x500605b008d3ce90), slot(2)
[   14.490683] scsi 7:0:1:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y)
[   14.532902] scsi 7:0:1:0: serial_number(     WD-XXXXXXXXXXXX)
[   14.560562] scsi 7:0:1:0: qdepth(32), tagged(1), simple(0), ordered(0), scsi_level(7), cmd_que(1)
[   14.603905] <redpill/scsi_notifier.c:65> Probing SCSI device using sd_probe_shim
[   14.639970] <redpill/scsi_notifier.c:77> Triggering SCSI_EVT_DEV_PROBING notifications
[   14.678608] <redpill/scsi_notifier.c:87> Calling original sd_probe()
[   14.709422] want_idx 7 index 8. delay and reget
[   15.732100] want_idx 7 index 8
[   15.746730] want_idx 7 index 8. delay and reget
[   16.769285] want_idx 7 index 8
[   16.783923] want_idx 7 index 8. delay and reget
[   17.806467] want_idx 7 index 8
[   17.821391] want_idx 7 index 8. delay and reget
[   18.844655] want_idx 7 index 8
[   18.859635] want_idx 7 index 8. delay and reget
[   19.881839] want_idx 7 index 8
[   19.896865] want_idx 7 index 8. delay and reget
[   20.920024] want_idx 7 index 8
[   20.935061] want_idx 7 index 8. delay and reget
[   21.958210] want_idx 7 index 8
[   21.973257] want_idx 7 index 8. delay and reget
[   22.996396] want_idx 7 index 8
[   23.011361] want_idx 7 index 8. delay and reget
[   24.034583] want_idx 7 index 8
[   24.049784] want_idx 7 index 8. delay and reget
[   25.072767] want_idx 7 index 8
[   25.087767] want_idx 7 index 8. delay and reget
[   26.110955] want_idx 7 index 8
[   26.126089] want_idx 7 index 8. delay and reget
[   27.149139] want_idx 7 index 8
[   27.163945] want_idx 7 index 8. delay and reget
[   28.186325] want_idx 7 index 8
[   28.201122] want_idx 7 index 8. delay and reget
[   29.223513] want_idx 7 index 8
[   29.238067] want_idx 7 index 8. delay and reget
[   30.260700] want_idx 7 index 8
[   30.275773] <redpill/scsi_notifier.c:91> Triggering SCSI_EVT_DEV_PROBED notifications - sd_probe() exit=0
[   30.277139] sd 7:0:1:0: [sdi] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
[   30.283646] sd 7:0:1:0: [sdi] Write Protect is off
[   30.283648] sd 7:0:1:0: [sdi] Mode Sense: 7f 00 10 08
[   30.285721] sd 7:0:1:0: [sdi] Write cache: enabled, read cache: enabled, supports DPO and FUA
[   30.360941]  sdi: sdi1 sdi2 sdi3
[   30.448984] sd 7:0:1:0: [sdi] Attached SCSI disk
[   30.490059] mpt2sas0: detecting: handle(0x000b), sas_address(0x4433221106000000), phy(6)
[   30.530023] mpt2sas0: REPORT_LUNS: handle(0x000b), retries(0)
[   30.734667] mpt2sas0: TEST_UNIT_READY: handle(0x000b), lun(0)
[   31.066625] mpt2sas0: REPORT_LUNS: handle(0x000b), retries(0)
[   31.094853] mpt2sas0: TEST_UNIT_READY: handle(0x000b), lun(0)
[   31.128783] scsi 7:0:2:0: Direct-Access     WDC      WD2005FBYZ-01YCBB2       RR07 PQ: 0 ANSI: 6
[   31.172581] scsi 7:0:2:0: SATA: handle(0x000b), sas_addr(0x4433221106000000), phy(6), device_name(0x0000000000000000)
[   31.224582] scsi 7:0:2:0: SATA: enclosure_logical_id(0x500605b008d3ce90), slot(1)
[   31.261085] scsi 7:0:2:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y)
[   31.303278] scsi 7:0:2:0: serial_number(     WD-XXXXXXXXXXXX)
[   31.331454] scsi 7:0:2:0: qdepth(32), tagged(1), simple(0), ordered(0), scsi_level(7), cmd_que(1)
[   31.375343] <redpill/scsi_notifier.c:65> Probing SCSI device using sd_probe_shim
[   31.411148] <redpill/scsi_notifier.c:77> Triggering SCSI_EVT_DEV_PROBING notifications
[   31.450214] <redpill/scsi_notifier.c:87> Calling original sd_probe()
[   31.480423] want_idx 7 index 9. delay and reget
[   32.503255] want_idx 7 index 9
[   32.517717] want_idx 7 index 9. delay and reget
[   33.540440] want_idx 7 index 9
[   33.555142] want_idx 7 index 9. delay and reget
[   34.577622] want_idx 7 index 9
[   34.592351] want_idx 7 index 9. delay and reget
[   35.614808] want_idx 7 index 9
[   35.629830] want_idx 7 index 9. delay and reget
[   36.652994] want_idx 7 index 9
[   36.667833] want_idx 7 index 9. delay and reget
[   37.691181] want_idx 7 index 9
[   37.706037] want_idx 7 index 9. delay and reget
[   38.728364] want_idx 7 index 9
[   38.743224] want_idx 7 index 9. delay and reget
[   39.765549] want_idx 7 index 9
[   39.779935] want_idx 7 index 9. delay and reget
[   40.802733] want_idx 7 index 9
[   40.817384] want_idx 7 index 9. delay and reget
[   41.839920] want_idx 7 index 9
[   41.854672] want_idx 7 index 9. delay and reget
[   42.877102] want_idx 7 index 9
[   42.892007] want_idx 7 index 9. delay and reget
[   43.914287] want_idx 7 index 9
[   43.929150] want_idx 7 index 9. delay and reget
[   44.951472] want_idx 7 index 9
[   44.966575] want_idx 7 index 9. delay and reget
[   45.989658] want_idx 7 index 9
[   46.004641] want_idx 7 index 9. delay and reget
[   47.026842] want_idx 7 index 9
[   47.041913] <redpill/scsi_notifier.c:91> Triggering SCSI_EVT_DEV_PROBED notifications - sd_probe() exit=0
[   47.043282] sd 7:0:2:0: [sdj] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
[   47.049766] sd 7:0:2:0: [sdj] Write Protect is off
[   47.049767] sd 7:0:2:0: [sdj] Mode Sense: 7f 00 10 08
[   47.051849] sd 7:0:2:0: [sdj] Write cache: enabled, read cache: enabled, supports DPO and FUA
[   47.127287]  sdj: sdj1 sdj2 sdj3
[   47.215277] sd 7:0:2:0: [sdj] Attached SCSI disk
[   47.252922] mpt2sas0: detecting: handle(0x000c), sas_address(0x4433221107000000), phy(7)
[   47.292282] mpt2sas0: REPORT_LUNS: handle(0x000c), retries(0)
[   47.504078] mpt2sas0: TEST_UNIT_READY: handle(0x000c), lun(0)
[   47.835782] mpt2sas0: REPORT_LUNS: handle(0x000c), retries(0)
[   47.863842] mpt2sas0: TEST_UNIT_READY: handle(0x000c), lun(0)
[   47.897425] scsi 7:0:3:0: Direct-Access     WDC      WD2005FBYZ-01YCBB2       RR07 PQ: 0 ANSI: 6
[   47.941332] scsi 7:0:3:0: SATA: handle(0x000c), sas_addr(0x4433221107000000), phy(7), device_name(0x0000000000000000)
[   47.993476] scsi 7:0:3:0: SATA: enclosure_logical_id(0x500605b008d3ce90), slot(0)
[   48.030432] scsi 7:0:3:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y)
[   48.072889] scsi 7:0:3:0: serial_number(     WD-XXXXXXXXXXXX)
[   48.100928] scsi 7:0:3:0: qdepth(32), tagged(1), simple(0), ordered(0), scsi_level(7), cmd_que(1)
[   48.143907] <redpill/scsi_notifier.c:65> Probing SCSI device using sd_probe_shim
[   48.180052] <redpill/scsi_notifier.c:77> Triggering SCSI_EVT_DEV_PROBING notifications
[   48.218560] <redpill/scsi_notifier.c:87> Calling original sd_probe()
[   48.248924] want_idx 7 index 10. delay and reget
[   49.272407] want_idx 7 index 10
[   49.287298] want_idx 7 index 10. delay and reget
[   50.310594] want_idx 7 index 10
[   50.325887] want_idx 7 index 10. delay and reget
[   51.348778] want_idx 7 index 10
[   51.364108] want_idx 7 index 10. delay and reget
[   52.386964] want_idx 7 index 10
[   52.402325] want_idx 7 index 10. delay and reget
[   53.426153] want_idx 7 index 10
[   53.441215] want_idx 7 index 10. delay and reget
[   54.464337] want_idx 7 index 10
[   54.480004] want_idx 7 index 10. delay and reget
[   55.503525] want_idx 7 index 10
[   55.518861] want_idx 7 index 10. delay and reget
[   56.541710] want_idx 7 index 10
[   56.557159] want_idx 7 index 10. delay and reget
[   57.579897] want_idx 7 index 10
[   57.594972] want_idx 7 index 10. delay and reget
[   58.618081] want_idx 7 index 10
[   58.633376] want_idx 7 index 10. delay and reget
[   59.656271] want_idx 7 index 10
[   59.671398] want_idx 7 index 10. delay and reget
[   60.694452] want_idx 7 index 10
[   60.709836] want_idx 7 index 10. delay and reget
[   61.732641] want_idx 7 index 10
[   61.747569] want_idx 7 index 10. delay and reget
[   62.770824] want_idx 7 index 10
[   62.786318] want_idx 7 index 10. delay and reget
[   63.809010] want_idx 7 index 10
[   63.824614] <redpill/scsi_notifier.c:91> Triggering SCSI_EVT_DEV_PROBED notifications - sd_probe() exit=0
[   63.825969] sd 7:0:3:0: [sdk] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
[   63.832470] sd 7:0:3:0: [sdk] Write Protect is off
[   63.832472] sd 7:0:3:0: [sdk] Mode Sense: 7f 00 10 08
[   63.834551] sd 7:0:3:0: [sdk] Write cache: enabled, read cache: enabled, supports DPO and FUA
[   63.938044]  sdk: sdk1 sdk2 sdk3
[   64.019261] mpt2sas0: port enable: SUCCESS
[   64.026068] sd 7:0:3:0: [sdk] Attached SCSI disk
/lib/modules/mpt3sas.ko not found - skipping
Ran "load-builtin-sas.sh" for thethorgroup.sas-activator->on_boot - exit=0

 

Link to post
Share on other sites
3 minutes ago, WiteWulf said:

I thought you were running baremetal on Gen8 Microserver? You don't need to load the SAS drivers for the onboard AHCI controller, it's SATA and supported natively.

I am running baremetal, I'm using a LSI 9207-4i4e with IT firmware with 4 drives attached.

Link to post
Share on other sites
1 hour ago, Mixpower said:

Yes this driver works great so far!

 

@WiteWulfI did a migration which went fine and on boot all 4 drives seem detected but in DSM only one drive is detected for some reason.

Is it possible to save this or start from scratch?

I had the same problem some weeks ago (only one of 4 drives was seen in DSM, baremetal install on Intel SS4200, ICH7R). With a newer version of loader and tool-chain it worked. Not sure what the problem was, maybe cached data from previous try for loader generation? Now I always clean cached data and download everything again.

In the earlier versions of the tool-chain you had to fill "vid/pid/...", in the later versions it is "pid/vid/...", I mixed up this because I didn't read carefully and filled in wrong order.

Edited by paro44
Link to post
Share on other sites
Just now, Mixpower said:

I am running baremetal, I'm using a LSI 9207-4i4e with IT firmware with 4 drives attached.

Ah, okay, you didn't mention the LSI controller previously. Please include as much information as you can either in your signature or on every request for help you post.

 

I don't have an HBA, though, so I'm afraid I'm unable to help further...

  • Like 1
Link to post
Share on other sites

  

4 minutes ago, paro44 said:

I had the same problem some weeks ago (only one of 4 drives was seen in DSM, baremetal install on Intel SS4200, ICH7R). With a newer version of loader and tool-chain it worked. Not sure what the problem was?

In the earlier versions of the tool-chain you had to fill "vid/pid/...", in the later versions it is "pid/vid/...", I mixed up this because I didn't read carefully and filled in wrong order.

Thanks, I'll see what I can find out.

 

4 minutes ago, WiteWulf said:

Ah, okay, you didn't mention the LSI controller previously. Please include as much information as you can either in your signature or on every request for help you post.

 

I don't have an HBA, though, so I'm afraid I'm unable to help further...

No problem, I thought it as clear because I am using mpt2sas. :)

Edited by Mixpower
Link to post
Share on other sites
1 minute ago, Mixpower said:

No problem, I thought it as clear because I am using mpt2sas. :) 

Do you have drives on the onboard controller, are they seen? Maybe you can try that, if this is your test nas with no important data on it.

Link to post
Share on other sites
57 minutes ago, paro44 said:

Do you have drives on the onboard controller, are they seen? Maybe you can try that, if this is your test nas with no important data on it.

I don't but I want to use my LSI controller, I already wiped the whole system now and it only sees disk 8 even though these drives are connected to 0,1,2,3 and are all present at boot as seen by the output. I also tried the mpt2sas driver of @pocopicoinstead of the one from ThorGroup but the issue remains.

Link to post
Share on other sites

For those who might use VMWare Workstation to do some tests.

 

Serial console from TCPIP is not available from GUI, and not officially supported.

 

But you can edit your .vmx file to add :

 

serial0.present = "TRUE"
serial0.fileType = "network"
serial0.fileName = "0.0.0.0:10021"
serial0.network.endPoint = "server"
serial0.startConnected = "TRUE"

 

10021 or whatever suits you.

 

Then you can telnet to the serial port as usual.

  • Like 2
  • Thanks 1
Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.