SOS!!!!!Grub not loading after pass BIOS POST

    • SOS!!!!!Grub not loading after pass BIOS POST

      Hi OMV Guru

      please try to understand my English , I am not native speaker . I need help of my box .
      My omv suddenly not able to boot normally after I replaced one of the hard drive sata cable due to system was not able to detect it .

      this is my hard disks show in BIOS, sata port 1 is the boot disk
      pic1

      stuck in this prompt , not able to load grub page
      pic2

      however, I can see grub.cfg when i boot the USB "super grub2 disk " and I can select the kernel and boot omv in this way .
      pic3

      does anyone even faced the same issue ? please help me to solve it , I need to connect monitor every time when need to power-on OMV . ||
      if any config file needed for T-shoot , please leave a message , i will post ASAP , thank you <3
      AMD E240 @4.1.23-1
    • fdisk -l output

      Source Code

      1. root@K-NAS:/boot/grub# fdisk -l
      2. Disk /dev/sda: 149.1 GiB, 160041885696 bytes, 312581808 sectors
      3. Units: sectors of 1 * 512 = 512 bytes
      4. Sector size (logical/physical): 512 bytes / 512 bytes
      5. I/O size (minimum/optimal): 512 bytes / 512 bytes
      6. Disklabel type: dos
      7. Disk identifier: 0x76e85cf5
      8. Device Boot Start End Sectors Size Id Type
      9. /dev/sda1 2048 68601855 68599808 32.7G 83 Linux
      10. /dev/sda2 131000320 312580095 181579776 86.6G 83 Linux
      11. /dev/sda3 68601856 131000319 62398464 29.8G 83 Linux
      12. Partition table entries are not in disk order.
      13. Disk /dev/sdc: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
      14. Units: sectors of 1 * 512 = 512 bytes
      15. Sector size (logical/physical): 512 bytes / 512 bytes
      16. I/O size (minimum/optimal): 512 bytes / 512 bytes
      17. Disklabel type: dos
      18. Disk identifier: 0x90909090
      19. Device Boot Start End Sectors Size Id Type
      20. /dev/sdc1 2048 1953523711 1953521664 931.5G 83 Linux
      21. Disk /dev/sdd: 298.1 GiB, 320072933376 bytes, 625142448 sectors
      22. Units: sectors of 1 * 512 = 512 bytes
      23. Sector size (logical/physical): 512 bytes / 512 bytes
      24. I/O size (minimum/optimal): 512 bytes / 512 bytes
      25. Disklabel type: gpt
      26. Disk identifier: 201F70E4-DB78-4C1D-AF8A-B6170040F179
      27. Device Start End Sectors Size Type
      28. /dev/sdd1 2048 625142414 625140367 298.1G Linux filesystem
      29. Disk /dev/sdb: 74.5 GiB, 80026361856 bytes, 156301488 sectors
      30. Units: sectors of 1 * 512 = 512 bytes
      31. Sector size (logical/physical): 512 bytes / 512 bytes
      32. I/O size (minimum/optimal): 512 bytes / 512 bytes
      33. Disklabel type: dos
      34. Disk identifier: 0x00000000
      35. Device Boot Start End Sectors Size Id Type
      36. /dev/sdb1 * 2048 1050623 1048576 512M b W95 FAT32
      37. /dev/sdb2 1050624 148707327 147656704 70.4G 83 Linux
      38. /dev/sdb3 148707328 156301311 7593984 3.6G 82 Linux swap / Solaris
      39. Disk /dev/sde: 596.2 GiB, 640135028736 bytes, 1250263728 sectors
      40. Units: sectors of 1 * 512 = 512 bytes
      41. Sector size (logical/physical): 512 bytes / 512 bytes
      42. I/O size (minimum/optimal): 512 bytes / 512 bytes
      43. Disklabel type: dos
      44. Disk identifier: 0x375694cc
      Display All
      AMD E240 @4.1.23-1
    • kitkit210 wrote:

      fdisk -l output

      Source Code

      1. root@K-NAS:/boot/grub# fdisk -l
      2. Disk /dev/sda: 149.1 GiB, 160041885696 bytes, 312581808 sectors
      3. Units: sectors of 1 * 512 = 512 bytes
      4. Sector size (logical/physical): 512 bytes / 512 bytes
      5. I/O size (minimum/optimal): 512 bytes / 512 bytes
      6. Disklabel type: dos
      7. Disk identifier: 0x76e85cf5
      8. Device Boot Start End Sectors Size Id Type
      9. /dev/sda1 2048 68601855 68599808 32.7G 83 Linux
      10. /dev/sda2 131000320 312580095 181579776 86.6G 83 Linux
      11. /dev/sda3 68601856 131000319 62398464 29.8G 83 Linux
      12. Partition table entries are not in disk order.
      13. Disk /dev/sdc: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
      14. Units: sectors of 1 * 512 = 512 bytes
      15. Sector size (logical/physical): 512 bytes / 512 bytes
      16. I/O size (minimum/optimal): 512 bytes / 512 bytes
      17. Disklabel type: dos
      18. Disk identifier: 0x90909090
      19. Device Boot Start End Sectors Size Id Type
      20. /dev/sdc1 2048 1953523711 1953521664 931.5G 83 Linux
      21. Disk /dev/sdd: 298.1 GiB, 320072933376 bytes, 625142448 sectors
      22. Units: sectors of 1 * 512 = 512 bytes
      23. Sector size (logical/physical): 512 bytes / 512 bytes
      24. I/O size (minimum/optimal): 512 bytes / 512 bytes
      25. Disklabel type: gpt
      26. Disk identifier: 201F70E4-DB78-4C1D-AF8A-B6170040F179
      27. Device Start End Sectors Size Type
      28. /dev/sdd1 2048 625142414 625140367 298.1G Linux filesystem
      29. Disk /dev/sdb: 74.5 GiB, 80026361856 bytes, 156301488 sectors
      30. Units: sectors of 1 * 512 = 512 bytes
      31. Sector size (logical/physical): 512 bytes / 512 bytes
      32. I/O size (minimum/optimal): 512 bytes / 512 bytes
      33. Disklabel type: dos
      34. Disk identifier: 0x00000000
      35. Device Boot Start End Sectors Size Id Type
      36. /dev/sdb1 * 2048 1050623 1048576 512M b W95 FAT32
      37. /dev/sdb2 1050624 148707327 147656704 70.4G 83 Linux
      38. /dev/sdb3 148707328 156301311 7593984 3.6G 82 Linux swap / Solaris
      39. Disk /dev/sde: 596.2 GiB, 640135028736 bytes, 1250263728 sectors
      40. Units: sectors of 1 * 512 = 512 bytes
      41. Sector size (logical/physical): 512 bytes / 512 bytes
      42. I/O size (minimum/optimal): 512 bytes / 512 bytes
      43. Disklabel type: dos
      44. Disk identifier: 0x375694cc
      Display All
      Was your OS disk the only disk connected to the motherboard, other than the install disk? Almost seems like Grub got installed to the wrong drive. If you disconnect all drives but the OS drive, does it boot?

      You should be able to use the super grub disk to reinstall grub to the proper disk, if that's the case.
      Air Conditioners are a lot like PC's... They work great until you open Windows.

    • KM0201 wrote:

      kitkit210 wrote:

      fdisk -l output

      Source Code

      1. root@K-NAS:/boot/grub# fdisk -l
      2. Disk /dev/sda: 149.1 GiB, 160041885696 bytes, 312581808 sectors
      3. Units: sectors of 1 * 512 = 512 bytes
      4. Sector size (logical/physical): 512 bytes / 512 bytes
      5. I/O size (minimum/optimal): 512 bytes / 512 bytes
      6. Disklabel type: dos
      7. Disk identifier: 0x76e85cf5
      8. Device Boot Start End Sectors Size Id Type
      9. /dev/sda1 2048 68601855 68599808 32.7G 83 Linux
      10. /dev/sda2 131000320 312580095 181579776 86.6G 83 Linux
      11. /dev/sda3 68601856 131000319 62398464 29.8G 83 Linux
      12. Partition table entries are not in disk order.
      13. Disk /dev/sdc: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
      14. Units: sectors of 1 * 512 = 512 bytes
      15. Sector size (logical/physical): 512 bytes / 512 bytes
      16. I/O size (minimum/optimal): 512 bytes / 512 bytes
      17. Disklabel type: dos
      18. Disk identifier: 0x90909090
      19. Device Boot Start End Sectors Size Id Type
      20. /dev/sdc1 2048 1953523711 1953521664 931.5G 83 Linux
      21. Disk /dev/sdd: 298.1 GiB, 320072933376 bytes, 625142448 sectors
      22. Units: sectors of 1 * 512 = 512 bytes
      23. Sector size (logical/physical): 512 bytes / 512 bytes
      24. I/O size (minimum/optimal): 512 bytes / 512 bytes
      25. Disklabel type: gpt
      26. Disk identifier: 201F70E4-DB78-4C1D-AF8A-B6170040F179
      27. Device Start End Sectors Size Type
      28. /dev/sdd1 2048 625142414 625140367 298.1G Linux filesystem
      29. Disk /dev/sdb: 74.5 GiB, 80026361856 bytes, 156301488 sectors
      30. Units: sectors of 1 * 512 = 512 bytes
      31. Sector size (logical/physical): 512 bytes / 512 bytes
      32. I/O size (minimum/optimal): 512 bytes / 512 bytes
      33. Disklabel type: dos
      34. Disk identifier: 0x00000000
      35. Device Boot Start End Sectors Size Id Type
      36. /dev/sdb1 * 2048 1050623 1048576 512M b W95 FAT32
      37. /dev/sdb2 1050624 148707327 147656704 70.4G 83 Linux
      38. /dev/sdb3 148707328 156301311 7593984 3.6G 82 Linux swap / Solaris
      39. Disk /dev/sde: 596.2 GiB, 640135028736 bytes, 1250263728 sectors
      40. Units: sectors of 1 * 512 = 512 bytes
      41. Sector size (logical/physical): 512 bytes / 512 bytes
      42. I/O size (minimum/optimal): 512 bytes / 512 bytes
      43. Disklabel type: dos
      44. Disk identifier: 0x375694cc
      Display All
      Was your OS disk the only disk connected to the motherboard, other than the install disk? Almost seems like Grub got installed to the wrong drive. If you disconnect all drives but the OS drive, does it boot?
      You should be able to use the super grub disk to reinstall grub to the proper disk, if that's the case.
      will try once I back home
      AMD E240 @4.1.23-1
    • KM0201 wrote:

      Was your OS disk the only disk connected to the motherboard, other than the install disk? Almost seems like Grub got installed to the wrong drive. If you disconnect all drives but the OS drive, does it boot?
      You should be able to use the super grub disk to reinstall grub to the proper disk, if that's the case.
      after install grub-pc , the grub menu appear again , but new issue occurred :whistling: - not able to boot to OS , will upload pic soon
      AMD E240 @4.1.23-1
    • Hello,

      Sorry for my english.

      I have the same problem since thursday.
      After the BIOS, Grub does not appear and i have a binking cursor. no boot to OMV. Same problem, if i disconnect all my data disk.
      I have remove my OS disk and replaced it by my backup OS disk, and it boot directly.

      The defective disk is readable. I can mount it via USB on my other pc. In attach the boot info result, On this report, the OMV disk is sdg.

      The last update made was the package "base-files 9.9+deb9u11".

      Can you help me with this disk ?
      Files
      • bootinfo.txt

        (43.4 kB, downloaded 7 times, last: )
    • Hi Telev

      Quite the same like me , My problem is solved .

      Just for your reference.

      I used "super grub2 disk" tried to boot to the defective disk and it is OK .

      like KM0201 recommended , after enter OS , I installed grub-pc and select the boot disk , and everything ok now .


      Telev wrote:

      Hello,

      Sorry for my english.

      I have the same problem since thursday.
      After the BIOS, Grub does not appear and i have a binking cursor. no boot to OMV. Same problem, if i disconnect all my data disk.
      I have remove my OS disk and replaced it by my backup OS disk, and it boot directly.

      The defective disk is readable. I can mount it via USB on my other pc. In attach the boot info result, On this report, the OMV disk is sdg.

      The last update made was the package "base-files 9.9+deb9u11".

      Can you help me with this disk ?
      AMD E240 @4.1.23-1
    • the new issue was caused by a broken PCI SATA Card , after removing from the motherboard ,everything is ok :D :thumbsup: :thumbup:

      kitkit210 wrote:


      KM0201 wrote:

      Was your OS disk the only disk connected to the motherboard, other than the install disk? Almost seems like Grub got installed to the wrong drive. If you disconnect all drives but the OS drive, does it boot?
      You should be able to use the super grub disk to reinstall grub to the proper disk, if that's the case.
      after install grub-pc , the grub menu appear again , but new issue occurred :whistling: - not able to boot to OS , will upload pic soon
      AMD E240 @4.1.23-1
    • Users Online 2

      2 Guests