Invalid BS_jmpBoot in boot block: b7c45d + File system verify or repair failed

Using TestDisk to repair the filesystem
Forum rules
When asking for technical support:
- Search for posts on the same topic before posting a new question.
- Give clear, specific information in the title of your post.
- Include as many details as you can, MOST POSTS WILL GET ONLY ONE OR TWO ANSWERS.
- Post a follow up with a "Thank you" or "This worked!"
- When you learn something, use that knowledge to HELP ANOTHER USER LATER.
Before posting, please read https://www.cgsecurity.org/testdisk.pdf
Post Reply
Message
Author
izzy
Posts: 6
Joined: 29 Dec 2017, 07:22

Invalid BS_jmpBoot in boot block: b7c45d + File system verify or repair failed

#1 Post by izzy » 29 Dec 2017, 07:36

Hi,

I have a WD 1 Tera external hard disk. This disk has all of my kids and work documents and is very important for me. Appreciate all your help here. Thanks so much in advance.

What happened?
- Today I was copying my kids pics to this drive, and was done. I tried to eject it in the normally way from my mac, but then received a message saying, I need to a force eject as some other app was using it. I didn't want to but then had no other option after 15 minutes as this got stuck. Selected a force eject option. After this, I plugged my external drive again, and then saw a message saying "the drive is not readable" and gave me some options, initialize, ignore etc. I selected initialize and then saw that my drive was recognizable. Ran the first aid via the diskutils, and then selected the specific drive and ran the first aid again, which is similar to what I ran from the command line below, and came across the below error:

$diskutil list
/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *320.1 GB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_CoreStorage Macintosh HD 319.2 GB disk0s2
3: Apple_Boot Recovery HD 650.0 MB disk0s3

/dev/disk1 (internal, virtual):
#: TYPE NAME SIZE IDENTIFIER
0: Macintosh HD +318.8 GB disk1
Logical Volume on disk0s2
EE6A0CEE-7942-4F0E-816E-9EB2B6983D73
Unlocked Encrypted

/dev/disk2 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: FDisk_partition_scheme *1.0 TB disk2
1: DOS_FAT_32 1.0 TB disk2s1


I'm receiving the below error:

$ diskutil verifyVolume disk2s1
Started file system verification on disk2s1
Verifying file system
** /dev/rdisk2s1
Invalid BS_jmpBoot in boot block: b7c45d
File system check exit code is 8
Error: -69845: File system verify or repair failed
Underlying error: 8: Exec format error

I learnt from the internet about test disk, and downloaded. So far am able to navigate and am here running the analyze sector. Selected the apple partition map..

TestDisk 7.0, Data Recovery Utility, April 2015
Christophe GRENIER <grenier@cgsecurity.org>
http://www.cgsecurity.org

Disk /dev/rdisk2s1 - 1000 GB / 931 GiB - 1953525105 sectors
Analyse sector 5439488/1953525104: 00%

Can someone please help if I'm going in the right direction or not. If yes, then what do I need to do next?

Thanks again,
Izzy

Sponsored links

User avatar
cgrenier
Site Admin
Posts: 4390
Joined: 18 Feb 2012, 15:08
Location: Le Perreux Sur Marne, France
Contact:

Re: Invalid BS_jmpBoot in boot block: b7c45d + File system verify or repair failed

#2 Post by cgrenier » 29 Dec 2017, 19:00

Do you know what filesystem was used ? FAT32, as listed or something else like HFS+, exFAT, NTFS...

izzy
Posts: 6
Joined: 29 Dec 2017, 07:22

Re: Invalid BS_jmpBoot in boot block: b7c45d + File system verify or repair failed

#3 Post by izzy » 29 Dec 2017, 19:11

Thank you Christophe.

WD is an old one, which is based on DOS_FAT_32 but was recognizable by mac after I converted to mac journal, meaning this has transformed to HFS. Here is the latest data as test disk runs:

Disk /dev/rdisk2s1 - 1000 GB / 931 GiB - 1953525105 sectors
Analyse sector 229605376/1953525104: 00%
Read error at 171644838/0/1 (lba=171644838)

HFS 95890400 95892367 1968
HFS 95892448 95894415 1968

izzy
Posts: 6
Joined: 29 Dec 2017, 07:22

Re: Invalid BS_jmpBoot in boot block: b7c45d + File system verify or repair failed

#4 Post by izzy » 30 Dec 2017, 20:25

Here is the latest data run from the analyse:

TestDisk 7.0, Data Recovery Utility, April 2015
Christophe GRENIER <grenier@cgsecurity.org>
http://www.cgsecurity.org

Disk /dev/rdisk2s1 - 1000 GB / 931 GiB - 1953525105 sectors
Analyse sector 798687232/1953525104: 00%
Read error at 171644838/0/1 (lba=171644838)

HFS 95890400 95892367 1968
HFS 95892448 95894415 1968

Stop


I'm also reading up some articles where they mention about ddrescue and https://www.easeus.com/data-recovery/ot ... k-ntfs.htm - Can you please advise if I have to explore any of these after the analyse task is done or stick with test disk with a combination of photorec for data recovery?

Thanks much,
Raj

izzy
Posts: 6
Joined: 29 Dec 2017, 07:22

Re: Invalid BS_jmpBoot in boot block: b7c45d + File system verify or repair failed

#5 Post by izzy » 31 Dec 2017, 06:43

Updating another data point of my test disk run. Now the read error is at a different place.

TestDisk 7.0, Data Recovery Utility, April 2015
Christophe GRENIER <grenier@cgsecurity.org>
http://www.cgsecurity.org

Disk /dev/rdisk2s1 - 1000 GB / 931 GiB - 1953525105 sectors
Analyse sector 1017708544/1953525104: 00%
Read error at 1016235703/0/1 (lba=1016235703)

HFS 95890400 95892367 1968
HFS 95892448 95894415 1968

Stop

Appreciate any pointers posted in my earlier thread.

Thanks in advance
Izzy

User avatar
cgrenier
Site Admin
Posts: 4390
Joined: 18 Feb 2012, 15:08
Location: Le Perreux Sur Marne, France
Contact:

Re: Invalid BS_jmpBoot in boot block: b7c45d + File system verify or repair failed

#6 Post by cgrenier » 01 Jan 2018, 09:29

There may be some bad sectors, you should try to clone the disk using ddrescue (cf https://www.cgsecurity.org/testdisk.pdf )

The partition table lists a FAT32, so maybe Mac OS X fsck tries to fix a FAT32 filesystem instead of a HFS+, try

Code: Select all

sudo fsck_hfs -r -d /dev/disk2s1

izzy
Posts: 6
Joined: 29 Dec 2017, 07:22

Re: Invalid BS_jmpBoot in boot block: b7c45d + File system verify or repair failed

#7 Post by izzy » 02 Jan 2018, 21:01

Thank you Christophe. Happy New Year 2018!

I'll try your suggestion. I was waiting for the analysis to be complete, and it got done. Here is the final report of the analysis.

Quick question: I guess there is no point going into and doing a deeper search or analysis or for the test disk tool to fix it correct?

TestDisk 7.0, Data Recovery Utility, April 2015
Christophe GRENIER <grenier@cgsecurity.org>
http://www.cgsecurity.org

Disk /dev/rdisk2s1 - 1000 GB / 931 GiB - 1953525105 sectors
Partition Start End Size in sectors
>P HFS 95890400 95892367 1968
P HFS 95892448 95894415 1968


Structure: Ok. Use Up/Down Arrow keys to select partition.
Use Left/Right Arrow keys to CHANGE partition characteristics:
P=Primary D=Deleted
Keys A: add partition, L: load backup, T: change type,
Enter: to continue
HFS+ blocksize=4096, 1007 KB / 984 KiB

izzy
Posts: 6
Joined: 29 Dec 2017, 07:22

Re: Invalid BS_jmpBoot in boot block: b7c45d + File system verify or repair failed

#8 Post by izzy » 02 Jan 2018, 21:12

Hi Christophe,

I ran this option you suggested - sudo fsck_hfs -r -d /dev/disk2s1

Gave me an error. I guess its not good to write or build any btree as it could harm the defected disk.

journal_replay(/dev/disk2s1) returned 22
** /dev/rdisk2s1
Using cacheBlockSize=32K cacheTotalBlock=16384 cacheSize=524288K.
Executing fsck_hfs (version hfs-366.1.1).
Block 2 is not an MDB or Volume Header
Block 1953525103 is not an MDB or Volume Header
volumeType is 0
0000: b7c4 5d3d c0d4 a408 a8ec 2fea bf11 908f |................|
0010: 26f0 8989 8519 2778 8bcd 91f7 58ef ce8a |.......x....X...|
0020: 7ba9 490c 1c6c d1af 90af 3aca 417d 1ab0 |..I..l......A...|
0030: 20c2 bf89 65b6 0c49 ae8b b4d4 51af 8d8d |....e..I....Q...|
0040: 2d02 3c60 ac79 39f6 2f6d 7e2e cc8a bfe4 |.....y9..m......|
0050: d4d8 10f3 2862 c290 27f5 620b 1ba5 f135 |.....b....b....5|
0060: d71f e162 b8ae 274b 517f 7033 1017 19b7 |...b...KQ.p3....|
0070: 3a79 f255 e8f6 4a6e 12aa 564c 5b15 acbf |.y.U..Jn..VL....|
0080: f59a da03 1f5a 7ebf 2ba3 80b6 dec5 88dc |.....Z..........|
0090: c208 3820 45d6 c22a e850 4ce3 3631 cad0 |..8.E....PL.61..|
00a0: 9c91 6cb0 f441 b9b9 d160 0a3e a7ce 77f9 |..l..A........w.|
00b0: 22f4 2741 0a13 0abf 144f 0e29 4775 e86d |...A.....O..Gu.m|
00c0: 1a7b 691c a86d 4c27 d8ec cfac 1eda b76e |..i..mL........n|
00d0: f98f e0f6 d0b0 1f69 c0a4 7d8c fff4 29ab |.......i........|
00e0: 4578 b09b cfba e148 df81 2726 9531 64cb |Ex.....H.....1d.|
00f0: 22b3 457e 1ae5 655e 9488 dc9e 7b89 49d6 |..E...e.......I.|
0100: bcda 2fbd 8877 3308 2669 c733 3685 e4bf |.....w3..i.36...|
0110: 41fe e8fd 586b 1112 20a9 6e87 eb2a c7f8 |A...Xk....n.....|
0120: f91e 7670 c7d6 298c 7e4c 8e11 7140 152b |..vp.....L..q...|
0130: 8520 a3c2 1f4e 7825 022a a24d 71ff 2d95 |.....Nx....Mq...|
0140: e7ee 05f4 29bf a0e9 540c ac74 8da1 0d89 |........T..t....|
0150: d037 eb1f ea5e 8611 5a37 83cc 0949 a50a |.7......Z7...I..|
0160: 05de db60 0eb4 3d50 17eb f17a 39d4 9d01 |.......P...z9...|
0170: e08f e818 dfad 5026 d268 d8d5 a51d e39e |......P..h......|
0180: d4a3 31b3 48ec a880 be4e 29f9 5f11 5483 |..1.H....N....T.|
0190: 7142 a140 5e7b ca6b b472 fe0b 9774 2326 |qB.....k.r...t..|
01a0: 4de5 895d 21b2 3ceb 1cf0 3b30 4716 ce45 |M..........0G..E|
01b0: 911c fd52 3bfe 6e58 30c8 d7fc 93d8 63ef |...R..nX0.....c.|
01c0: c183 28d8 0094 907d 22a8 dc3a aba6 bd92 |................|
01d0: de26 5e22 0da0 7b46 a0f2 0b5d bd94 d8d1 |.......F........|
01e0: 30b1 a552 240a 539d dbf6 69ea 3eea c41e |0..R..S...i.....|
01f0: ecbc a3e6 4751 6f56 3c46 c781 1618 0f28 |....GQoV.F......|
unknown volume type
primary MDB is at block 0 0x00
alternate MDB is at block 0 0x00
primary VHB is at block 0 0x00
alternate VHB is at block 0 0x00
sector size = 512 0x200
VolumeObject flags = 0x01
total sectors for volume = 1953525105 0x74706d71
total sectors for embedded volume = 0 0x00
CheckForClean - unknown volume type
CheckHFS returned 6, fsmodified = 0

Post Reply

Who is online

Users browsing this forum: No registered users and 3 guests