I extracted the 3 dmgs from the original appletv hard drive and put in a 32gb ssd using the "prepare a hard drive" instructions on ankwardtv. No problems so far, but using the same method with a 1tb hdd doesn't seem to work. Neither does atvdrive or atvcloner apps. Disk drive utility shows the recovery and osboot partitions to be 3 and 7 gb respectively, which is a bit odd, but the block nummers are correct as far as the terminal shows. What could be wrong?
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
1TB hard drive for gen 1
- Thread starter potatis
- Start date
- Sort by reaction score
Managed to start it with sudo path-to-app-executable. I get following output for without and with large disk mode, neither works:
Code:
AtvCloner 0.2
/dev/disk0
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *64.0 GB disk0
1: EFI 209.7 MB disk0s1
2: Apple_HFS Macintosh SSD 63.7 GB disk0s2
/dev/disk1
#: TYPE NAME SIZE IDENTIFIER
0: Apple_partition_scheme *500.1 GB disk1
1: Apple_partition_map 32.3 KB disk1s1
2: Apple_HFS Mammas 500.0 GB disk1s3
/dev/disk2
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *2.0 TB disk2
1: EFI 209.7 MB disk2s1
2: Apple_HFS Macally 2.0 TB disk2s2
/dev/disk3
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *1.0 TB disk3
1: EFI 314.6 MB disk3s1
2: Apple_HFS AtvTargetDrive 999.8 GB disk3s2
/dev/disk4
#: TYPE NAME SIZE IDENTIFIER
0: Transcend *63.2 GB disk4
New ATV Disk (NewHfs) Setup
Adding OSBoot partition with got …
Copying osboot.img with dd …
Copying recovery.img with dd …
Started partitioning on disk3
Unmounting disk
Creating the partition map
Waiting for the disks to reappear
Formatting disk3s2 as Mac OS Extended with name AtvTargetDrive
Initialized /dev/rdisk3s2 as a 931 GB HFS Plus volume
Mounting disk
Finished partitioning on disk3
/dev/disk3
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *1.0 TB disk3
1: EFI 314.6 MB disk3s1
2: Apple_HFS AtvTargetDrive 999.8 GB disk3s2
Unmount of all volumes on disk3 was successful
Unmount of all volumes on disk3 was successful
/dev/disk3s1 added
Unmount of all volumes on disk3 was successful
/dev/disk3s2 added
Unmount of all volumes on disk3 was successful
/dev/disk3s3 added
Unmount of all volumes on disk3 was successful
899+1 records in
899+1 records out
943714304 bytes transferred in 93.379407 secs (10106236 bytes/sec)
Unmount of all volumes on disk3 was successful
34+0 records in
34+0 records out
35651584 bytes transferred in 3.589682 secs (9931683 bytes/sec)
Unmount of all volumes on disk3 was successful
399+1 records in
399+1 records out
419405824 bytes transferred in 41.476782 secs (10111822 bytes/sec)
Unmount of all volumes on disk3 was successful
/dev/disk3s4 added
Unmount of disk3 failed: at least one volume could not be unmounted
Initialized /dev/rdisk3s4 as a 921 GB HFS Plus volume with a 81920k journal
Unmount of all volumes on disk3 was successful
Unmount of all volumes on disk3 was successful
start size index contents
0 1 PMBR
1 1 Pri GPT header
2 4 Pri GPT table
6 34
40 69632 1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
69672 819200 2 GPT part - 5265636F-7665-11AA-AA11-00306543ECAC
888872 1843200 3 GPT part - 48465300-0000-11AA-AA11-00306543ECAC
2732072 241458569 4 GPT part - 48465300-0000-11AA-AA11-00306543ECAC
244190641 4 Sec GPT table
244190645 1 Sec GPT header
/dev/disk0
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *64.0 GB disk0
1: EFI 209.7 MB disk0s1
2: Apple_HFS Macintosh SSD 63.7 GB disk0s2
/dev/disk1
#: TYPE NAME SIZE IDENTIFIER
0: Apple_partition_scheme *500.1 GB disk1
1: Apple_partition_map 32.3 KB disk1s1
2: Apple_HFS Mammas 500.0 GB disk1s3
/dev/disk2
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *2.0 TB disk2
1: EFI 209.7 MB disk2s1
2: Apple_HFS Macally 2.0 TB disk2s2
/dev/disk3
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *1.0 TB disk3
1: EFI 285.2 MB disk3s1
2: Apple_Recovery 3.4 GB disk3s2
3: Apple_HFS OSBoot 7.5 GB disk3s3
4: Apple_HFS Media 989.0 GB disk3s4
/dev/disk4
#: TYPE NAME SIZE IDENTIFIER
0: Transcend *63.2 GB disk4
New ATV Disk (Diskutil) Setup
Adding OSBoot partition with got …
New ATV Disk (Diskutil) Setup
Adding OSBoot partition with got …
Copying osboot.img with dd …
Copying recovery.img with dd …
Started partitioning on disk3
Unmounting disk
Creating the partition map
Waiting for the disks to reappear
Formatting disk3s2 as Mac OS Extended with name AtvTargetDrive
Initialized /dev/rdisk3s2 as a 931 GB HFS Plus volume
Mounting disk
Finished partitioning on disk3
/dev/disk3
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *1.0 TB disk3
1: EFI 314.6 MB disk3s1
2: Apple_HFS AtvTargetDrive 999.8 GB disk3s2
Unmount of all volumes on disk3 was successful
Unmount of all volumes on disk3 was successful
/dev/disk3s1 added
Unmount of all volumes on disk3 was successful
/dev/disk3s2 added
Unmount of all volumes on disk3 was successful
/dev/disk3s3 added
Unmount of all volumes on disk3 was successful
/dev/disk3s4 added
Unmount of all volumes on disk3 was successful
Started erase on disk3s4 Media
Unmounting disk
Erasing
Initialized /dev/rdisk3s4 as a 921 GB HFS Plus volume with a 81920k journal
Mounting disk
Finished erase on disk3s4 Media
Unmount of all volumes on disk3 was successful
/dev/disk3s1 removed
Unmount of disk3 failed: at least one volume could not be unmounted
got remove: unable to open device '/dev/disk3': Resource busy
Unmount of all volumes on disk3 was successful
/dev/disk3s3 removed
Unmount of all volumes on disk3 was successful
/dev/disk3s1 added
Unmount of all volumes on disk3 was successful
got add: /dev/disk3: error: entry at index 2 is not free
Unmount of all volumes on disk3 was successful
/dev/disk3s3 added
Unmount of all volumes on disk3 was successful
899+1 records in
899+1 records out
943714304 bytes transferred in 91.347353 secs (10331053 bytes/sec)
Unmount of all volumes on disk3 was successful
34+0 records in
34+0 records out
35651584 bytes transferred in 3.459658 secs (10304944 bytes/sec)
Unmount of all volumes on disk3 was successful
399+1 records in
399+1 records out
419405824 bytes transferred in 40.656954 secs (10315722 bytes/sec)
Unmount of all volumes on disk3 was successful
Initialized /dev/rdisk3s4 as a 921 GB HFS Plus volume with a 81920k journal
Unmount of all volumes on disk3 was successful
Unmount of all volumes on disk3 was successful
start size index contents
0 1 PMBR
1 1 Pri GPT header
2 4 Pri GPT table
6 34
40 69632 1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
69672 819200 2 GPT part - 5265636F-7665-11AA-AA11-00306543ECAC
888872 1843200 3 GPT part - 48465300-0000-11AA-AA11-00306543ECAC
2732072 241425801 4 GPT part - 48465300-0000-11AA-AA11-00306543ECAC
244157873 32768
244190641 4 Sec GPT table
244190645 1 Sec GPT header
/dev/disk0
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *64.0 GB disk0
1: EFI 209.7 MB disk0s1
2: Apple_HFS Macintosh SSD 63.7 GB disk0s2
/dev/disk1
#: TYPE NAME SIZE IDENTIFIER
0: Apple_partition_scheme *500.1 GB disk1
1: Apple_partition_map 32.3 KB disk1s1
2: Apple_HFS Mammas 500.0 GB disk1s3
/dev/disk2
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *2.0 TB disk2
1: EFI 209.7 MB disk2s1
2: Apple_HFS Macally 2.0 TB disk2s2
/dev/disk3
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *1.0 TB disk3
1: EFI 285.2 MB disk3s1
2: Apple_Recovery 3.4 GB disk3s2
3: Apple_HFS OSBoot 7.5 GB disk3s3
4: Apple_HFS Media 988.9 GB disk3s4
/dev/disk4
#: TYPE NAME SIZE IDENTIFIER
0: Transcend *63.2 GB disk4It seems the partition blocks need to be multiplied by 4096 to get the correct partition size. So I made the three first partitions as following:
-b 6 -i 1 -s 8704
-b 8710 -i 2 -s 102400
-b 111110 -i 3 -s 230400
Still no luck when putting the drive on the ATV.
-b 6 -i 1 -s 8704
-b 8710 -i 2 -s 102400
-b 111110 -i 3 -s 230400
Still no luck when putting the drive on the ATV.
Last edited:
Can it be that ATV doesn't work with 4k sector "Advanced Format" drives, if so what drives can be used?
hmm, Large disk (experimental) should fix that, basically is uses diskutil to pad the partitons to work out.
The external drive I have used have all been WD and yes, there was a TB one.
The atv 1 takes IDE drives yes? I didn't know there were 1tb IDE drives that would fit! Or are we talking externals?
Same issue as potatis
potatis were you able to resolve your large drive issue?
I have exactly the same problem as you and am unsure of how to fix it. I am using a brand new Samsung 1TB drive, Model #: ST1000LM024
What is more is that I am running AtvCloner on OSX 10.8.2 and am unable to bypass the permission denied issue even when I run AtvCloner as root via sudo. The reason I know I have the same issue is that I tried to manually partition the drive using the procedure here...
http://wiki.awkwardtv.org/wiki/Prepare_a_Hard_Drive
...and here is what I get:
/dev/disk1
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *1.0 TB disk1
1: EFI 285.2 MB disk1s1
2: Apple_Recovery 3.4 GB disk1s2
3: Apple_HFS 7.5 GB disk1s3
4: Apple_HFS Media 989.0 GB disk1s4
start size index contents
0 1 PMBR
1 1 Pri GPT header
2 32 Pri GPT table
34 6
40 69632 1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
69672 819200 2 GPT part - 5265636F-7665-11AA-AA11-00306543ECAC
888872 1843200 3 GPT part - 48465300-0000-11AA-AA11-00306543ECAC
2732072 75408048 4 GPT part - 48465300-0000-11AA-AA11-00306543ECAC
78140120 7
78140127 32 Sec GPT table
78140159 1 Sec GPT header
... below is the output of AtvCloner when I run it as root using sudo...
New ATV Disk (Diskutil) Setup
Adding OSBoot partition with got
New ATV Disk (Diskutil) Setup
Adding OSBoot partition with got
Copying osboot.img with dd
Copying recovery.img with dd
Started partitioning on disk1
Unmounting disk
Creating the partition map
Waiting for the disks to reappear
Formatting disk1s2 as Mac OS Extended with name AtvTargetDrive
Initialized /dev/rdisk1s2 as a 931 GB HFS Plus volume
Mounting disk
Finished partitioning on disk1
/dev/disk1
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *1.0 TB disk1
1: EFI 209.7 MB disk1s1
2: Apple_HFS AtvTargetDrive 999.9 GB disk1s2
Unmount of all volumes on disk1 was successful
gpt destroy: unable to open device '/dev/disk1': Permission denied
got create: unable to open device '/dev/disk1': Permission denied
Unmount of all volumes on disk1 was successful
got add: unable to open device '/dev/disk1': Permission denied
Unmount of all volumes on disk1 was successful
got add: unable to open device '/dev/disk1': Permission denied
Unmount of all volumes on disk1 was successful
got add: unable to open device '/dev/disk1': Permission denied
Unmount of all volumes on disk1 was successful
got add: unable to open device '/dev/disk1': Permission denied
Unmount of all volumes on disk1 was successful
Unable to find disk for /dev/disk1s4
Unmount of all volumes on disk1 was successful
gpt remove: unable to open device '/dev/disk1': Permission denied
Unmount of all volumes on disk1 was successful
gpt remove: unable to open device '/dev/disk1': Permission denied
Unmount of all volumes on disk1 was successful
gpt remove: unable to open device '/dev/disk1': Permission denied
Unmount of all volumes on disk1 was successful
got add: unable to open device '/dev/disk1': Permission denied
Unmount of all volumes on disk1 was successful
got add: unable to open device '/dev/disk1': Permission denied
Unmount of all volumes on disk1 was successful
got add: unable to open device '/dev/disk1': Permission denied
Unmount of all volumes on disk1 was successful
dd: /dev/disk1s3: Permission denied
Unmount of all volumes on disk1 was successful
dd: /dev/disk1s1: Permission denied
Unmount of all volumes on disk1 was successful
dd: /dev/disk1s2: Permission denied
Unmount of all volumes on disk1 was successful
newfs_hfs: cannot create filesystem on /dev/rdisk1s4: No such file or directory
Unmount of all volumes on disk1 was successful
Unmount of all volumes on disk1 was successful
got show: unable to open device '/dev/disk1': Permission denied
/dev/disk0
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *750.2 GB disk0
1: EFI 209.7 MB disk0s1
2: Apple_HFS Macintosh HD 749.3 GB disk0s2
3: Apple_Boot Recovery HD 650.0 MB disk0s3
/dev/disk1
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *1.0 TB disk1
1: EFI 209.7 MB disk1s1
2: Apple_HFS AtvTargetDrive 999.9 GB disk1s2
potatis were you able to resolve your large drive issue?
I have exactly the same problem as you and am unsure of how to fix it. I am using a brand new Samsung 1TB drive, Model #: ST1000LM024
What is more is that I am running AtvCloner on OSX 10.8.2 and am unable to bypass the permission denied issue even when I run AtvCloner as root via sudo. The reason I know I have the same issue is that I tried to manually partition the drive using the procedure here...
http://wiki.awkwardtv.org/wiki/Prepare_a_Hard_Drive
...and here is what I get:
/dev/disk1
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *1.0 TB disk1
1: EFI 285.2 MB disk1s1
2: Apple_Recovery 3.4 GB disk1s2
3: Apple_HFS 7.5 GB disk1s3
4: Apple_HFS Media 989.0 GB disk1s4
start size index contents
0 1 PMBR
1 1 Pri GPT header
2 32 Pri GPT table
34 6
40 69632 1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
69672 819200 2 GPT part - 5265636F-7665-11AA-AA11-00306543ECAC
888872 1843200 3 GPT part - 48465300-0000-11AA-AA11-00306543ECAC
2732072 75408048 4 GPT part - 48465300-0000-11AA-AA11-00306543ECAC
78140120 7
78140127 32 Sec GPT table
78140159 1 Sec GPT header
... below is the output of AtvCloner when I run it as root using sudo...
New ATV Disk (Diskutil) Setup
Adding OSBoot partition with got
New ATV Disk (Diskutil) Setup
Adding OSBoot partition with got
Copying osboot.img with dd
Copying recovery.img with dd
Started partitioning on disk1
Unmounting disk
Creating the partition map
Waiting for the disks to reappear
Formatting disk1s2 as Mac OS Extended with name AtvTargetDrive
Initialized /dev/rdisk1s2 as a 931 GB HFS Plus volume
Mounting disk
Finished partitioning on disk1
/dev/disk1
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *1.0 TB disk1
1: EFI 209.7 MB disk1s1
2: Apple_HFS AtvTargetDrive 999.9 GB disk1s2
Unmount of all volumes on disk1 was successful
gpt destroy: unable to open device '/dev/disk1': Permission denied
got create: unable to open device '/dev/disk1': Permission denied
Unmount of all volumes on disk1 was successful
got add: unable to open device '/dev/disk1': Permission denied
Unmount of all volumes on disk1 was successful
got add: unable to open device '/dev/disk1': Permission denied
Unmount of all volumes on disk1 was successful
got add: unable to open device '/dev/disk1': Permission denied
Unmount of all volumes on disk1 was successful
got add: unable to open device '/dev/disk1': Permission denied
Unmount of all volumes on disk1 was successful
Unable to find disk for /dev/disk1s4
Unmount of all volumes on disk1 was successful
gpt remove: unable to open device '/dev/disk1': Permission denied
Unmount of all volumes on disk1 was successful
gpt remove: unable to open device '/dev/disk1': Permission denied
Unmount of all volumes on disk1 was successful
gpt remove: unable to open device '/dev/disk1': Permission denied
Unmount of all volumes on disk1 was successful
got add: unable to open device '/dev/disk1': Permission denied
Unmount of all volumes on disk1 was successful
got add: unable to open device '/dev/disk1': Permission denied
Unmount of all volumes on disk1 was successful
got add: unable to open device '/dev/disk1': Permission denied
Unmount of all volumes on disk1 was successful
dd: /dev/disk1s3: Permission denied
Unmount of all volumes on disk1 was successful
dd: /dev/disk1s1: Permission denied
Unmount of all volumes on disk1 was successful
dd: /dev/disk1s2: Permission denied
Unmount of all volumes on disk1 was successful
newfs_hfs: cannot create filesystem on /dev/rdisk1s4: No such file or directory
Unmount of all volumes on disk1 was successful
Unmount of all volumes on disk1 was successful
got show: unable to open device '/dev/disk1': Permission denied
/dev/disk0
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *750.2 GB disk0
1: EFI 209.7 MB disk0s1
2: Apple_HFS Macintosh HD 749.3 GB disk0s2
3: Apple_Boot Recovery HD 650.0 MB disk0s3
/dev/disk1
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *1.0 TB disk1
1: EFI 209.7 MB disk1s1
2: Apple_HFS AtvTargetDrive 999.9 GB disk1s2
The issue I noted above is definitely occurring due to my 1TB drive having the Advanced Drive feature that effectively stores 4096 bytes / block rather than the conventional 512 bytes per block.
http://en.wikipedia.org/wiki/Advanced_Format
Has anyone been able to use a newer SATA hard drive with the Advanced Format feature to work inside AppleTV1 (using a SATA to PATA interface card)?
I would assume that in creating your partitions you could just take the traditional sizes an divide by 8 since there are 8 traditional 512 byte / blocks stored in one Advanced Format hard drive block. But I am not sure if this simple approach works. I will ultimately try this and report back, but it would be helpful if anyone has done this successfully and could comment on how they did it and how their drive is partitioned in terms of blocks.
Thanks.
http://en.wikipedia.org/wiki/Advanced_Format
Has anyone been able to use a newer SATA hard drive with the Advanced Format feature to work inside AppleTV1 (using a SATA to PATA interface card)?
I would assume that in creating your partitions you could just take the traditional sizes an divide by 8 since there are 8 traditional 512 byte / blocks stored in one Advanced Format hard drive block. But I am not sure if this simple approach works. I will ultimately try this and report back, but it would be helpful if anyone has done this successfully and could comment on how they did it and how their drive is partitioned in terms of blocks.
Thanks.
Omne666: not sure if it fits in an untouched unit.., my unit (bought 2nd hand) was pre modded to make it fit. I think basically you can cut off half of the long metal rod next to the fan.
Pasormac: managed to break my 1TB Hitachi drive so I put it on hold for now. Not sure what to do, maybe buy a WD drive instead, they got some hybrid models coming (hoping the ATV OS would locate to the SSD part for absolute silence when not using it).
Reading that Advanced Format info gives me the idea that different brands of 1TB hard drives use different methods of emulating 512 block size, and maybe only the correct method is ok for the ATV.
Did you try exchanging the values in the ankwardtv guide for the ones I tried?
For the three first partitions:
-b 6 -i 1 -s 8704
-b 8710 -i 2 -s 102400
-b 111110 -i 3 -s 230400
Not sure if it should begin on 6, could also be 34 or 40 from what I seen when formatting it with disk utility, so try also adding 28 and 34 to everything respectively).
As for AtvCloner I launched it from terminal with:
sudo /Applications/AtvCloner.app/Contents/MacOS/AtvCloner
Though I also end up with a single "AtvTargetDrive" partition which can't be right.
Pasormac: managed to break my 1TB Hitachi drive so I put it on hold for now. Not sure what to do, maybe buy a WD drive instead, they got some hybrid models coming (hoping the ATV OS would locate to the SSD part for absolute silence when not using it).
Reading that Advanced Format info gives me the idea that different brands of 1TB hard drives use different methods of emulating 512 block size, and maybe only the correct method is ok for the ATV.
Did you try exchanging the values in the ankwardtv guide for the ones I tried?
For the three first partitions:
-b 6 -i 1 -s 8704
-b 8710 -i 2 -s 102400
-b 111110 -i 3 -s 230400
Not sure if it should begin on 6, could also be 34 or 40 from what I seen when formatting it with disk utility, so try also adding 28 and 34 to everything respectively).
As for AtvCloner I launched it from terminal with:
sudo /Applications/AtvCloner.app/Contents/MacOS/AtvCloner
Though I also end up with a single "AtvTargetDrive" partition which can't be right.
Last edited:
Thats because AtvCloner does a quick hfs single partitioning before it makes the actual atv partition setup to make sure anything else is blown away first. You are ending up with that because atvcloner is borking when it gets to permission denied on ML. I do not have a ML setup so have now way right now to fix it.
potatis.... I am going to try what you suggest and partition based on dividing by 8 and trying starting variations with that begin with 6, 34 or 40. I can do it manually so I don't need AtvCloner (but it's time consuming). Will report back on this later tonight.
dynaflash, were you the author of AtvCloner? Nice job.... too bad that ML broke it. Makes me think I should have kept my old iMac on an older OsX version rather than running to upgrade.
AtvCloner is nice and handy to make this whole process fast but there are manual ways to make these partitions. It's just so time consuming to input the commands in manually. Gotta do it to see if this works. Will report back later tonight.
For those interested, the PATA to SATA adapter I bought was from the link below (only $7.75 with free shipping). It took about 8 business days to be delivered (to Toronto, Canada) and it works with my iMac - USB - PATA interface adapter so I know it will work with the AppleTV1.
http://dx.com/p/sata-to-2-5-ide-male-hard-drive-adapter-card-horizontal-19735
dynaflash, were you the author of AtvCloner? Nice job.... too bad that ML broke it. Makes me think I should have kept my old iMac on an older OsX version rather than running to upgrade.
AtvCloner is nice and handy to make this whole process fast but there are manual ways to make these partitions. It's just so time consuming to input the commands in manually. Gotta do it to see if this works. Will report back later tonight.
For those interested, the PATA to SATA adapter I bought was from the link below (only $7.75 with free shipping). It took about 8 business days to be delivered (to Toronto, Canada) and it works with my iMac - USB - PATA interface adapter so I know it will work with the AppleTV1.
http://dx.com/p/sata-to-2-5-ide-male-hard-drive-adapter-card-horizontal-19735
Yes. I plan to get into ML pretty quick here, but for now have no way to test fixes. I can change the block size that AtvCloner uses but like I said have no way to test it. If you get it fixed using a different block size post the results here and I can change it in atvcloner. The sudo thing is a pita. We are having issues with HB on ML as well due to ML's overly aggressive energy saving mode. Working on a patch for that as well.
Exactly, I got very tired of doing it manually so wrote atvcloner to make it more automated and point and click. Basically ... the obj-C gui just runs mostly the same commands you do with terminal but uses NSTask to run the dd, gpt, hfs and diskutil terminal commands. Not sure how to get around the permission denied errors in ML. Will look into it though. Sorry for the problems.
Maybe it's only the -b (if standing for begin and not blocks) or -s (if standing for start and not size) values that should be tried to be changed, think it's -b though, correct me if I'm wrong. (b+s on one partition = b for the next partition as you can see). The ankwardtv guide says which one is which, and the values above gave me the correct sizes with a 1TB drive. Although it wouldn't work for me I might have an incompatible hard drive or adapter (some only support 500gb drives) so it could work for you.
Last edited:
well, like I said I am not on ML (due to issues with some other projects I work on) and as well do not have access to a drive like the one you are having issues with. So its kind of a shot in the dark on my end.
First thing is to get around the permission errors with gpt which show up in the log. This is why the partitions are not created and everything falls apart. If anyone can get it to work on said drive and supply the terminal commands that fix it I am more than happy to hack atvcloner and put a beta up to see if it works.
First thing is to get around the permission errors with gpt which show up in the log. This is why the partitions are not created and everything falls apart. If anyone can get it to work on said drive and supply the terminal commands that fix it I am more than happy to hack atvcloner and put a beta up to see if it works.
Ok so the following partitions don't seem to work....
gpt add -b 6 -i 1 -s 8704 -t efi /dev/disk1
gpt add -b 8710 -i 2 -s 102400 -t 5265636F-7665-11AA-AA11-00306543ECAC
gpt add -b 111110 -i 3 -s 230400 -t hfs /dev/disk1
gpt add -b 341510 -i 4 -s 243849131 -t hfs /dev/disk1
Need to try something else. I wish someone could verify that they have done it using Advanced Format drives. Are all 1TB drives Advanced Format? I know others have been able to get 1TB drives to work.
Continuing to try something else....
gpt add -b 6 -i 1 -s 8704 -t efi /dev/disk1
gpt add -b 8710 -i 2 -s 102400 -t 5265636F-7665-11AA-AA11-00306543ECAC
gpt add -b 111110 -i 3 -s 230400 -t hfs /dev/disk1
gpt add -b 341510 -i 4 -s 243849131 -t hfs /dev/disk1
Need to try something else. I wish someone could verify that they have done it using Advanced Format drives. Are all 1TB drives Advanced Format? I know others have been able to get 1TB drives to work.
Continuing to try something else....
Seems like WD has a compatibility tool for AF drives, maybe there's something similar at Samsung's site?
http://www.wdc.com/global/products/features/?id=7&language=1
Edit; this?: http://www.seagate.com/support/inte...es/samsung-advanced-format-utility-master-dl/
http://www.wdc.com/global/products/features/?id=7&language=1
Edit; this?: http://www.seagate.com/support/inte...es/samsung-advanced-format-utility-master-dl/
Last edited:
Ok... so 3 attempts (one posted above) to make this Advanced Format Seagate/Samsung HD work, no success (so far).
Below is the partitioning table for the 3 attempts:
Attempt 1) -----------------------------------------------------------------------
start size index contents
0 1 PMBR
1 1 Pri GPT header
2 4 Pri GPT table
6 8704 1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
8710 102400 2 GPT part - 5265636F-7665-11AA-AA11-00306543ECAC
111110 230400 3 GPT part - 48465300-0000-11AA-AA11-00306543ECAC
341510 243849131 4 GPT part - 48465300-0000-11AA-AA11-00306543ECAC
244190641 4 Sec GPT table
244190645 1 Sec GPT header
Attempt 2) -----------------------------------------------------------------------
start size index contents
0 1 PMBR
1 1 Pri GPT header
2 4 Pri GPT table
6 34
40 8704 1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
8744 102400 2 GPT part - 5265636F-7665-11AA-AA11-00306543ECAC
111144 230400 3 GPT part - 48465300-0000-11AA-AA11-00306543ECAC
341544 243849090 4 GPT part - 48465300-0000-11AA-AA11-00306543ECAC
244190634 7
244190641 4 Sec GPT table
244190645 1 Sec GPT header
Attempt 3) -----------------------------------------------------------------------
start size index contents
0 1 PMBR
1 1 Pri GPT header
2 4 Pri GPT table
6 28
34 8704 1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
8738 102400 2 GPT part - 5265636F-7665-11AA-AA11-00306543ECAC
111138 230400 3 GPT part - 48465300-0000-11AA-AA11-00306543ECAC
341538 243849090 4 GPT part - 48465300-0000-11AA-AA11-00306543ECAC
244190628 13
244190641 4 Sec GPT table
244190645 1 Sec GPT header
----------------------------------------------------------------------------------
The partition sizes for all 3 attempts above are as follows:
/dev/disk1
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *1.0 TB disk1
1: EFI 35.7 MB disk1s1
2: Apple_Recovery 419.4 MB disk1s2
3: Apple_HFS OSBoot 943.7 MB disk1s3
4: Apple_HFS Media 998.8 GB disk1s4
Partition sizes mimic the initial 40Gig hard drive other than the Media partition, but obviously the block starting points and sizes differ due to the number of bytes/block being 8x bigger than non-Advanced Format HD's.
You'll note there is a small unused part of the drive before partition 1 and after partition 4 in some of the attempts. I tried to mimic what was on the initial 40Gig hard drive. But unfortunately the above did not work.
I am not sure you would use a compatibility tool for this sort of application. It seems the compatibility tool would only be used in an open system like Windows XP that doesn't support the new drives. But AppleTV is a closed system and I don't think there is any way to introduce such a tool.
As I sit here and try to think about what could be wrong, I am starting to wonder about how AppleTV knows where to look on the drive (i.e. what block on the drive). It must be hardcoded somewhere and with the blocks now representing 8 bytes rather than 1, I am wondering if the data is now being stored intra-block and when apple tries to reference certain blocks to kick off the boot program it is getting lost and going to some other location. No clue if this is the case, just trying to reason it out.
Today I thought about alternative drives... I realized I had a 1Gig 2.5" Western Digital Passport external drive enclosure. I tested the block sizes in it and sure enough it was 512 bytes / block - BINGO! But when I looked up how to disassemble these on YouTube, I saw that the drives have been modified to take away the SATA port on the back. They go directly to a USB port output, so taking this apart and trying to use that drive would be useless unless I obtained a USB - PATA adapter.
Hopefully tomorrow will be a better day...
Below is the partitioning table for the 3 attempts:
Attempt 1) -----------------------------------------------------------------------
start size index contents
0 1 PMBR
1 1 Pri GPT header
2 4 Pri GPT table
6 8704 1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
8710 102400 2 GPT part - 5265636F-7665-11AA-AA11-00306543ECAC
111110 230400 3 GPT part - 48465300-0000-11AA-AA11-00306543ECAC
341510 243849131 4 GPT part - 48465300-0000-11AA-AA11-00306543ECAC
244190641 4 Sec GPT table
244190645 1 Sec GPT header
Attempt 2) -----------------------------------------------------------------------
start size index contents
0 1 PMBR
1 1 Pri GPT header
2 4 Pri GPT table
6 34
40 8704 1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
8744 102400 2 GPT part - 5265636F-7665-11AA-AA11-00306543ECAC
111144 230400 3 GPT part - 48465300-0000-11AA-AA11-00306543ECAC
341544 243849090 4 GPT part - 48465300-0000-11AA-AA11-00306543ECAC
244190634 7
244190641 4 Sec GPT table
244190645 1 Sec GPT header
Attempt 3) -----------------------------------------------------------------------
start size index contents
0 1 PMBR
1 1 Pri GPT header
2 4 Pri GPT table
6 28
34 8704 1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
8738 102400 2 GPT part - 5265636F-7665-11AA-AA11-00306543ECAC
111138 230400 3 GPT part - 48465300-0000-11AA-AA11-00306543ECAC
341538 243849090 4 GPT part - 48465300-0000-11AA-AA11-00306543ECAC
244190628 13
244190641 4 Sec GPT table
244190645 1 Sec GPT header
----------------------------------------------------------------------------------
The partition sizes for all 3 attempts above are as follows:
/dev/disk1
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *1.0 TB disk1
1: EFI 35.7 MB disk1s1
2: Apple_Recovery 419.4 MB disk1s2
3: Apple_HFS OSBoot 943.7 MB disk1s3
4: Apple_HFS Media 998.8 GB disk1s4
Partition sizes mimic the initial 40Gig hard drive other than the Media partition, but obviously the block starting points and sizes differ due to the number of bytes/block being 8x bigger than non-Advanced Format HD's.
You'll note there is a small unused part of the drive before partition 1 and after partition 4 in some of the attempts. I tried to mimic what was on the initial 40Gig hard drive. But unfortunately the above did not work.
I am not sure you would use a compatibility tool for this sort of application. It seems the compatibility tool would only be used in an open system like Windows XP that doesn't support the new drives. But AppleTV is a closed system and I don't think there is any way to introduce such a tool.
As I sit here and try to think about what could be wrong, I am starting to wonder about how AppleTV knows where to look on the drive (i.e. what block on the drive). It must be hardcoded somewhere and with the blocks now representing 8 bytes rather than 1, I am wondering if the data is now being stored intra-block and when apple tries to reference certain blocks to kick off the boot program it is getting lost and going to some other location. No clue if this is the case, just trying to reason it out.
Today I thought about alternative drives... I realized I had a 1Gig 2.5" Western Digital Passport external drive enclosure. I tested the block sizes in it and sure enough it was 512 bytes / block - BINGO! But when I looked up how to disassemble these on YouTube, I saw that the drives have been modified to take away the SATA port on the back. They go directly to a USB port output, so taking this apart and trying to use that drive would be useless unless I obtained a USB - PATA adapter.
Hopefully tomorrow will be a better day...