BSOD, MBR поврежден, попытался исправить с помощью Testdisk на Linux с двойной загрузкой, теперь ничего не работает

1318
Michael

Короче говоря, я получил BSOD от программы Windows. Я тогда не мог загрузить Windows. Моя система настроена на GRUB для двойной загрузки в CentOS, поэтому я загрузился в CentOS и попытался исправить MBR с помощью TestDisk. Теперь я не могу загрузить ни ОС, ни GRUB. Я могу просматривать файлы с помощью TestDisk с LiveCD, чтобы видеть, что они все еще там. Ниже приведен вывод из bootinfoscript и fdisk -l, запущенного из Fedora LiveCD.

В настоящее время, когда я загружаюсь с жесткого диска, я получаю приглашение «Ошибка жесткого диска», вот и все.

sdd - это жесткий диск с разделами Windows и Linux. Там написано, что GRUB установлен, но я не загружаюсь. Я попытался «проанализировать» и «более глубокий поиск» с помощью testdisk, и я забыл точную ошибку, но не смог найти таблицу.

Таблица выглядит хорошо, хотя в соответствии с bootinfoscript.

Пожалуйста, как я могу это исправить? Должен быть способ!

редактировать: я попытался загрузить установочный диск Windows 7 и режим восстановления не видит его раздел. Аддитально в режиме восстановления CentOS не видит своего раздела.

bootinfoscript:

 Boot Info Script 0.61 [1 April 2012]   ============================= Boot Info Summary: ===============================  => Windows is installed in the MBR of /dev/sda. => Grub Legacy (v0.97) is installed in the MBR of /dev/sdc and looks on boot  drive #1 in partition #3 for /grub/stage2 and /grub/grub.conf. => Testdisk is installed in the MBR of /dev/sdd. => Windows is installed in the MBR of /dev/sde.  sda1: __________________________________________________________________________  File system:  Boot sector type: - Boot sector info:  Mounting failed: mount: unknown filesystem type ''  sdc1: __________________________________________________________________________  File system: ntfs Boot sector type: Grub Legacy Boot sector info: Grub Legacy (v0.97) is installed in the boot sector  of sdc1 and looks at sector 1 on boot drive #119 for  the stage2 file. A stage2 file is at this location on  /dev/sdd. Stage2 looks on the same partition for  /grub/stage2. No errors found in the Boot Parameter  Block. Mounting failed: mount: unknown filesystem type '' Failed to read last sector (1953534081): Invalid argument HINTS: Either the volume is a RAID/LDM but it wasn't setup yet, or it was not setup correctly (e.g. by not using mdadm --build ...), or a wrong device is tried to be mounted, or the partition table is corrupt (partition is smaller than NTFS), or the NTFS boot sector is corrupt (NTFS size is not valid). Failed to mount '/dev/sdc1': Invalid argument The device '/dev/sdc1' doesn't seem to have a valid NTFS. Maybe the wrong device is used? Or the whole disk instead of a partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around? Failed to read last sector (1953534081): Invalid argument HINTS: Either the volume is a RAID/LDM but it wasn't setup yet, or it was not setup correctly (e.g. by not using mdadm --build ...), or a wrong device is tried to be mounted, or the partition table is corrupt (partition is smaller than NTFS), or the NTFS boot sector is corrupt (NTFS size is not valid). Failed to mount '/dev/sdc1': Invalid argument The device '/dev/sdc1' doesn't seem to have a valid NTFS. Maybe the wrong device is used? Or the whole disk instead of a partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?  sdd1: __________________________________________________________________________  File system: ntfs Boot sector type: Grub Legacy Boot sector info: Grub Legacy (v0.97) is installed in the boot sector  of sdd1 and looks at sector 1 on boot drive #119 for  the stage2 file. A stage2 file is at this location on  /dev/sdd. Stage2 looks on the same partition for  /grub/stage2. No errors found in the Boot Parameter  Block. Operating System:  Boot files: /bootmgr /Boot/BCD  sdd2: __________________________________________________________________________  File system: ntfs Boot sector type: Grub Legacy Boot sector info: Grub Legacy (v0.97) is installed in the boot sector  of sdd2 and looks at sector 1 on boot drive #119 for  the stage2 file. A stage2 file is at this location on  /dev/sdd. Stage2 looks on the same partition for  /grub/stage2. No errors found in the Boot Parameter  Block. Operating System:  Boot files:   sdd3: __________________________________________________________________________  File system: ext4 Boot sector type: Grub Legacy Boot sector info: Grub Legacy (v) is installed in the boot sector of  sdd3 and looks at sector 977307854 of the same hard  drive for the stage2 file, but no stage2 files can be  found at this location. Operating System:  Boot files: /grub/menu.lst /grub/grub.conf  sdd4: __________________________________________________________________________  File system: Extended Partition Boot sector type: Grub Legacy Boot sector info: Grub Legacy (v0.97) is installed in the boot sector  of sdd4 and looks at sector 977306630 of the same hard  drive for the stage2 file. A stage2 file is at this  location on /dev/sdd. Stage2 looks on partition #3  for /grub/grub.conf.  sdd5: __________________________________________________________________________  File system: LVM2_member Boot sector type: Grub Legacy Boot sector info: Grub Legacy (v0.97) is installed in the boot sector  of sdd5 and looks at sector 977307806 of the same hard  drive for the stage2 file. A stage2 file is at this  location on /dev/sdd. Stage2 looks on partition #3  for /grub/grub.conf.  sde1: __________________________________________________________________________  File system: ntfs Boot sector type: Windows Vista/7: NTFS Boot sector info: According to the info in the boot sector, sde1 has  625137663 sectors, but according to the info from  fdisk, it has 625151361 sectors. Operating System: Windows 7 Boot files: /Windows/System32/winload.exe  vg_mikenix-lv_root': ___________________________________________________________  File system:  Boot sector type: Unknown Boot sector info:  Mounting failed: mount: unknown filesystem type '' Failed to read last sector (1953534081): Invalid argument HINTS: Either the volume is a RAID/LDM but it wasn't setup yet, or it was not setup correctly (e.g. by not using mdadm --build ...), or a wrong device is tried to be mounted, or the partition table is corrupt (partition is smaller than NTFS), or the NTFS boot sector is corrupt (NTFS size is not valid). Failed to mount '/dev/sdc1': Invalid argument The device '/dev/sdc1' doesn't seem to have a valid NTFS. Maybe the wrong device is used? Or the whole disk instead of a partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around? Failed to read last sector (1953534081): Invalid argument HINTS: Either the volume is a RAID/LDM but it wasn't setup yet, or it was not setup correctly (e.g. by not using mdadm --build ...), or a wrong device is tried to be mounted, or the partition table is corrupt (partition is smaller than NTFS), or the NTFS boot sector is corrupt (NTFS size is not valid). Failed to mount '/dev/sdc1': Invalid argument The device '/dev/sdc1' doesn't seem to have a valid NTFS. Maybe the wrong device is used? Or the whole disk instead of a partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around? ntfs_mst_post_read_fixup_warn: magic: 0x454c4946 size: 4096 usa_ofs: 48 usa_count: 2: Invalid argument Actual VCN (0x1003800010004) of index buffer is different from expected VCN (0x0). ntfs_mst_post_read_fixup_warn: magic: 0x454c4946 size: 4096 usa_ofs: 48 usa_count: 2: Invalid argument Actual VCN (0x1003800010004) of index buffer is different from expected VCN (0x0). mount: unknown filesystem type ''  vg_mikenix-lv_home': ___________________________________________________________  File system:  Boot sector type: Unknown Boot sector info:  Mounting failed: mount: unknown filesystem type '' Failed to read last sector (1953534081): Invalid argument HINTS: Either the volume is a RAID/LDM but it wasn't setup yet, or it was not setup correctly (e.g. by not using mdadm --build ...), or a wrong device is tried to be mounted, or the partition table is corrupt (partition is smaller than NTFS), or the NTFS boot sector is corrupt (NTFS size is not valid). Failed to mount '/dev/sdc1': Invalid argument The device '/dev/sdc1' doesn't seem to have a valid NTFS. Maybe the wrong device is used? Or the whole disk instead of a partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around? Failed to read last sector (1953534081): Invalid argument HINTS: Either the volume is a RAID/LDM but it wasn't setup yet, or it was not setup correctly (e.g. by not using mdadm --build ...), or a wrong device is tried to be mounted, or the partition table is corrupt (partition is smaller than NTFS), or the NTFS boot sector is corrupt (NTFS size is not valid). Failed to mount '/dev/sdc1': Invalid argument The device '/dev/sdc1' doesn't seem to have a valid NTFS. Maybe the wrong device is used? Or the whole disk instead of a partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around? ntfs_mst_post_read_fixup_warn: magic: 0x454c4946 size: 4096 usa_ofs: 48 usa_count: 2: Invalid argument Actual VCN (0x1003800010004) of index buffer is different from expected VCN (0x0). ntfs_mst_post_read_fixup_warn: magic: 0x454c4946 size: 4096 usa_ofs: 48 usa_count: 2: Invalid argument Actual VCN (0x1003800010004) of index buffer is different from expected VCN (0x0). mount: unknown filesystem type '' mount: unknown filesystem type ''  vg_mikenix-lv_swap': ___________________________________________________________  File system:  Boot sector type: Unknown Boot sector info:  Mounting failed: mount: unknown filesystem type '' Failed to read last sector (1953534081): Invalid argument HINTS: Either the volume is a RAID/LDM but it wasn't setup yet, or it was not setup correctly (e.g. by not using mdadm --build ...), or a wrong device is tried to be mounted, or the partition table is corrupt (partition is smaller than NTFS), or the NTFS boot sector is corrupt (NTFS size is not valid). Failed to mount '/dev/sdc1': Invalid argument The device '/dev/sdc1' doesn't seem to have a valid NTFS. Maybe the wrong device is used? Or the whole disk instead of a partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around? Failed to read last sector (1953534081): Invalid argument HINTS: Either the volume is a RAID/LDM but it wasn't setup yet, or it was not setup correctly (e.g. by not using mdadm --build ...), or a wrong device is tried to be mounted, or the partition table is corrupt (partition is smaller than NTFS), or the NTFS boot sector is corrupt (NTFS size is not valid). Failed to mount '/dev/sdc1': Invalid argument The device '/dev/sdc1' doesn't seem to have a valid NTFS. Maybe the wrong device is used? Or the whole disk instead of a partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around? ntfs_mst_post_read_fixup_warn: magic: 0x454c4946 size: 4096 usa_ofs: 48 usa_count: 2: Invalid argument Actual VCN (0x1003800010004) of index buffer is different from expected VCN (0x0). ntfs_mst_post_read_fixup_warn: magic: 0x454c4946 size: 4096 usa_ofs: 48 usa_count: 2: Invalid argument Actual VCN (0x1003800010004) of index buffer is different from expected VCN (0x0). mount: unknown filesystem type '' mount: unknown filesystem type '' mount: unknown filesystem type ''  ============================ Drive/Partition Info: =============================  Drive: sda _____________________________________________________________________  Disk /dev/sda: 320.1 GB, 320072933376 bytes 255 heads, 63 sectors/track, 38913 cylinders, total 625142448 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes  Partition Boot Start Sector End Sector # of Sectors Id System  /dev/sda1 63 625,140,399 625,140,337 42 SFS   Drive: sdc _____________________________________________________________________  Disk /dev/sdc: 1000.2 GB, 1000204886016 bytes 255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes  Partition Boot Start Sector End Sector # of Sectors Id System  /dev/sdc1 2,048 1,953,536,129 1,953,534,082 7 NTFS / exFAT / HPFS  /dev/sdc1 ends after the last sector of /dev/sdc  Drive: sdd _____________________________________________________________________  Disk /dev/sdd: 1000.2 GB, 1000204886016 bytes 255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes  Partition Boot Start Sector End Sector # of Sectors Id System  /dev/sdd1 * 2,048 211,679 209,632 7 NTFS / exFAT / HPFS /dev/sdd2 206,848 976,767,119 976,560,272 7 NTFS / exFAT / HPFS /dev/sdd3 976,764,928 977,788,927 1,024,000 83 Linux /dev/sdd4 977,788,928 1,953,525,167 975,736,240 5 Extended /dev/sdd5 977,790,976 1,953,523,711 975,732,736 8e Linux LVM  /dev/sdd1 overlaps with /dev/sdd2 /dev/sdd2 overlaps with /dev/sdd3  Drive: sde _____________________________________________________________________  Disk /dev/sde: 320.1 GB, 320072933376 bytes 255 heads, 63 sectors/track, 38913 cylinders, total 625142448 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes  Partition Boot Start Sector End Sector # of Sectors Id System  /dev/sde1 * 2,048 625,153,409 625,151,362 7 NTFS / exFAT / HPFS  /dev/sde1 ends after the last sector of /dev/sde  "blkid" output: ________________________________________________________________  Device UUID TYPE LABEL  /dev/loop0 squashfs  /dev/loop1 DM_snapshot_cow  /dev/loop2 squashfs  /dev/loop3 b39d6418-8f98-4350-a48a-e70b0dd203f9 ext4 _Fedora-17-x86_6 /dev/mapper/live-osimg-min b39d6418-8f98-4350-a48a-e70b0dd203f9 ext4 _Fedora-17-x86_6 /dev/mapper/live-rw b39d6418-8f98-4350-a48a-e70b0dd203f9 ext4 _Fedora-17-x86_6 /dev/mapper/vg_mikenix-lv_home 52e59386-1ea4-4dd0-b94b-6b8dbe389358 ext4  /dev/mapper/vg_mikenix-lv_root 563ab476-602e-4c05-abb7-33b44a12d9fb ext4  /dev/mapper/vg_mikenix-lv_swap 342be5e7-dd8b-44e5-9e9f-c705e385ad4e swap  /dev/sdc1 80C2F69090FA0800 ntfs New Volume /dev/sdd1 80C2F69090FA0800 ntfs System Reserved /dev/sdd2 80C2F69090FA0800 ntfs  /dev/sdd3 34bfd48b-c8ca-41f3-a5cb-aa9991e98f2d ext4  /dev/sdd5 GxpmvW-powX-BiJ1-qaXB-SH9r-fuV3-WUeBef LVM2_member  /dev/sde1 EE524F21524EEDC1 ntfs  /dev/sr0 iso9660 Fedora-17-x86_64-Live-Desktop.is  ========================= "ls -R /dev/mapper/" output: =========================  /dev/mapper: control live-osimg-min live-rw vg_mikenix-lv_home vg_mikenix-lv_root vg_mikenix-lv_swap  ================================ Mount points: =================================  Device Mount_Point Type Options  /dev/mapper/live-rw / ext4 (rw,noatime,seclabel,user_xattr,barrier=1,data=ordered) /dev/sr0 /run/initramfs/live iso9660 (ro,relatime)   ============================= sdd3/grub/grub.conf: =============================  -------------------------------------------------------------------------------- # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd0,2) # kernel /vmlinuz-version ro root=/dev/mapper/vg_mikenix-lv_root # initrd /initrd-[generic-]version.img #boot=/dev/sdd default=2 timeout=5 splashimage=(hd0,2)/grub/splash.xpm.gz hiddenmenu title CentOS (2.6.32-279.1.1.el6.x86_64) root (hd0,2) kernel /vmlinuz-2.6.32-279.1.1.el6.x86_64 ro root=/dev/mapper/vg_mikenix-lv_root rd_NO_LUKS LANG=en_US.UTF-8 rd_LVM_LV=vg_mikenix/lv_swap rd_NO_MD SYSFONT=latarcyrheb-sun16 crashkernel=auto rd_LVM_LV=vg_mikenix/lv_root KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM rhgb quiet initrd /initramfs-2.6.32-279.1.1.el6.x86_64.img title CentOS (2.6.32-279.el6.x86_64) root (hd0,2) kernel /vmlinuz-2.6.32-279.el6.x86_64 ro root=/dev/mapper/vg_mikenix-lv_root rd_NO_LUKS LANG=en_US.UTF-8 rd_LVM_LV=vg_mikenix/lv_swap rd_NO_MD SYSFONT=latarcyrheb-sun16 crashkernel=auto rd_LVM_LV=vg_mikenix/lv_root KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM rhgb quiet initrd /initramfs-2.6.32-279.el6.x86_64.img title Windows 7 rootnoverify (hd0,0) chainloader +1 --------------------------------------------------------------------------------  =================== sdd3: Location of files loaded by Grub: ====================  GiB - GB File Fragment(s)  466.016604424 = 500.381518848 grub/grub.conf 1 466.016604424 = 500.381518848 grub/menu.lst 1 466.016795158 = 500.381723648 grub/stage2 1 465.821786880 = 500.172335104 initramfs-2.6.32-279.1.1.el6.x86_64.img 2 465.790484428 = 500.138724352 initramfs-2.6.32-279.el6.x86_64.img 2 465.826546669 = 500.177445888 initrd-2.6.32-279.1.1.el6.x86_64kdump.img 1 465.795757294 = 500.144386048 initrd-2.6.32-279.el6.x86_64kdump.img 1 465.804494858 = 500.153767936 vmlinuz-2.6.32-279.1.1.el6.x86_64 1 465.773245811 = 500.120214528 vmlinuz-2.6.32-279.el6.x86_64 1  ======================== Unknown MBRs/Boot Sectors/etc: ========================  Unknown BootLoader on vg_mikenix-lv_root'   Unknown BootLoader on vg_mikenix-lv_home'   Unknown BootLoader on vg_mikenix-lv_swap'    ========= Devices which don't seem to have a corresponding hard drive: =========  sdb   =============================== StdErr Messages: ===============================  ls: reading directory sdd2/: Input/output error One or more specified logical volume(s) not found. One or more specified logical volume(s) not found. One or more specified logical volume(s) not found. hexdump: /dev/mapper/vg_mikenix-lv_root': No such file or directory hexdump: stdin: Bad file descriptor hexdump: /dev/mapper/vg_mikenix-lv_root': No such file or directory hexdump: /dev/mapper/vg_mikenix-lv_root': Bad file descriptor One or more specified logical volume(s) not found. One or more specified logical volume(s) not found. One or more specified logical volume(s) not found. hexdump: /dev/mapper/vg_mikenix-lv_home': No such file or directory hexdump: stdin: Bad file descriptor hexdump: /dev/mapper/vg_mikenix-lv_home': No such file or directory hexdump: /dev/mapper/vg_mikenix-lv_home': Bad file descriptor One or more specified logical volume(s) not found. One or more specified logical volume(s) not found. One or more specified logical volume(s) not found. hexdump: /dev/mapper/vg_mikenix-lv_swap': No such file or directory hexdump: stdin: Bad file descriptor hexdump: /dev/mapper/vg_mikenix-lv_swap': No such file or directory hexdump: /dev/mapper/vg_mikenix-lv_swap': Bad file descriptor mdadm: No arrays found in config file or automatically 

fdisk -l:

Disk /dev/sda: 320.1 GB, 320072933376 bytes 255 heads, 63 sectors/track, 38913 cylinders, total 625142448 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x48c044ea  Device Boot Start End Blocks Id System /dev/sda1 63 625140399 312570168+ 42 SFS  Disk /dev/sdc: 1000.2 GB, 1000204886016 bytes 255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x75f7e06d  Device Boot Start End Blocks Id System /dev/sdc1 2048 1953536129 976767041 7 HPFS/NTFS/exFAT  Disk /dev/sdd: 1000.2 GB, 1000204886016 bytes 255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x812f5830  Device Boot Start End Blocks Id System /dev/sdd1 * 2048 211679 104816 7 HPFS/NTFS/exFAT /dev/sdd2 206848 976767119 488280136 7 HPFS/NTFS/exFAT /dev/sdd3 976764928 977788927 512000 83 Linux /dev/sdd4 977788928 1953525167 487868120 5 Extended /dev/sdd5 977790976 1953523711 487866368 8e Linux LVM  Disk /dev/sde: 320.1 GB, 320072933376 bytes 255 heads, 63 sectors/track, 38913 cylinders, total 625142448 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x14a014a0  Device Boot Start End Blocks Id System /dev/sde1 * 2048 625153409 312575681 7 HPFS/NTFS/exFAT  Disk /dev/mapper/live-rw: 4294 MB, 4294967296 bytes 255 heads, 63 sectors/track, 522 cylinders, total 8388608 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes   Disk /dev/mapper/live-osimg-min: 4294 MB, 4294967296 bytes 255 heads, 63 sectors/track, 522 cylinders, total 8388608 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes   Disk /dev/mapper/vg_mikenix-lv_root: 53.7 GB, 53687091200 bytes 255 heads, 63 sectors/track, 6527 cylinders, total 104857600 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes   Disk /dev/mapper/vg_mikenix-lv_home: 439.6 GB, 439609196544 bytes 255 heads, 63 sectors/track, 53446 cylinders, total 858611712 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes   Disk /dev/mapper/vg_mikenix-lv_swap: 6274 MB, 6274678784 bytes 255 heads, 63 sectors/track, 762 cylinders, total 12255232 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes 
5
Вы пробовали запустить boot-repair? user1301428 11 лет назад 1
Я не. Я могу попробовать этот вечер. Я вижу, что это утилита Ubuntu. Если есть какие-то хитрости или конкретное использование для этого, пожалуйста, дайте мне знать. Благодарю. Michael 11 лет назад 0
Не совсем, вы можете немного повозиться с настройками, но обычно достаточно настроек по умолчанию. Если вы хотите, есть также live live CD;) user1301428 11 лет назад 0
Возможно, стоит попытаться загрузиться прямо в ваш раздел Linux с помощью [Super Grub Disc 2] (http://www.supergrubdisk.org/), чтобы убедиться, что он не поврежден - кажется, что bootinfoscript так и есть (хотя я может быть, это неправильно читать). Он должен автоматически обнаруживать ваши системы и позволять вам пытаться войти в систему. Изменили ли вы что-нибудь недавно перед этим (режим SATA, оборудование, новый жесткий диск и т. Д.)? Это, конечно, само собой разумеется, но если у вас есть возможность подкрепить свои вкусности, это, вероятно, будет разумно. nerdwaller 11 лет назад 0
Я вчера попробовал использовать Super Grub Disc 2. Я перепробовал все варианты, и он просто пошел бы на черный экран и ничего не делал. Я не делал никаких последних изменений в оборудовании. Программа, которую я запускал, которая давала мне BSOD, была CPU-Z. Это не имеет смысла: - | Michael 11 лет назад 0
ремонт багажника не сработал. Это был бесконечный поиск разделов. Я только что купил новый жесткий диск. Похоже, я собираюсь переустановить Windows, Linux и перенести. Спасибо вам обоим за помощь. Michael 11 лет назад 0
Возможно, слишком поздно / невозможно, но в некоторых ситуациях вы можете попробовать использовать spinrite http://www.grc.com/spinrite.htm. FreudianSlip 11 лет назад 0

1 ответ на вопрос

0
William Entriken

CentOS livecd можно использовать для переустановки Grub и исправления MBR. Подробности об этом подходе есть в вики CentOS по адресу http://wiki.centos.org/TipsAndTricks/ReinstallGRUB.