-
All replies
-
Helpful answers
-
Sep 25, 2016 6:03 PM in response to Loner Tby allowin,Asturias:~ Home$ sudo fdisk /dev/disk0
Password:
Disk: /dev/disk0 geometry: 19457/255/63 [312581808 sectors]
Signature: 0xAA55
Starting Ending
#: id cyl hd sec - cyl hd sec [ start - size]
------------------------------------------------------------------------
1: EE 1023 254 63 - 1023 254 63 [ 1 - 409639] <Unknown ID>
2: AF 1023 254 63 - 1023 254 63 [ 409640 - 222656256] HFS+
3: 0B 1023 254 63 - 1023 254 63 [ 223328256 - 89251840] Win95 FAT-32
4: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
Asturias:~ Home$
I think I have Paragon
-
Sep 25, 2016 6:07 PM in response to allowinby Loner T,The Paragon and Apple NTFS drivers have conflicts, which causes the restored device not to mount. Can you temporarily remove/uninstall/disable Paragon and restore the Winclone image again?
Once Winclone can mount the partition properly, your restore should work. If you still run into any issues, please post back.
-
Sep 25, 2016 6:11 PM in response to Loner Tby allowin,Disk: /dev/disk0 geometry: 19457/255/63 [312581808 sectors] Signature: 0xAA55
Starting Ending
#: id cyl hd sec - cyl hd sec [ start - size]
------------------------------------------------------------------------
1: EE 1023 254 63 - 1023 254 63 [ 1 - 409639] <Unknown ID>
2: AF 1023 254 63 - 1023 254 63 [ 409640 - 222656256] HFS+
3: 0B 1023 254 63 - 1023 254 63 [ 223328256 - 89251840] Win95 FAT-32
4: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
Asturias:~ Home$
Asturias:~ Home$ sudo dd if=/dev/rdisk0s3 count=1 2>/dev/null | hexdump -C
Password:
00000000 eb 58 90 42 53 44 20 20 34 2e 34 00 02 40 20 00 |.X.BSD 4.4..@ .|
00000010 02 00 00 00 00 f0 00 00 20 00 ff 00 00 00 00 00 |........ .......|
00000020 00 e0 51 05 8d 2a 00 00 00 00 00 00 02 00 00 00 |..Q..*..........|
00000030 01 00 06 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
00000040 00 00 29 f3 0e 62 14 42 4f 4f 54 43 41 4d 50 20 |..)..b.BOOTCAMP |
00000050 20 20 46 41 54 33 32 20 20 20 fa 31 c0 8e d0 bc | FAT32 .1....|
00000060 00 7c fb 8e d8 e8 00 00 5e 83 c6 19 bb 07 00 fc |.|......^.......|
00000070 ac 84 c0 74 06 b4 0e cd 10 eb f5 30 e4 cd 16 cd |...t.......0....|
00000080 19 0d 0a 4e 6f 6e 2d 73 79 73 74 65 6d 20 64 69 |...Non-system di|
00000090 73 6b 0d 0a 50 72 65 73 73 20 61 6e 79 20 6b 65 |sk..Press any ke|
000000a0 79 20 74 6f 20 72 65 62 6f 6f 74 0d 0a 00 00 00 |y to reboot.....|
000000b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
000001f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa |..............U.|
00000200
-
Sep 25, 2016 6:16 PM in response to allowinby Loner T,Is this a Windows XP installation on a FAT partition? As the MBR and the block dump indicate, it is still a FAT32 partition.
-
Sep 25, 2016 6:17 PM in response to Loner Tby allowin,Excuse me Loner T, I am exhausted, not been sleeping well lately, please let us continue after few hours of rest.
thanks a lot
-
Sep 25, 2016 6:20 PM in response to allowinby Loner T,Post back when you are ready. If you are in CEST, you are about 6 hours ahead of me.
-
-
Sep 25, 2016 6:22 PM in response to Loner Tby allowin,it is a fat32 partition made with Bootcamp assistant
ya i'm in France. please forgivec me, I am really tired
-
Sep 25, 2016 6:25 PM in response to allowinby Loner T,Please uninstall Paragon, to avoid conflicts and try it after you have had some sleep.
-
Sep 25, 2016 11:51 PM in response to Loner Tby allowin,Hy, There is no Paragon installed in my system at the moment, I think I have tried to use it few years ago, that's all.
Now what about erasing the drive again with guid partition, install by moving with super duper my snow leopard, and then creating a bootcamp partition with Bootcamp assistant ? there is some time consuming, but it's clean, what you think ?Maybe I got all these trouble, when manipulating my drive with disk utility in enlarging partitions of my drive ?
-
Sep 26, 2016 12:07 AM in response to Loner Tby allowin,Hi, I have started terminal without your permission, this is what it says:
Last login: Mon Sep 26 08:37:47 on console
Asturias:~ Home$ udo fdisk /dev/disk0
-bash: udo: command not found
Asturias:~ Home$ sudo fdisk /dev/disk0
Password:
Disk: /dev/disk0 geometry: 19457/255/63 [312581808 sectors]
Signature: 0xAA55
Starting Ending
#: id cyl hd sec - cyl hd sec [ start - size]
------------------------------------------------------------------------
1: EE 1023 254 63 - 1023 254 63 [ 1 - 409639] <Unknown ID>
2: AF 1023 254 63 - 1023 254 63 [ 409640 - 222656256] HFS+
3: 0B 1023 254 63 - 1023 254 63 [ 223328256 - 89251840] Win95 FAT-32
4: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
Asturias:~ Home$ sudo dd if=/dev/rdisk0s3 count=1 2>/dev/null | hexdump -C
00000000 eb 58 90 42 53 44 20 20 34 2e 34 00 02 40 20 00 |.X.BSD 4.4..@ .|
00000010 02 00 00 00 00 f0 00 00 20 00 ff 00 00 00 00 00 |........ .......|
00000020 00 e0 51 05 8d 2a 00 00 00 00 00 00 02 00 00 00 |..Q..*..........|
00000030 01 00 06 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
00000040 00 00 29 f3 0e 62 14 42 4f 4f 54 43 41 4d 50 20 |..)..b.BOOTCAMP |
00000050 20 20 46 41 54 33 32 20 20 20 fa 31 c0 8e d0 bc | FAT32 .1....|
00000060 00 7c fb 8e d8 e8 00 00 5e 83 c6 19 bb 07 00 fc |.|......^.......|
00000070 ac 84 c0 74 06 b4 0e cd 10 eb f5 30 e4 cd 16 cd |...t.......0....|
00000080 19 0d 0a 4e 6f 6e 2d 73 79 73 74 65 6d 20 64 69 |...Non-system di|
00000090 73 6b 0d 0a 50 72 65 73 73 20 61 6e 79 20 6b 65 |sk..Press any ke|
000000a0 79 20 74 6f 20 72 65 62 6f 6f 74 0d 0a 00 00 00 |y to reboot.....|
000000b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
000001f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa |..............U.|
00000200
Asturias:~ Home$ diskutil list
/dev/disk0
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *160.0 GB disk0
1: EFI 209.7 MB disk0s1
2: Apple_HFS Atlas 114.0 GB disk0s2
3: Microsoft Basic Data BOOTCAMP 45.7 GB disk0s3
/dev/disk1
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *750.2 GB disk1
1: EFI 209.7 MB disk1s1
2: Apple_HFS Shiba750 749.8 GB disk1s2
/dev/disk2
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *120.0 GB disk2
1: EFI 209.7 MB disk2s1
2: Apple_HFS Toubkal 85.9 GB disk2s2
3: Microsoft Basic Data BOOTCAMP 26.2 GB disk2s3
Asturias:~ Home$ sudo gpt -vv -r show /dev/disk0
gpt show: /dev/disk0: mediasize=160041885696; sectorsize=512; blocks=312581808
gpt show: /dev/disk0: Suspicious MBR at sector 0
gpt show: /dev/disk0: Pri GPT at sector 1
gpt show: /dev/disk0: Sec GPT at sector 312581807
start size index contents
0 1 MBR
1 1 Pri GPT header
2 32 Pri GPT table
34 6
40 409600 1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
409640 222656256 2 GPT part - 48465300-0000-11AA-AA11-00306543ECAC
223065896 262360
223328256 89251840 3 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
312580096 1679
312581775 32 Sec GPT table
312581807 1 Sec GPT header
Asturias:~ Home$ man diskutil
diskutil(8) BSD System Manager's Manual diskutil(8)
NAME
diskutil -- Modify, verify and repair local disks.
SYNOPSIS
diskutil [quiet] verb [options]
DESCRIPTION
diskutil manipulates the volume-level structure of local disks. It pro-
vides information about, and allows the administration of, the partition-
ing scheme of disks, optical discs, and AppleRAID sets.
VERBS
Each verb is listed with its description and individual arguments.
list [-plist | device]
List disks. If no argument is given, then all disks and all of
their partitions are listed.
If -plist is specified, then a property list will be emitted
instead of the normal user-readable output. If a device is
specified, then instead of listing all families of whole disks
and their partitions, only one such family is listed. In that
case, specifying either the whole disk or any of its slices
will work. The -plist and device arguments may not both be
specified at the same time.
A script could interpret the results of the diskutil list
-plist output and use diskutil info -plist as well as diskutil
listFilesystems -plist for more detailed information.
See the DEVICES section below for the various forms that the
device specification may take for this and all of the other
diskutil verbs.
The top-to-bottom appearance of partitions in diskutil list
always indicates the on-disk ordering. BSD disk identifiers
may, in certain circumstances, not appear in slice-numerical
order when viewed this way. This is normal and is likely the
result of a recent partition map editing operation in which
:
-
Sep 26, 2016 4:27 AM in response to allowinby Loner T,What is the version of Windows? Does the installation use NTFS?
The partition table and other outputs look clean. From Terminal, please run the following command and post the output.
diskutil mount /Volumes/BOOTCAMP disk0s3
If the directory BOOTCAMP does not exist in /Volumes, it will give return an error.
The man commands are for you see what each command does. You do not need to post the output of these.
-
Sep 26, 2016 5:12 AM in response to Loner Tby allowin,hi, nice to see you again,
I have partitioned with diskutility the new drive and mooved with superduper my snow leopard, I haven't made any partition with Bootcamp assistant yet the disk is in one GUID partion. this is what I get with Terminal, it changes from:
dev/disk0: Suspicious MBR at sector 0 to dev/disk0: PMBR at sector 0
Last login: Mon Sep 26 13:41:14 on console
Asturias:~ Home$ sudo gpt -vv -r show /dev/disk0
WARNING: Improper use of the sudo command could lead to data loss
or the deletion of important system files. Please double-check your
typing when using sudo. Type "man sudo" for more information.
To proceed, enter your password, or type Ctrl-C to abort.
Password:
gpt show: /dev/disk0: mediasize=160041885696; sectorsize=512; blocks=312581808
gpt show: /dev/disk0: PMBR at sector 0
gpt show: /dev/disk0: Pri GPT at sector 1
gpt show: /dev/disk0: Sec GPT at sector 312581807
start size index contents
0 1 PMBR
1 1 Pri GPT header
2 32 Pri GPT table
34 6
40 409600 1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
409640 311909984 2 GPT part - 48465300-0000-11AA-AA11-00306543ECAC
312319624 262151
312581775 32 Sec GPT table
312581807 1 Sec GPT header
Asturias:~ Home$
OK ?
Now when I open diskutility and select the drive it doesn't show the the mount point that should say: Volumes/Atlas
it's just blank
-
Sep 26, 2016 5:25 AM in response to Loner Tby allowin,Asturias:~ Home$ diskutil mount /Volumes/BOOTCAMP disk0s3
Usage: diskutil mount [readOnly] [-mountPoint Path] DiskIdentifier|DeviceNode
Mount will mount the volume in the "standard" place (/Volumes), unless
an optional mount point is specified.
Asturias:~ Home$
-
Sep 26, 2016 5:28 AM in response to allowinby Loner T,Can you also post the Windows version for the record?
Atlas was the name used for the older copy of SL 10.6. You may need to rename the volume, if you want to see the same name.
You can create a FAT32 partition using either Disk Utility or BC Assistant. Please try the restore.