| View previous topic :: View next topic |
| Author |
Message |
Anton Gubarkov
n00b
Joined: 13 Mar 2008
Posts: 65
|
 Posted: Fri Nov 24, 2017 1:16 pm Post subject: Grub 2.02 can't see SATA disks connected to Adaptec 1000-8i |
 |
|
Decided to build myself a NAS.
Adaptec 1000-8i connects 6 Seagate Ironwolf disks.
When I boot from a rescue CD, the adapter driver is loaded (aacraid) and the disks are recognized.
I've build my ZFS pool and copied my system to it. I've mounted the EFI system partition (located on the SSD connected via a standard Intel SATA controller on motheboard) and re-installed grub. I've also re-generated grub.cfg with grub-mkconfig.
dracut-generated initramfs was updated as well to include zfs modules.
When I rebooted, grub couldn't find the zfs boot dataset. I started to investigate and I found out that grub can't see any of the disks connected to the Adaptec controller. ls command showed only the disk connected to Intel SATA controller on motherboard.
I have rather old Gigabyte P67-D3-B3 mb in UEFI mode. Is it a bug in the UEFI or in Grub?
Any recommendations are welcome. |
|
| Back to top |
|
 |
Roman_Gruber
Advocate
Joined: 03 Oct 2006
Posts: 3846
Location: Austro Bavaria
|
| Posted: Fri Nov 24, 2017 4:08 pm Post subject: |
|
|
| It's Good that a rescue CD works. So you just need to reuse its config and rebuild your kernel. Build in the hardware driver for your hardware in the kernel. |
|
| Back to top |
|
|
krinn
Watchman
Joined: 02 May 2003
Posts: 7470
|
| Posted: Fri Nov 24, 2017 4:15 pm Post subject: |
|
|
After bios is loaded and before grub is loaded, the adaptec should load its own bios, which will register drives attach to it.
If your card doesn't have any bios, no m/b will be able to boot from disks attach to it.
If your card have a bios, loaded it, init drives... and you aren't able to see disks, it must be grub (however i use grub:0 and it works flawlessly)
If your card have a bios, it doesn't load, your m/b might have an option to prevent it (check m/b bios options) ; if your m/b doesn't' have any option to prevent it, it's a shitty m/b bios |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54236
Location: 56N 3W
|
| Posted: Fri Nov 24, 2017 8:40 pm Post subject: |
|
|
krinn,
What you say about BIOS is 100% spot on but UEFI is in use here.
I don't know how UEFI identifies plug in boards and boots from them.
Is UEFI the same?
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
krinn
Watchman
Joined: 02 May 2003
Posts: 7470
|
| Posted: Sat Nov 25, 2017 12:55 am Post subject: |
|
|
| NeddySeagoon wrote: | krinn,
What you say about BIOS is 100% spot on but UEFI is in use here.
I don't know how UEFI identifies plug in boards and boots from them.
Is UEFI the same? |
It's how my UEFI bios handle it, just the same way as before (with non-EUFI one).
What is going on is that BIOS or EUFI one, boot & init its internal device (sata, net...) ; let's say at this point drive 80, 81 are define by bios
And prior reaching the <press f8 to choose boot device, f2 to enter bios> part, the adaptec bios is loaded, it init the card, find the drives and register then. This create drive 82, 83...
Once you enter bios with f2 or use f8, the propose drives are 80,81,82,83
On my UEFI bios it's even better because the UEFI bios also point which card handle which drives, something like: adaptec1505_cheetah (which is not name of my disk, but the name of the array), intel_sata_WD200... making the selection quiet easy. |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54236
Location: 56N 3W
|
| Posted: Sat Nov 25, 2017 7:44 pm Post subject: |
|
|
krinn,
I don't have any UEFI systems yet.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
|
Other Things Gentoo
