You can find everything about the LSI system I described at this link: https://www.fujitsu.com/global/imagesgig5/b7fy-2331-01en.pdf (see page 59). Maybe I didn't understand this software well or maybe I should have found an old page of Fujitsu.com that no longer exists and that would have helped me manage the configuration of LSI for Linux. The AI recommended me a very long manual configuration procedure in which Grub was installed after I had installed /boot on each of the two hard drives and had partitioned each disk identically. However, when I restarted the computer I had the diagnostic "Operating System not found". Probably because every type of RAID, with that manual configuration, had disappeared. Maybe it would have been enough to recreate it and restart the computer? I also tried to correct everything from the console: a nightmare, one error after another, keyboard map messed up, etc. Without touching anything, on this computer, both with a single hard disk and with two hard disks, before the failure of compiling a C++ source code of an ssh, I installed Debian 12 automatically by letting the Debian installer do everything, and everything worked wonderfully. I did the same thing for another server: I inserted two SAS hard disks in the bay, I started the Debian installer and it did everything by itself perfectly. I don't understand if I'm doing something wrong and where...
CPA ________________________________ Da: Titus Newswanger Inviato: Giovedì, 24 Aprile, 2025 01:35 A: debian-user@lists.debian.org Oggetto: Re: R: Grub problem On 4/23/25 18:07, Pier Antonio Corradini wrote: > I tried everything: the BIOS does not see any hard disk (single or in > pair with its own twin) if you do not first configure, in the LSI > environment, either a RAID 0 So it is some kind of LSI RAID card. What Brand? model? Some of that info should be visible in your "LSI environment" (I think you mean the LSI bios menu?) which, I think, might be a separate bios menu from that of the main motherboard, accessible via some keyboard shortcut during startup. The HDDs are not visible to the os until you configure your RAID device in the LSI bios. Then you install your os to that RAID device as a normal install. The os will not know it is running on a RAID AFAIK. I think on one system like this, I needed to go into that LSI configuration, delete my RAID, initialize the hard disks, then set up a new RAID, after a corrupted install. After that, my os install completed successfully. Doing all that destroys all data you may have on those hard drives. However, in case of a failed new os install that is usually no concern. > (when there is only one hard disk) or a RAID 1 (when there are two > hard disks). Leaving Debian 12 to do the partitioning does not create > /boot and therefore the Grub installation fails. If you create /boot > (and all the other partitions) manually, Grub is installed but the > operating system does not load and when you turn it back on, the RAID > no longer exists in the loading console. Moreover, if you create, in > the partitioning, a vg0 unit, the individual partitions already made > are transformed into others and the entire newly created structure is > destroyed and the new one becomes unchangeable. > A real nightmare! > PA > -- Titus Newswanger Curtiss WI
