Hacking WBFS-HD corrupted - any chance to recover?

jjkwii

Member
Newcomer
Joined
Nov 9, 2008
Messages
9
Trophies
0
XP
208
Country
Canada
Thanks for the quick response! Here are the results of both commands:


C:\Toolz\WWT>wwt analyze /dev/sdb1

ANALYZE /dev/sdb1
------------------------------------------------------------------------------------
HD SECTORS WBFS SECTORS DISCS (all values in hex)
WBFS total sec total sec max inode
NAME magic vrs num size num size num size ADDITIONAL INFORMATION
------------------------------------------------------------------------------------
HEADER: ok 0 74705982 200 e8e0 1000000 1f4 600 WBFS header scanning
DISCS: - 0 74705982 200 e8e0 1000000 1f4 600 166 disc header found
CALC 512: - 1 74705982 200 e8e0 1000000 1f4 600 calculation of init function
CALC 1024: - 1 3a382cc1 400 e8e0 1000000 3f4 800 " but sector-size=1024
CALC 2048: - 1 1d1c1660 800 e8e0 1000000 7f4 800 " but sector-size=2048
CALC 4096: - 1 e8e0b30 1000 e8e0 1000000 ff4 1000 " but sector-size=4096
------------------------------------------------------------------------------------



C:\Toolz\WWT> wwt init --recover /dev/sdb1
***** wwt: Wiimms WBFS Tool v0.43a r957 cygwin - Dirk Clemens - 2010-04-30 *****
!! wwt: Option --force must be set to formatting a WBFS!
!! wwt: => test mode (like --test) enabled!

ANALYZE BLOCK DEVICE /dev/sdb1
WOULD FORMAT BLOCK DEVICE /dev/sdb1 [932 GiB, hss=512, wss=16 MiB]
** 1 file formatted.
 

jjkwii

Member
Newcomer
Joined
Nov 9, 2008
Messages
9
Trophies
0
XP
208
Country
Canada
C:\Toolz\WWT>wwt init --recover --force /dev/sdb1
***** wwt: Wiimms WBFS Tool v0.43a r957 cygwin - Dirk Clemens - 2010-04-30 *****
ANALYZE BLOCK DEVICE /dev/sdb1
FORMAT BLOCK DEVICE /dev/sdb1 [932 GiB, hss=512, wss=16 MiB]
* Scan 442 discs in 500 slots.
* Check for disc block errors.
* Check free blocks table.

* Summary of WBFS check: no errors found.

** 1 file formatted.





C:\Toolz\WWT>wwt -a edit act=0-1000
***** wwt: Wiimms WBFS Tool v0.43a r957 cygwin - Dirk Clemens - 2010-04-30 *****

* MODIFY WBFS partition /dev/sdb1:
> WBFS block size: 1000000/hex = 16777216 = 16.0 MiB
> WBFS block range: 1..59615
> ISO block range: 0..560
> Number of discs: 442
> Number of slots: 500

- WOULD activate discs 0..499.

* Use option --force to leave the test mode.<


Everything looks clean now. The drive isn't detected in USB Loader GX though, but that's another problem. Thanks for you help, it's greatly appreciated!
 

tedrogers

Member
Newcomer
Joined
Dec 11, 2009
Messages
15
Trophies
0
Website
Visit site
XP
12
Country
manrikisan said:
I downloaded the hexeditor and followed the instructions from KIMEM on page 2 and everything works!!! Sweet!!

Hi, I've got the same issue, so I'm trying the HxD solution, and at sector 63 I don't have the term "WBFS" at all...it is blank.

Sector 64 shows my first title, and my last title is around Sector 950, so I can count them all.

What should I do? Or is there a better / safer way?

I really am flying blind here, and I know I'll probably wreck it if I try.

Please help. Lost a 500GB partition when my Wii crashed!!
 

Wiimm

Developer
Member
Joined
Aug 11, 2009
Messages
2,292
Trophies
1
Location
Germany
Website
wiimmfi.de
XP
1,519
Country
Germany
open a command windows (admin mode) and try
Code:
# check, if any WBFS is detected and to inform you
wwt analyze 

# if the output is to long try one of (os depended)
wwt analyze | less 
wwt analyze | more
wwt analyze > analyze.txt # and edit

# give format a chance (test mode only)
wwt format --recover --test /dev/your_drive

# If you like the results try
wwt formatÂÂ--recover --force /dev/your_drive

But remember: a wrong drive path may destroy the content of that drive
 

tedrogers

Member
Newcomer
Joined
Dec 11, 2009
Messages
15
Trophies
0
Website
Visit site
XP
12
Country
Wiimm said:
open a command windows (admin mode) and try
Code:
# check, if any WBFS is detected and to inform you
wwt analyze 

# if the output is to long try one of (os depended)
wwt analyze | less 
wwt analyze | more
wwt analyze > analyze.txt # and edit

# give format a chance (test mode only)
wwt format --recover --test /dev/your_drive

# If you like the results try
wwt formatÂÂ--recover --force /dev/your_drive

But remember: a wrong drive path may destroy the content of that drive

Hi thanks for your fast reply.

I just have some questions before I attempt this.

1. In Linux (Ubuntu), for ADMIN mode you mean I should run ROOT TERMINAL or gksudo a terminal, and not simply "su" (switching user) in a normal terminal?

2. Do I need to manually mount the external drive with broken WBFS before issuing "wwt analyze" command, or is the purpose of "wwt analyze" to scan all attached filesystems for WBFS content, even if not mounted?

3. How would I know if I like the results produced by issuing "wwt format --recover --test /dev/your_drive"? What would I be looking for? If good, would it say "SUCCESS" or something similar???

4. When I connect my WBFS drive I have several devices listed. These are /dev/sdb and /dev/sdb1. sdb1 is the partition with the data, and sdb is just the logical drive I think, so I would use /dev/sdb1 in your final step? Correct?

Thank you once again, I am desperate for help and people like you are a blessing!
smile.gif


Ted.
 

Wiimm

Developer
Member
Joined
Aug 11, 2009
Messages
2,292
Trophies
1
Location
Germany
Website
wiimmfi.de
XP
1,519
Country
Germany
@tedrogers
You need to switch to root if your drive can't be read from your working account. "su" or "sudo" or "ssh root@localhost command" are some of many possible ways.

If you use "wwt find -l" you get a list with all drives that wwt can find and read.

"wwt analyze" will generate a list for all this drives and gives you a little table with info for each drive. See docu "command ANALYZE" (file wwt.txt) for more info.

Both "wwt find" and "wwt analyze" includes the drive path. Format needs this drive path to format. Only "wwt format --force" will modify (and may be destroy) data. All other her explained commands are read only.
 

tedrogers

Member
Newcomer
Joined
Dec 11, 2009
Messages
15
Trophies
0
Website
Visit site
XP
12
Country
Wiimm said:
@tedrogers
You need to switch to root if your drive can't be read from your working account. "su" or "sudo" or "ssh root@localhost command" are some of many possible ways.

If you use "wwt find -l" you get a list with all drives that wwt can find and read.

"wwt analyze" will generate a list for all this drives and gives you a little table with info for each drive. See docu "command ANALYZE" (file wwt.txt) for more info.

Both "wwt find" and "wwt analyze" includes the drive path. Format needs this drive path to format. Only "wwt format --force" will modify (and may be destroy) data. All other her explained commands are read only.

@Wiimm
This format command does worry me...assuming that it is successful, how can it be that it can leave the backup ISO data intact, will it not simply erase the TOC, or does it rebuild this and therefore restore the drive to a fully working condition with backup ISO's in place?

Also, how can I avoid this problem again in future? It has happened to me once before, but this was because of human error - I erased it!! Doh!
smile.gif
 

Wiimm

Developer
Member
Joined
Aug 11, 2009
Messages
2,292
Trophies
1
Location
Germany
Website
wiimmfi.de
XP
1,519
Country
Germany
The --recover option says "wwt format":
1.) make a analyze (like wwt ANALYZE) to find old WBFS data.
2.) format by writing only the header with the geometry found by analyze (or set with --hss and --wss).
3.) search discs and recover them if possible.

Please do all commands but not "wwt format --force" before asking again and then you see what i mean. The --test mode is available for all modifying commands and enabled for "wwt format" by default.

If you erased a disc only by mistake, then try "wwt recover" (with option --test for testmode).


EDIT:
One last word: I have implemented this recover functions with care and without a need of my self. I have made many tests. But I'm not perfect. I can't guarantee that all work. So it is your decision to do it or not. If you have enough disk space you can make 1:1 copy of your drive and play with that copy.
 

tedrogers

Member
Newcomer
Joined
Dec 11, 2009
Messages
15
Trophies
0
Website
Visit site
XP
12
Country
Wiimm said:
The --recover option says "wwt format":
1.) make a analyze (like wwt ANALYZE) to find old WBFS data.
2.) format by writing only the header with the geometry found by analyze (or set with --hss and --wss).
3.) search discs and recover them if possible.

Please do all commands but not "wwt format --force" before asking again and then you see what i mean. The --test mode is available for all modifying commands and enabled for "wwt format" by default.

If you erased a disc only by mistake, then try "wwt recover" (with option --test for testmode).


EDIT:
One last word: I have implemented this recover functions with care and without a need of my self. I have made many tests. But I'm not perfect. I can't guarantee that all work. So it is your decision to do it or not. If you have enough disk space you can make 1:1 copy of your drive and play with that copy.

Okay well I gave it a go, using Windows 7, and at first it seemed to work brilliantly.

I performed the steps and did wwt format --recover --force /dev/YOUR_DRIVE to both /sdb and /sdb1, like such, doing each one in turn:

wwt format --recover --force /dev/sdb
wwt format --recover --force /dev/sdb1

When I loaded WBFS Manager, I could see all my backups. I thought all was well.

So, I disconnected the drive and attatched it to my Wii, but in USB Loader GX and Configurable USB Loader, it would not see any of the backup titles?

I reconnected the drive back to the computer, ran wwt analyse again, and now /sdb1 is missing - I only have /sdb??

Can you advise what I am doing wrong, or have I completely broken it??!!??

UPDATE
: For further information, I loaded up HxD Hex Editor and noticed that I do have 2 physical drives. If I go to Sector 63 and 64 on the 2nd drive (which I guess is my sdb1, as sdb would be the 1st drive), then I can see it says WBFS:8L at the start of Sector 63, and then my first backup title, e.g. Wii Play, at the start of Sector 74.

So I guess this means that sdb1 still exists on the drive, but isn't being recognised by the computer / Wii?

Then I decided to look into the Disk Manager in Windows 7, and I was presented with a dialogue box requesting that a build a Master Boot Record (MBR). Here's a screenshot.

wiim.png


So does that then mean I have broken the MBR and is it fixable?

Thanks for your continued assistance...I really do appreciate it.
 

tedrogers

Member
Newcomer
Joined
Dec 11, 2009
Messages
15
Trophies
0
Website
Visit site
XP
12
Country
Wiimm said:
"wwt format --recover --force /dev/sdb" will overwrite the partition table of the drive.

That didn't work. The wwt commands seem to have been successful (see screens), but I am still not able to see sdb1 with all my titles in WBFS Manager or on the Wii console in USB Loader GX or other.

I don't understand where sdb1 has gone.

Here is wwt analyse /dev/sdb:

66738819.png


Here is wwt format --recover --force /dev/sdb

31456776.png


Do you have any further ideas?

Thank you.
 

udoncat

Member
Newcomer
Joined
Mar 18, 2010
Messages
6
Trophies
0
XP
50
Country
Please excuse my noobishness regarding wwt and hex and apologies for jumping in this thread.

I believed my 600gb hdd was corrupted as WBFS tool v14 couldn't transfer any ISOs to the drive (it had about 20 games already) and neither could it transfer some of the ISOs off it or delete any of the images.

cfgUSB loader could still load the drive and load some games, so I decided formatting the drive to NTFS, using a newer tool to reformat to WBFS and reloading all discs and images would be best. I've used ncWBFSTool to reformat to WBFS, but it reported that the drive no longer has any free space and could not copy any images to the drive.

The drive was then reformatted to NTFS and WiiBackup Manager used instead but it couldn't detect the drive.

What the heck is going on and how can it be fixed?
 

Wiimm

Developer
Member
Joined
Aug 11, 2009
Messages
2,292
Trophies
1
Location
Germany
Website
wiimmfi.de
XP
1,519
Country
Germany
@tedrogers
after formatting you get that result with "wit analyze". I think that /dev/sdb was the right one. And a test with analyse should give you much info before formatting.

If analyze find something it looks like:
Code:
ANALYZE /dev/sdb2
------------------------------------------------------------------------------------
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂHD SECTORSÂÂWBFS SECTORSÂÂ DISCSÂÂÂÂÂÂ (all values in hex)
ÂÂÂÂÂÂÂÂÂÂ WBFSÂÂÂÂ totalÂÂsecÂÂtotalÂÂÂÂsecÂÂmax inode
NAMEÂÂÂÂmagic vrsÂÂÂÂ num sizeÂÂ numÂÂÂÂsizeÂÂnum sizeÂÂADDITIONAL INFORMATION
------------------------------------------------------------------------------------
HEADER:ÂÂÂÂokÂÂ1ÂÂba70449ÂÂ200ÂÂba70ÂÂ200000ÂÂ d6 2600ÂÂWBFS header scanning
INODE-TIM: okÂÂ1ÂÂba70449ÂÂ200ÂÂba70ÂÂ200000ÂÂ d6 2600ÂÂ2010-03-12 12:11:38 n=214
DISCS:ÂÂÂÂÂÂ-ÂÂ0ÂÂba70449ÂÂ200ÂÂba70ÂÂ200000ÂÂ d6 2600ÂÂ17 disc header found
CALCÂÂ512:ÂÂ-ÂÂ1ÂÂba70449ÂÂ200ÂÂba70ÂÂ200000ÂÂ d6 2600ÂÂcalculation of init function
CALC 1024:ÂÂ-ÂÂ1ÂÂ5d38224ÂÂ400ÂÂba70ÂÂ200000ÂÂ cc 2800ÂÂ " but sector-size=1024
CALC 2048:ÂÂ-ÂÂ1ÂÂ2e9c112ÂÂ800ÂÂba70ÂÂ200000ÂÂ cc 2800ÂÂ " but sector-size=2048
CALC 4096:ÂÂ-ÂÂ1ÂÂ174e089 1000ÂÂba70ÂÂ200000ÂÂ a9 3000ÂÂ " but sector-size=4096
------------------------------------------------------------------------------------

The docu explains the lines:
Code:
...
The columns (all numbers are printed in hex):

ÂÂÂÂNAME
ÂÂÂÂÂÂÂÂShort name of the analyze mode.
ÂÂÂÂÂÂÂÂ- HEADER:ÂÂResult of header analyzing (first 12 bytes).
ÂÂÂÂÂÂÂÂ- INODE-*: Result of INODE-INFO searching.
ÂÂÂÂÂÂÂÂÂÂÂÂ- INODE-TIM: The newest INODE found.
ÂÂÂÂÂÂÂÂÂÂÂÂ- INODE-CNT: The inodes with the largest equal-inodes-count.
ÂÂÂÂÂÂÂÂÂÂÂÂ- INODE-1ST: The first inodes found if not already printed.
ÂÂÂÂÂÂÂÂ- DISCS:ÂÂ Result of searching discs in the WBFS management area.
ÂÂÂÂÂÂÂÂ- CALC #:ÂÂCalculation of the INIT function.
ÂÂÂÂÂÂÂÂ- OLD #:ÂÂ Calculation of the INIT function with the old buggy algorithm.

ÂÂÂÂWBFS magic:
ÂÂÂÂÂÂÂÂ"ok" if a WBFS magic was found.

ÂÂÂÂWBFS vrs:
ÂÂÂÂÂÂÂÂWBFS version.

ÂÂÂÂHD SECTORS total num:
ÂÂÂÂÂÂÂÂTotal number of HS sectors of the file/partition.

ÂÂÂÂHD SECTORS sec size:
ÂÂÂÂÂÂÂÂThe harddisk sector size of the file/partition.

ÂÂÂÂWBFS SECTORS total num:
ÂÂÂÂÂÂÂÂTotal number of WBFS sectors. The maximum if 0x10000 = 65536.

ÂÂÂÂWBFS SECTORS sec size:
ÂÂÂÂÂÂÂÂThe WBFS sector size of the file/partition.
ÂÂÂÂÂÂÂÂ
ÂÂÂÂDISCS max num:
ÂÂÂÂÂÂÂÂMaximal possible discs.

ÂÂÂÂDISCS inode size:
ÂÂÂÂÂÂÂÂThe disc info size for a single disc.

ÂÂÂÂADDITIONAL INFORMATION:
ÂÂÂÂÂÂÂÂAdditiional informaton.
ÂÂÂÂÂÂÂÂ- INODE: most current date and number of equal inodes infos found.
ÂÂÂÂÂÂÂÂ- DISCS: number of discs found in the management area of WEBFS.

The output can also be used to setup parameters for the INIT command.

And for /dev/sdb you have
- HEADER because of formatting
- CALC-* as example calculations

And because of formatting /dev/sdb you has lost your disk partition table and no access to partiton /dev/sdb1.

Solution:
backup the first 50 MB of your drive with "dd if=/dev/sdb of=backup-file bs=1m count=50"
you can restore it with "dd if=backup-file of=/dev/sdb bs=1m"

then use fdisk to create a new partition table (don't format) and then try to recover (analyze first) /dev/sdb1. Perhaps there are tools that will repair you partition table.

EDIT
I'm not perfect. So think about what I said before executing it.
 

Wiimm

Developer
Member
Joined
Aug 11, 2009
Messages
2,292
Trophies
1
Location
Germany
Website
wiimmfi.de
XP
1,519
Country
Germany
@udoncat
try "wwt check -a" for a wbfs check. If there is no valid WBFS then try "wwt analyze" to analyze all found partitions. wwt must run in root/admin mode.
 

tedrogers

Member
Newcomer
Joined
Dec 11, 2009
Messages
15
Trophies
0
Website
Visit site
XP
12
Country
Wiimm said:
@tedrogers
after formatting you get that result with "wit analyze". I think that /dev/sdb was the right one. And a test with analyse should give you much info before formatting.

If analyze find something it looks like:
Code:
ANALYZE /dev/sdb2
------------------------------------------------------------------------------------
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂHD SECTORSÂÂWBFS SECTORSÂÂ DISCSÂÂÂÂÂÂ (all values in hex)
ÂÂÂÂÂÂÂÂÂÂ WBFSÂÂÂÂ totalÂÂsecÂÂtotalÂÂÂÂsecÂÂmax inode
NAMEÂÂÂÂmagic vrsÂÂÂÂ num sizeÂÂ numÂÂÂÂsizeÂÂnum sizeÂÂADDITIONAL INFORMATION
------------------------------------------------------------------------------------
HEADER:ÂÂÂÂokÂÂ1ÂÂba70449ÂÂ200ÂÂba70ÂÂ200000ÂÂ d6 2600ÂÂWBFS header scanning
INODE-TIM: okÂÂ1ÂÂba70449ÂÂ200ÂÂba70ÂÂ200000ÂÂ d6 2600ÂÂ2010-03-12 12:11:38 n=214
DISCS:ÂÂÂÂÂÂ-ÂÂ0ÂÂba70449ÂÂ200ÂÂba70ÂÂ200000ÂÂ d6 2600ÂÂ17 disc header found
CALCÂÂ512:ÂÂ-ÂÂ1ÂÂba70449ÂÂ200ÂÂba70ÂÂ200000ÂÂ d6 2600ÂÂcalculation of init function
CALC 1024:ÂÂ-ÂÂ1ÂÂ5d38224ÂÂ400ÂÂba70ÂÂ200000ÂÂ cc 2800ÂÂ " but sector-size=1024
CALC 2048:ÂÂ-ÂÂ1ÂÂ2e9c112ÂÂ800ÂÂba70ÂÂ200000ÂÂ cc 2800ÂÂ " but sector-size=2048
CALC 4096:ÂÂ-ÂÂ1ÂÂ174e089 1000ÂÂba70ÂÂ200000ÂÂ a9 3000ÂÂ " but sector-size=4096
------------------------------------------------------------------------------------

The docu explains the lines:
Code:
...
The columns (all numbers are printed in hex):

ÂÂÂÂNAME
ÂÂÂÂÂÂÂÂShort name of the analyze mode.
ÂÂÂÂÂÂÂÂ- HEADER:ÂÂResult of header analyzing (first 12 bytes).
ÂÂÂÂÂÂÂÂ- INODE-*: Result of INODE-INFO searching.
ÂÂÂÂÂÂÂÂÂÂÂÂ- INODE-TIM: The newest INODE found.
ÂÂÂÂÂÂÂÂÂÂÂÂ- INODE-CNT: The inodes with the largest equal-inodes-count.
ÂÂÂÂÂÂÂÂÂÂÂÂ- INODE-1ST: The first inodes found if not already printed.
ÂÂÂÂÂÂÂÂ- DISCS:ÂÂ Result of searching discs in the WBFS management area.
ÂÂÂÂÂÂÂÂ- CALC #:ÂÂCalculation of the INIT function.
ÂÂÂÂÂÂÂÂ- OLD #:ÂÂ Calculation of the INIT function with the old buggy algorithm.

ÂÂÂÂWBFS magic:
ÂÂÂÂÂÂÂÂ"ok" if a WBFS magic was found.

ÂÂÂÂWBFS vrs:
ÂÂÂÂÂÂÂÂWBFS version.

ÂÂÂÂHD SECTORS total num:
ÂÂÂÂÂÂÂÂTotal number of HS sectors of the file/partition.

ÂÂÂÂHD SECTORS sec size:
ÂÂÂÂÂÂÂÂThe harddisk sector size of the file/partition.

ÂÂÂÂWBFS SECTORS total num:
ÂÂÂÂÂÂÂÂTotal number of WBFS sectors. The maximum if 0x10000 = 65536.

ÂÂÂÂWBFS SECTORS sec size:
ÂÂÂÂÂÂÂÂThe WBFS sector size of the file/partition.
ÂÂÂÂÂÂÂÂ
ÂÂÂÂDISCS max num:
ÂÂÂÂÂÂÂÂMaximal possible discs.

ÂÂÂÂDISCS inode size:
ÂÂÂÂÂÂÂÂThe disc info size for a single disc.

ÂÂÂÂADDITIONAL INFORMATION:
ÂÂÂÂÂÂÂÂAdditiional informaton.
ÂÂÂÂÂÂÂÂ- INODE: most current date and number of equal inodes infos found.
ÂÂÂÂÂÂÂÂ- DISCS: number of discs found in the management area of WEBFS.

The output can also be used to setup parameters for the INIT command.

And for /dev/sdb you have
- HEADER because of formatting
- CALC-* as example calculations

And because of formatting /dev/sdb you has lost your disk partition table and no access to partiton /dev/sdb1.

Solution:
backup the first 50 MB of your drive with "dd if=/dev/sdb of=backup-file bs=1m count=50"
you can restore it with "dd if=backup-file of=/dev/sdb bs=1m"

then use fdisk to create a new partition table (don't format) and then try to recover (analyze first) /dev/sdb1. Perhaps there are tools that will repair you partition table.

EDIT
I'm not perfect. So think about what I said before executing it.

@Wiimm

Hi Wiimm, and thanks so much for being patient with me.
smile.gif


I thought hard about what you suggest and I have studied your posts and compared with my results several times, and I am beginning to understand (it's complex), but I am still having trouble.

The command to backup "dd if=/dev/sdb of=backup-file bs=1m count=50" does not work. I tried in Windows 7 and the command "dd is not recognised".

So I looked it up and found it was a Linux backup application, so I tried it in Ubuntu.

The command still did not work and for the command "dd if=/dev/sdb of=backup-file bs=1m count=50" it returned the error "dd: invalid number `1m'"...so I looked in the manual for "dd" and found that bs= BYTES. So I wonder if you meant "bs=1" and not "bs=1m"? Is the "m" a mistake?

To test, as a backup cannot do any harm, the command "dd if=/dev/sdb of=backup-file bs=1 count=50" (no "m") worked fine...I think. Can you confirm success?

It did this:

Code:
50+0 records in
50+0 records out
50 bytes (50 B) copied, 0.0206131 s, 2.4 kB/s

This produced a file of 50 bytes and not 50MB....so it can't be right?

If I wanted a 50MB backup, then shouldn't the command be:

Code:
dd if=/dev/sdb of=backup-file bs=1 count=52428800

*Notice the count was changed from count=50*

This did produce a file of 50MB so I assume this is this now correct? Agreed?

When doing fdisk, it produced this output:

Code:
Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel
Building a new DOS disklabel with disk identifier 0xb5b0b14a.
Changes will remain in memory only, until you decide to write them.
After that, of course, the previous content won't be recoverable.

Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite)

WARNING: DOS-compatible mode is deprecated. It's strongly recommended to
ÂÂÂÂÂÂÂÂ switch off the mode (command 'c') and change display units to
ÂÂÂÂÂÂÂÂ sectors (command 'u').

The worrying thing here is the part in RED and bold below. What does this mean?

Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite)

Finally, how would I go about making a new partition table with fdisk?

Would I use option O from the HELP in fdisk?

CODEoÂÂ create a new empty DOS partition table

Thank you, a thousand times!!
smile.gif
 

Wiimm

Developer
Member
Joined
Aug 11, 2009
Messages
2,292
Trophies
1
Location
Germany
Website
wiimmfi.de
XP
1,519
Country
Germany
"1M" is correct and it means 1024*1024 byes. With count=50 you will backup the first 50 MiB of your drive. Yes, dd dous not exists native on Windows. use cygwin or other unix like extensions.

The error message is because you have an invalid partition table. "o" is the right way to create a new on.
 

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
    Xdqwerty @ Xdqwerty: @K3Nv2, prove it