Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #206551 > unrolled thread
| Started by | Mimiko <vbvbrj@gmail.com> |
|---|---|
| First post | 2019-03-24 21:00 +0100 |
| Last post | 2019-03-26 17:50 +0100 |
| Articles | 8 — 4 participants |
Back to article view | Back to linux.debian.user
mdadm started before disks are detected Mimiko <vbvbrj@gmail.com> - 2019-03-24 21:00 +0100
Re: mdadm started before disks are detected Sven Hartge <sven@svenhartge.de> - 2019-03-24 21:50 +0100
Re: mdadm started before disks are detected Mimiko <vbvbrj@gmail.com> - 2019-03-25 18:30 +0100
Re: mdadm started before disks are detected Sven Hartge <sven@svenhartge.de> - 2019-03-25 20:30 +0100
Re: mdadm started before disks are detected John Hasler <jhasler@newsguy.com> - 2019-03-25 21:30 +0100
Re: mdadm started before disks are detected Mimiko <vbvbrj@gmail.com> - 2019-03-26 07:20 +0100
Re: mdadm started before disks are detected Sven Hartge <sven@svenhartge.de> - 2019-03-26 17:50 +0100
Re: mdadm started before disks are detected "Alexander V. Makartsev" <avbetev@gmail.com> - 2019-03-26 17:50 +0100
| From | Mimiko <vbvbrj@gmail.com> |
|---|---|
| Date | 2019-03-24 21:00 +0100 |
| Subject | mdadm started before disks are detected |
| Message-ID | <xFhrH-5hf-9@gated-at.bofh.it> |
hello.
I came across a problem when booting. In the server is installed 4 disks connected to raid controller and 2 disks connected to motherboard sata
interfaces. During booting disks connected to raid controller are detected before md raid assembling process, while the 2 disks connected to
motherboard sata interfaces are detected after md raid assembly, so the raid made of this 2 disks are not detected and assembled during boot.
From log is seen that sdd and sde a detected after mdamd is started to assembly the raids.
How can I force those 2 disks to be detected before mdadm?
This is the log:
[ 1.186650] No iBFT detected.
[ 1.186876] TCP cubic registered
[ 1.186951] NET: Registered protocol family 10
[ 1.187496] Mobile IPv6
[ 1.187498] NET: Registered protocol family 17
[ 1.187548] PM: Resume from disk failed.
[ 1.187553] registered taskstats version 1
[ 1.188011] rtc_cmos 00:05: setting system clock to 2019-03-24 21:08:51 UTC (1553461731)
[ 1.188061] Initalizing network drop monitor service
[ 1.188084] Freeing unused kernel memory: 592k freed
[ 1.188170] Write protecting the kernel read-only data: 4236k
[ 1.197578] udev[116]: starting version 164
[ 1.224921] SCSI subsystem initialized
[ 1.229396] Fusion MPT base driver 3.04.12
[ 1.229398] Copyright (c) 1999-2008 LSI Corporation
[ 1.234546] Fusion MPT SAS Host driver 3.04.12
[ 1.234577] mptsas 0000:06:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 1.234648] mptbase: ioc0: Initiating bringup
[ 1.955862] ioc0: LSISAS1064E B3: Capabilities={Initiator}
[ 1.955889] mptsas 0000:06:00.0: setting latency timer to 64
[ 10.778908] scsi0 : ioc0: LSISAS1064E B3, FwRev=011e0500h, Ports=1, MaxQ=277, IRQ=16
[ 10.801289] mptsas: ioc0: attaching sata device: fw_channel 0, fw_id 6, phy 0, sas_addr 0x3dbfa994f1bd8090
[ 10.804203] scsi 0:0:0:0: Direct-Access ATA WD2502ABYS-23B7A 3B07 PQ: 0 ANSI: 5
[ 10.807855] mptsas: ioc0: attaching sata device: fw_channel 0, fw_id 7, phy 1, sas_addr 0x3f3b341d9a8a7d75
[ 10.824619] scsi 0:0:1:0: Direct-Access ATA TOSHIBA MG03ACA1 FL1A PQ: 0 ANSI: 5
[ 10.827405] mptsas: ioc0: attaching sata device: fw_channel 0, fw_id 9, phy 2, sas_addr 0x3dbfa995eebc7a90
[ 10.830257] scsi 0:0:2:0: Direct-Access ATA WD2502ABYS-23B7A 3B07 PQ: 0 ANSI: 5
[ 10.833875] mptsas: ioc0: attaching sata device: fw_channel 0, fw_id 8, phy 3, sas_addr 0x3f5c341d88a07675
[ 10.853400] scsi 0:0:3:0: Direct-Access ATA TOSHIBA MG03ACA1 FL1A PQ: 0 ANSI: 5
[ 10.856241] mptsas: ioc0: attaching raid volume, channel 1, id 5
[ 10.857101] scsi 0:1:5:0: Direct-Access LSILOGIC Logical Volume 3000 PQ: 0 ANSI: 2
[ 10.868797] sd 0:1:5:0: [sdc] 486326272 512-byte logical blocks: (248 GB/231 GiB)
[ 10.869031] sd 0:1:5:0: [sdc] Write Protect is off
[ 10.869033] sd 0:1:5:0: [sdc] Mode Sense: 03 00 00 08
[ 10.869447] sd 0:1:5:0: [sdc] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 10.870392] sdc: sdc1 sdc2 sdc3 sdc4 < sdc5 sdc6 >
[ 10.909617] sd 0:1:5:0: [sdc] Attached SCSI disk
[ 10.963876] sd 0:0:3:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
[ 10.981506] sd 0:0:1:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
[ 11.044709] sd 0:0:3:0: [sdb] Write Protect is off
[ 11.044714] sd 0:0:3:0: [sdb] Mode Sense: 73 00 00 08
[ 11.045837] sd 0:0:3:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 11.062588] sd 0:0:1:0: [sda] Write Protect is off
[ 11.062593] sd 0:0:1:0: [sda] Mode Sense: 73 00 00 08
[ 11.063707] sd 0:0:1:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 11.104040] sdb: unknown partition table
[ 11.130203] sda: unknown partition table
[ 11.187144] sd 0:0:3:0: [sdb] Attached SCSI disk
[ 11.233674] sd 0:0:1:0: [sda] Attached SCSI disk
[ 11.273175] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[ 11.274213] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[ 11.281803] md: raid1 personality registered for level 1
[ 11.284091] mdadm: sending ioctl 1261 to a partition!
[ 11.284096] mdadm: sending ioctl 1261 to a partition!
[ 11.284281] mdadm: sending ioctl 1261 to a partition!
[ 11.284284] mdadm: sending ioctl 1261 to a partition!
[ 11.284467] mdadm: sending ioctl 1261 to a partition!
[ 11.284470] mdadm: sending ioctl 1261 to a partition!
[ 11.284648] mdadm: sending ioctl 1261 to a partition!
[ 11.284651] mdadm: sending ioctl 1261 to a partition!
[ 11.284826] mdadm: sending ioctl 1261 to a partition!
[ 11.284829] mdadm: sending ioctl 1261 to a partition!
[ 11.286183] md: md0 stopped.
[ 11.287365] md: bind<sdb>
[ 11.288142] md: bind<sda>
[ 11.288972] raid1: raid set md0 active with 2 out of 2 mirrors
[ 11.288991] md0: detected capacity change from 0 to 1000203698176
[ 11.289483] md0: unknown partition table
[ 11.392474] PM: Starting manual resume from disk
[ 11.392476] PM: Resume from partition 8:34
[ 11.392477] PM: Checking hibernation image.
[ 11.392674] PM: Error -22 checking image file
[ 11.392677] PM: Resume from disk failed.
[ 11.423395] kjournald starting. Commit interval 5 seconds
[ 11.423403] EXT3-fs: mounted filesystem with ordered data mode.
[ 12.359232] udev[404]: starting version 164
[ 12.641279] input: PC Speaker as /devices/platform/pcspkr/input/input1
[ 12.642346] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input2
[ 12.642351] ACPI: Power Button [PWRB]
[ 12.642400] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input3
[ 12.642404] ACPI: Power Button [PWRF]
[ 12.644764] ACPI: SSDT 00000000df62a898 006F4 (v01 AMI IST 00000001 MSFT 03000001)
[ 12.645037] ACPI Warning: Incorrect checksum in table [SSDT] - 3F, should be 91 (20090903/tbutils-314)
[ 12.645042] ACPI: SSDT 00000000df623d98 000E4 (v01 AMI CST 00000001 MSFT 03000001)
[ 12.645460] Monitor-Mwait will be used to enter C-3 state
[ 12.645537] processor LNXCPU:00: registered as cooling_device0
[ 12.646101] processor LNXCPU:01: registered as cooling_device1
[ 12.646662] processor LNXCPU:02: registered as cooling_device2
[ 12.647164] processor LNXCPU:03: registered as cooling_device3
[ 12.647661] processor LNXCPU:04: registered as cooling_device4
[ 12.648177] processor LNXCPU:05: registered as cooling_device5
[ 12.648681] processor LNXCPU:06: registered as cooling_device6
[ 12.649169] processor LNXCPU:07: registered as cooling_device7
[ 12.665160] libata version 3.00 loaded.
[ 12.676979] ahci 0000:00:1f.2: version 3.0
[ 12.676993] alloc irq_desc for 19 on node -1
[ 12.676995] alloc kstat_irqs on node -1
[ 12.677001] ahci 0000:00:1f.2: PCI INT B -> GSI 19 (level, low) -> IRQ 19
[ 12.677099] alloc irq_desc for 36 on node -1
[ 12.677100] alloc kstat_irqs on node -1
[ 12.677108] ahci 0000:00:1f.2: irq 36 for MSI/MSI-X
[ 12.677115] ahci 0000:00:1f.2: controller can't do SNTF, turning off CAP_SNTF
[ 12.687214] dca service started, version 1.12.1
[ 12.690464] ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 6 ports 3 Gbps 0x23 impl RAID mode
[ 12.690471] ahci 0000:00:1f.2: flags: 64bit ncq ilck pm led clo pio slum part ems apst
[ 12.690478] ahci 0000:00:1f.2: setting latency timer to 64
[ 12.706458] scsi1 : ahci
[ 12.706523] scsi2 : ahci
[ 12.706582] scsi3 : ahci
[ 12.706637] scsi4 : ahci
[ 12.706693] scsi5 : ahci
[ 12.706749] scsi6 : ahci
[ 12.706875] ata1: SATA max UDMA/133 abar m2048@0xfb101000 port 0xfb101100 irq 36
[ 12.706922] ata2: SATA max UDMA/133 abar m2048@0xfb101000 port 0xfb101180 irq 36
[ 12.706924] ata3: DUMMY
[ 12.706924] ata4: DUMMY
[ 12.706925] ata5: DUMMY
[ 12.706927] ata6: SATA max UDMA/133 abar m2048@0xfb101000 port 0xfb101380 irq 36
[ 12.893858] e1000e: Intel(R) PRO/1000 Network Driver - 1.2.20-k2
[ 12.893860] e1000e: Copyright(c) 1999 - 2011 Intel Corporation.
[ 12.893891] e1000e 0000:07:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 12.893924] e1000e 0000:07:00.0: setting latency timer to 64
[ 12.894238] alloc irq_desc for 37 on node -1
[ 12.894241] alloc kstat_irqs on node -1
[ 12.894246] e1000e 0000:07:00.0: irq 37 for MSI/MSI-X
[ 12.894248] alloc irq_desc for 38 on node -1
[ 12.894250] alloc kstat_irqs on node -1
[ 12.894254] e1000e 0000:07:00.0: irq 38 for MSI/MSI-X
[ 12.894256] alloc irq_desc for 39 on node -1
[ 12.894258] alloc kstat_irqs on node -1
[ 12.894261] e1000e 0000:07:00.0: irq 39 for MSI/MSI-X
[ 12.894431] e1000e 0000:07:00.0: Disabling ASPM L0s
[ 12.894668] i801_smbus 0000:00:1f.3: PCI INT C -> GSI 18 (level, low) -> IRQ 18
[ 12.949624] Intel(R) Gigabit Ethernet Network Driver - version 3.0.6-k2
[ 12.949626] Copyright (c) 2007-2011 Intel Corporation.
[ 12.949652] igb 0000:04:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 12.949677] igb 0000:04:00.0: setting latency timer to 64
[ 12.950008] alloc irq_desc for 40 on node -1
[ 12.950010] alloc kstat_irqs on node -1
[ 12.950014] igb 0000:04:00.0: irq 40 for MSI/MSI-X
[ 12.950016] alloc irq_desc for 41 on node -1
[ 12.950017] alloc kstat_irqs on node -1
[ 12.950019] igb 0000:04:00.0: irq 41 for MSI/MSI-X
[ 12.950021] alloc irq_desc for 42 on node -1
[ 12.950022] alloc kstat_irqs on node -1
[ 12.950024] igb 0000:04:00.0: irq 42 for MSI/MSI-X
[ 12.950026] alloc irq_desc for 43 on node -1
[ 12.950027] alloc kstat_irqs on node -1
[ 12.950029] igb 0000:04:00.0: irq 43 for MSI/MSI-X
[ 12.950031] alloc irq_desc for 44 on node -1
[ 12.950032] alloc kstat_irqs on node -1
[ 12.950034] igb 0000:04:00.0: irq 44 for MSI/MSI-X
[ 12.950036] alloc irq_desc for 45 on node -1
[ 12.950037] alloc kstat_irqs on node -1
[ 12.950039] igb 0000:04:00.0: irq 45 for MSI/MSI-X
[ 12.950041] alloc irq_desc for 46 on node -1
[ 12.950042] alloc kstat_irqs on node -1
[ 12.950044] igb 0000:04:00.0: irq 46 for MSI/MSI-X
[ 12.950046] alloc irq_desc for 47 on node -1
[ 12.950047] alloc kstat_irqs on node -1
[ 12.950049] igb 0000:04:00.0: irq 47 for MSI/MSI-X
[ 12.950051] alloc irq_desc for 48 on node -1
[ 12.950052] alloc kstat_irqs on node -1
[ 12.950054] igb 0000:04:00.0: irq 48 for MSI/MSI-X
[ 12.950078] igb 0000:04:00.0: 0 vfs allocated
[ 13.005740] usbcore: registered new interface driver usbfs
[ 13.005757] usbcore: registered new interface driver hub
[ 13.005792] usbcore: registered new device driver usb
[ 13.016289] e1000e 0000:07:00.0: eth0: (PCI Express:2.5GB/s:Width x1) e4:1f:13:3f:85:da
[ 13.016292] e1000e 0000:07:00.0: eth0: Intel(R) PRO/1000 Network Connection
[ 13.016304] e1000e 0000:07:00.0: eth0: MAC: 3, PHY: 8, PBA No: FFFFFF-0FF
[ 13.025985] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 13.026033] ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 13.026055] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 13.026215] ata1.00: ATA-10: Verbatim Vi500 S3 480GB SSD, R0818A, max UDMA/133
[ 13.026221] ata1.00: 937703088 sectors, multi 0: LBA48 NCQ (depth 31/32), AA
[ 13.026364] ata2.00: ATA-10: Verbatim Vi500 S3 480GB SSD, R0818A, max UDMA/133
[ 13.026367] ata2.00: 937703088 sectors, multi 0: LBA48 NCQ (depth 31/32), AA
[ 13.026577] ata1.00: configured for UDMA/133
[ 13.026596] ata2.00: configured for UDMA/133
[ 13.028007] ata6.00: ATAPI: TSSTcorpDVD-ROM TS-H353C, LE01, max UDMA/100
[ 13.030622] ata6.00: configured for UDMA/100
[ 13.045821] scsi 1:0:0:0: Direct-Access ATA Verbatim Vi500 S R081 PQ: 0 ANSI: 5
[ 13.045973] sd 1:0:0:0: [sdd] 937703088 512-byte logical blocks: (480 GB/447 GiB)
[ 13.046000] scsi 2:0:0:0: Direct-Access ATA Verbatim Vi500 S R081 PQ: 0 ANSI: 5
[ 13.046072] sd 1:0:0:0: [sdd] Write Protect is off
[ 13.046075] sd 1:0:0:0: [sdd] Mode Sense: 00 3a 00 00
[ 13.046106] sd 1:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 13.046144] sd 2:0:0:0: [sde] 937703088 512-byte logical blocks: (480 GB/447 GiB)
[ 13.046177] sd 2:0:0:0: [sde] Write Protect is off
[ 13.046179] sd 2:0:0:0: [sde] Mode Sense: 00 3a 00 00
[ 13.046192] sd 2:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 13.046294] sdd:
[ 13.046325] sde: unknown partition table
[ 13.046905] unknown partition table
[ 13.047299] sd 2:0:0:0: [sde] Attached SCSI disk
[ 13.047310] sd 1:0:0:0: [sdd] Attached SCSI disk
[ 13.050485] scsi 6:0:0:0: CD-ROM TSSTcorp DVD-ROM TS-H353C LE01 PQ: 0 ANSI: 5
[toc] | [next] | [standalone]
| From | Sven Hartge <sven@svenhartge.de> |
|---|---|
| Date | 2019-03-24 21:50 +0100 |
| Message-ID | <xFie6-5X7-3@gated-at.bofh.it> |
| In reply to | #206551 |
Mimiko <vbvbrj@gmail.com> wrote: > I came across a problem when booting. In the server is installed 4 > disks connected to raid controller and 2 disks connected to > motherboard sata interfaces. During booting disks connected to raid > controller are detected before md raid assembling process, while the 2 > disks connected to motherboard sata interfaces are detected after md > raid assembly, so the raid made of this 2 disks are not detected and > assembled during boot. Add "rootdelay=10" to your Linux cmdline via /etc/default/grub. This normally solves the problem. S! -- Sigmentation fault. Core dumped.
[toc] | [prev] | [next] | [standalone]
| From | Mimiko <vbvbrj@gmail.com> |
|---|---|
| Date | 2019-03-25 18:30 +0100 |
| Message-ID | <xFBA5-XV-7@gated-at.bofh.it> |
| In reply to | #206554 |
On 24.03.2019 22:46, Sven Hartge wrote: >> I came across a problem when booting. In the server is installed 4 >> disks connected to raid controller and 2 disks connected to >> motherboard sata interfaces. During booting disks connected to raid >> controller are detected before md raid assembling process, while the 2 >> disks connected to motherboard sata interfaces are detected after md >> raid assembly, so the raid made of this 2 disks are not detected and >> assembled during boot. > Add "rootdelay=10" to your Linux cmdline via /etc/default/grub. This > normally solves the problem. This didn't help. Linux 2.6.32-5-amd64 #1 SMP Tue May 13 16:34:35 UTC 2014 x86_64 GNU/Linux
[toc] | [prev] | [next] | [standalone]
| From | Sven Hartge <sven@svenhartge.de> |
|---|---|
| Date | 2019-03-25 20:30 +0100 |
| Message-ID | <xFDsd-26I-5@gated-at.bofh.it> |
| In reply to | #206585 |
Mimiko <vbvbrj@gmail.com> wrote: > Linux 2.6.32-5-amd64 #1 SMP Tue May 13 16:34:35 UTC 2014 x86_64 GNU/Linux Please update your system, Debian 6.0 Squeeze is severely out of date and should NOT be used for any production systems and even less when connected to the public Internet. Grüße, Sven -- Sigmentation fault. Core dumped.
[toc] | [prev] | [next] | [standalone]
| From | John Hasler <jhasler@newsguy.com> |
|---|---|
| Date | 2019-03-25 21:30 +0100 |
| Message-ID | <xFEoi-2G2-13@gated-at.bofh.it> |
| In reply to | #206587 |
> Please update your system, Debian 6.0 Squeeze is severely out of date > and should NOT be used for any production systems and even less when > connected to the public Internet. It certainly should not be connected to the Internet but there is no reason not to keep using it for off-line systems where it still works. -- John Hasler jhasler@newsguy.com Elmwood, WI USA
[toc] | [prev] | [next] | [standalone]
| From | Mimiko <vbvbrj@gmail.com> |
|---|---|
| Date | 2019-03-26 07:20 +0100 |
| Message-ID | <xFNBg-8kX-3@gated-at.bofh.it> |
| In reply to | #206587 |
On 25.03.2019 21:23, Sven Hartge wrote: > Please update your system, Debian 6.0 Squeeze is severely out of date > and should NOT be used for any production systems and even less when > connected to the public Internet. Yes I know. But this is not the answer I'm searching.
[toc] | [prev] | [next] | [standalone]
| From | Sven Hartge <sven@svenhartge.de> |
|---|---|
| Date | 2019-03-26 17:50 +0100 |
| Message-ID | <xFXqW-5KA-9@gated-at.bofh.it> |
| In reply to | #206600 |
Mimiko <vbvbrj@gmail.com> wrote: > On 25.03.2019 21:23, Sven Hartge wrote: >> Please update your system, Debian 6.0 Squeeze is severely out of date >> and should NOT be used for any production systems and even less when >> connected to the public Internet. > Yes I know. But this is not the answer I'm searching. I know rootdelay=X works in Jessie and newer. I can't answer for older releases. S! -- Sigmentation fault. Core dumped.
[toc] | [prev] | [next] | [standalone]
| From | "Alexander V. Makartsev" <avbetev@gmail.com> |
|---|---|
| Date | 2019-03-26 17:50 +0100 |
| Message-ID | <xFXqW-5KA-7@gated-at.bofh.it> |
| In reply to | #206551 |
[Multipart message — attachments visible in raw view] — view raw
On 25.03.2019 0:50, Mimiko wrote: > hello. > > I came across a problem when booting. In the server is installed 4 > disks connected to raid controller and 2 disks connected to > motherboard sata interfaces. During booting disks connected to raid > controller are detected before md raid assembling process, while the 2 > disks connected to motherboard sata interfaces are detected after md > raid assembly, so the raid made of this 2 disks are not detected and > assembled during boot. > > From log is seen that sdd and sde a detected after mdamd is started to > assembly the raids. > > How can I force those 2 disks to be detected before mdadm? > > This is the log: Have you tried to use "/etc/modprobe.d/*.conf"-way to assign module dependency for mdadm? $ sudo modprobe -nD md-mod insmod /lib/modules/4.15.0-0.bpo.2-amd64/kernel/drivers/md/md-mod.ko start_ro=1 $ echo "softdep md_mod pre: libata libahci scsi_mod mpt3sas" | sudo tee /etc/modprobe.d/md-mod.conf $ sudo modprobe -nD md-mod insmod /lib/modules/4.15.0-0.bpo.2-amd64/kernel/drivers/scsi/scsi_mod.ko insmod /lib/modules/4.15.0-0.bpo.2-amd64/kernel/drivers/ata/libata.ko insmod /lib/modules/4.15.0-0.bpo.2-amd64/kernel/drivers/scsi/scsi_mod.ko insmod /lib/modules/4.15.0-0.bpo.2-amd64/kernel/drivers/ata/libata.ko insmod /lib/modules/4.15.0-0.bpo.2-amd64/kernel/drivers/ata/libahci.ko insmod /lib/modules/4.15.0-0.bpo.2-amd64/kernel/drivers/scsi/scsi_mod.ko insmod /lib/modules/4.15.0-0.bpo.2-amd64/kernel/drivers/scsi/scsi_mod.ko insmod /lib/modules/4.15.0-0.bpo.2-amd64/kernel/drivers/scsi/scsi_transport_sas.ko insmod /lib/modules/4.15.0-0.bpo.2-amd64/kernel/drivers/scsi/raid_class.ko insmod /lib/modules/4.15.0-0.bpo.2-amd64/kernel/drivers/scsi/mpt3sas/mpt3sas.ko insmod /lib/modules/4.15.0-0.bpo.2-amd64/kernel/drivers/md/md-mod.ko start_ro=1 You should get the idea. I think for your system you will need to change module "mpt3sas" to "mptsas" and/or "mptbase". After adding config file you will have to also update initramfs with: $ sudo update-initramfs -u I didn't tested this suggestion and you might break your system, so be prepared to boot from livecd to rollback changes, but because your root filesystem is on other disks I think it should be ok and hopefully your system will boot normally. There is also a possibility that "softdep" feature of kmod is not yet implemented on your old system and this suggestion won't work. -- With kindest regards, Alexander. ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org ⠈⠳⣄⠀⠀⠀⠀
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.user
csiph-web