Joined
·
1 Posts
HP Pavilion 14-b1305A started blue screening with above error, no sounds from harddrive and liveusb runs fine except that the hard disk cannot mount when I run a linux live-usb(I'm using gparted disk magic). Therefore suspect problem with partitions not memory/hard drive.
fdisk gives:GPT PMBR size mismatch (1465143295 != 1465149167) will be corrected by w(rite).
Disk /dev/sda: 698.7 GiB, 750156374016 bytes, 1465149168 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
Disklabel type: gpt
Disk identifier: 65AEFD90-8464-4ECD-B269-FAB7D6A4B6F6
Device Start End Sectors Size Type
/dev/sda1 2048 821247 819200 400M Windows recovery environment
/dev/sda2 821248 1353727 532480 260M EFI System
/dev/sda3 1353728 1615871 262144 128M Microsoft reserved
/dev/sda4 1615872 1418260075 1416644204 675.5G Microsoft basic data
/dev/sda5 1418260480 1419984895 1724416 842M Windows recovery environment
/dev/sda6 1419984896 1420701695 716800 350M Windows recovery environment
/dev/sda7 1420701696 1465141247 44439552 21.2G Microsoft basic data
Question 1: Is this the result you would expect with faulty partitioning?
Any recommendations? So far I have been trying to use testdisk to fix partition table, which thinks I have an EFI GPT partition table and lists the following partitions:
Disk /dev/sda - 750 GB / 698 GiB - CHS 91201 255 63
Partition Start End Size in sectors
>P MS Data 2048 821247 819200
P MS Data 821248 1353727 532480 [NO NAME]
D MS Data 1615872 1418260075 1416644204
D MS Data 1376262145 1420701696 44439552
D MS Data 1416536065 1418260480 1724416
D MS Data 1418260480 1419984895 1724416
D MS Data 1419268097 1419984896 716800
D MS Data 1419984896 1420701695 716800
D MS Data 1420701696 1465141247 44439552
Question 2: What changes should I make to the partition table? Is it possible the partition table isn't an EFI GPT?
fdisk gives:GPT PMBR size mismatch (1465143295 != 1465149167) will be corrected by w(rite).
Disk /dev/sda: 698.7 GiB, 750156374016 bytes, 1465149168 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
Disklabel type: gpt
Disk identifier: 65AEFD90-8464-4ECD-B269-FAB7D6A4B6F6
Device Start End Sectors Size Type
/dev/sda1 2048 821247 819200 400M Windows recovery environment
/dev/sda2 821248 1353727 532480 260M EFI System
/dev/sda3 1353728 1615871 262144 128M Microsoft reserved
/dev/sda4 1615872 1418260075 1416644204 675.5G Microsoft basic data
/dev/sda5 1418260480 1419984895 1724416 842M Windows recovery environment
/dev/sda6 1419984896 1420701695 716800 350M Windows recovery environment
/dev/sda7 1420701696 1465141247 44439552 21.2G Microsoft basic data
Question 1: Is this the result you would expect with faulty partitioning?
Any recommendations? So far I have been trying to use testdisk to fix partition table, which thinks I have an EFI GPT partition table and lists the following partitions:
Disk /dev/sda - 750 GB / 698 GiB - CHS 91201 255 63
Partition Start End Size in sectors
>P MS Data 2048 821247 819200
P MS Data 821248 1353727 532480 [NO NAME]
D MS Data 1615872 1418260075 1416644204
D MS Data 1376262145 1420701696 44439552
D MS Data 1416536065 1418260480 1724416
D MS Data 1418260480 1419984895 1724416
D MS Data 1419268097 1419984896 716800
D MS Data 1419984896 1420701695 716800
D MS Data 1420701696 1465141247 44439552
Question 2: What changes should I make to the partition table? Is it possible the partition table isn't an EFI GPT?