Good time, dear forum users. I had a problem in solving which I ask for your help. The problem is the following: on the motherboard the SATA controller died, I put the RAID card SiI 3114, connected a hard disk to it, reconfigured the fstab using the LiveCD (replaced the UUID with the device names), changed the hard disk name to / dev / sda6 ( this is my root), but the system still does not start, gives the following:

alt text

I suspect that the problem is that the system does not know which drivers to use for this controller.

I attach the screen breakdown HDD
alt text

Here I am attaching fstab and lilo.conf:
fstab

proc /proc proc nosuid,noexec,gid=proc 0 0 devpts /dev/pts devpts nosuid,noexec,gid=tty,mode=620 0 0 tmpfs /tmp tmpfs nosuid 0 0 /dev/sda6 / ext3 relatime 1 1 /dev/sda8 /home ext3 nosuid,relatime 1 2 /dev/sda7 swap swap defaults 0 0 /dev/sr0 /media/cdrom udf,iso9660 ro,noauto,user,utf8 0 0 /dev/sda9 /opt ext3 relatime 1 1

lilo.conf

 map="/boot/map" lba32 prompt compact vga="0x314" boot="/dev/sda" timeout="50" install="menu" message="/boot/splash/message" append="resume=/dev/sda7 panic=30 splash=silent" 
 

  default = "Windows1" 


  default = "ALTLinux" 

  image = "/ boot / vmlinuz"
     label = "ALTLinux"
     initrd = "/ boot / initrd.img"
     root = "/ dev / sda6"
     read-only 

  image = "/ boot / vmlinuz"
     label = "failsafe"
     initrd = "/ boot / initrd.img"
     root = "/ dev / sda6"
     addappend = "failsafe"
     vga = "normal"
     read-only 

 other="/dev/disk/by-id/ata-WDC_WD3200AAKS-00V1A0_WD-WMAWF0600635-part1" label="Windows1" image="/boot/memtest-4.00.bin" label="memtest" image="/boot/vmlinuz-2.6.30-std-def-alt14" initrd="/boot/initrd-2.6.30-std-def-alt14.img" label="2630-std-def-14" root="/dev/sda6" read-only optional image="/boot/vmlinuz-2.6.32-std-def-alt20.M50P.1" initrd="/boot/initrd-2.6.32-std-def-alt20.M50P.1.img" label="2632-std-def-20M50P1" root="/dev/sda6" read-only optional

If you turn off swap in fstab, then the same error occurs.

  • who is / dev / sda7? boot from live, create mount points, mount volumes manually. so you will find out if there really are volumes;) - niXman
  • I already did this: boot from live, mounted the HDD root partition, changed fstab and lilo.conf (in them I changed UUIDs to device names: / dev / sda6 - /, / dev / sda7 - swp, / dev / sda8 - / home ), then did: chroot / dev / sda6 lilo - Andrey Kozhaev
  • I'm sorry, I did not immediately understand your question. / dev / sda7 is the swap partition. When booting from live, these partitions are mounted normally and the data on them all remains the same - Andrey Kozhaev
  • What kind of a swap, if the OS says that it is not. check again, maybe that messed up. - niXman
  • Added HDD markup screen - Andrey Kozhaev

3 answers 3

Sorry for the indiscreet question. Did you perform / sbin / lilo well? If not, boot, for example, from a CD into GNU / linux and then try the following:

  1. Run mount without parameters (remember all proc, sys, dev ... virtual file systems).
  2. Mount your root on / mnt, mount to / mnt all your partitions that you have mounted during normal boot to the root (that is, / home, for example, you should become / mnt / home). With virtual file systems, we do almost the same thing, but otherwise we mount mount points to directories inside / mnt, so with proc, we proceed like this: mount --bind /proc /mnt/proc and according to this principle with each virtual file system.
  3. Making root substitution: chroot /mnt . Now you are in your system, not in life-cd.
  4. Run / sbin / lilo: lilo .
  5. Exit your system if nothing else is needed (for example, you can change lilo to GRUB): exit .
  6. Unmount everything with the command: umount .
  7. Reboot: reboot .
  8. Boot from hard disk.
  • Well, I did it all, except that I did not mount / home and / opt. But the mounting of these additional sections did not help either :( - Andrey Kozhaev
  • Yes. It’s time for a GRUB change. - Alexey Kotov
  • Solidarity. Give GRUB to the masses. - gecube
  • one
    Well, I don't know. It happens that lilo correctly finds the kernel but gives it incorrect information about where the root is, but if this is not your case, but there is no support for your controller, then, as an option, we do all of the above but rebuild kernel linux before executing / sbin / lilo (the components necessary for loading can be turned on monolithically) and we collect the initrd (if necessary). PS You can also add a volume label for your / dev / sda6 and instead of root = / dev / sda6 root = "LABEL = YOUR_TAG". - modal

Is it possible to fstab? As far as I have seen, it swears only on / dev / sda7. If you do not mount Swap (ie, sda7), does it start swearing at the next section?

  • The parameter resume = ... is used to return from deep sleep. Can be removed if not used. The error about / dev / sda7 comes even while the boot loader is running. Only here most likely modal rights. If with lilo order - this problem should not have been. - Alexey Kotov

The problem with the launch is solved. The solution suggested "asy", it was necessary to correct the initrd. Full version of the topic here
Thank you all for your help.