Junior Member
I finally took the 11.0d update in anticipation of TiVo's big announcement; everything ran fine for about 3 days with a null-initrd kernel and a patched tivoapp (cci & noencrypt). Then one night my S3 rebooted, and it's been rebooting every 20 minutes (almost down to the second) since then.
tverr lists three fatal error in short order: Activity TvSyncActivity strayed!, Activity TvSyncActivity assertion failure, and Thread died due to signal -2. Here is a sample
When it's running, everything is fine, but then the clock strikes 20 and...boom. I've been pulling my hair and would welcome any suggestions. ThanksCode:Mar 3 22:13:05 (none) TmkAssertionFailure[18089]: : (Audit, line 38 ()) Mar 3 22:13:05 (none) Activity TvSyncActivity[18089]: Tmk Fatal Error: Activity TvSyncActivity <18089> strayed! (block timestamp 35160987197611) Mar 3 22:13:05 (none) Activity TvSyncActivity[18089]: bt -t /tvbin/tivoapp Mar 3 22:13:05 (none) Activity TvSyncActivity[18089]: tcd 1 Mar 3 22:13:05 (none) Activity TvSyncActivity[18089]: hpk Gen05 Mar 3 22:13:05 (none) Activity TvSyncActivity[18089]: build b-11-0-mr @334825 2009.06.02-1007 release-mips [] Mar 3 22:13:05 (none) Activity TvSyncActivity[18089]: pack 11.0d-01-2 Mar 3 22:13:05 (none) Activity TvSyncActivity[18089]: read 0x00400000 /tvbin/tivoapp Mar 3 22:13:05 (none) Activity TvSyncActivity[18089]: read 0x04000000 /lib/libc.so.6 Mar 3 22:13:05 (none) Activity TvSyncActivity[18089]: read 0x04200000 /lib/libm.so.6 Mar 3 22:13:05 (none) Activity TvSyncActivity[18089]: read 0x04400000 /lib/libpthread.so.0 Mar 3 22:13:05 (none) Activity TvSyncActivity[18089]: read 0x04600000 /lib/libutil.so.1 Mar 3 22:13:06 (none) Activity TvSyncActivity[18089]: read 0x04800000 /lib/libtvutil.so Mar 3 22:13:06 (none) Activity TvSyncActivity[18089]: read 0x04a00000 /lib/libtmk.so Mar 3 22:13:06 (none) Activity TvSyncActivity[18089]: read 0x04c00000 /lib/libtvstructures.so Mar 3 22:13:06 (none) Activity TvSyncActivity[18089]: read 0x2aaa8000 /lib/ld.so.1 Mar 3 22:13:06 (none) Activity TvSyncActivity[18089]: read 0x2ab08000 /platform/lib/libmp3dec.so Mar 3 22:13:06 (none) Activity TvSyncActivity[18089]: read 0x2ab58000 /platform/lib/libcdsassetsentinelasf.so Mar 3 22:13:06 (none) Activity TvSyncActivity[18089]: read 0x2aba0000 /platform/lib/libmomcds.so Mar 3 22:13:06 (none) Activity TvSyncActivity[18089]: read 0x2abe8000 /platform/lib/libmomasf.so Mar 3 22:13:06 (none) Activity TvSyncActivity[18089]: read 0x2ac38000 /platform/lib/libhpkhl.so Mar 3 22:13:06 (none) Activity TvSyncActivity[18089]: read 0x2ad18000 /lib/libhpkoss.so Mar 3 22:13:06 (none) Activity TvSyncActivity[18089]: read 0x2ad68000 /platform/lib/libhpkll.so Mar 3 22:13:06 (none) Activity TvSyncActivity[18089]: read 0x2adb0000 /lib/librt.so.1 Mar 3 22:13:06 (none) Activity TvSyncActivity[18089]: read 0x2ae08000 /lib/libdl.so.2 Mar 3 22:13:06 (none) Activity TvSyncActivity[18089]: 0x04a8979c 0x00694b90 0x00545694 0x0055005c 0x00d30848 0x00d3067c 0x00d4056c 0x00d40da4 0x00d3d6f4 0x00d3bf88 0x00d3bb48 0x00d2cc08 0x00d2b148 0x00d2b0a8 0x00d3ab74 0x00d3aa48 0x00d2e7dc 0x00d2a5c4 0x00d2ab8c 0x04a2d818 0x04a2d448 0x04a2cca0 0x04a2bc20 0x04a3067c 0x04a6956c 0x04a2d818 0x04a3054c 0x04a2e4ac 0x04a3bd2c 0x04a3bc30 0x04a3bae0 0x04a3acb4 Mar 3 22:13:06 (none) Activity TvSyncActivity[18089]: Tmk Fatal Error: Activity TvSyncActivity <18089>: assertion failure Mar 3 22:13:06 (none) Activity TvSyncActivity[18089]: Tmk Fatal Error: Thread died due to signal -2 Mar 3 22:13:06 (none) Activity TvSyncActivity[18089]: Invoking rule 834: rebooting system Mar 3 22:17:57 (none) Billboard[299]: ERROR READING BILLBOARD! id = 589831 (GroupId: 9, ItemId: 7) Mar 3 22:33:14 (none) TmkAssertionFailure[533]: : (Audit, line 38 ()) Mar 3 22:33:14 (none) Activity TvSyncActivity[533]: Tmk Fatal Error: Activity TvSyncActivity <533> strayed! (block timestamp 174167008903) Mar 3 22:33:14 (none) Activity TvSyncActivity[533]: bt -t /tvbin/tivoapp Mar 3 22:33:14 (none) Activity TvSyncActivity[533]: tcd 1 Mar 3 22:33:14 (none) Activity TvSyncActivity[533]: hpk Gen05 Mar 3 22:33:14 (none) Activity TvSyncActivity[533]: build b-11-0-mr @334825 2009.06.02-1007 release-mips [] Mar 3 22:33:14 (none) Activity TvSyncActivity[533]: pack 11.0d-01-2 Mar 3 22:33:14 (none) Activity TvSyncActivity[533]: read 0x00400000 /tvbin/tivoapp Mar 3 22:33:14 (none) Activity TvSyncActivity[533]: read 0x04000000 /lib/libc.so.6 Mar 3 22:33:14 (none) Activity TvSyncActivity[533]: read 0x04200000 /lib/libm.so.6 Mar 3 22:33:14 (none) Activity TvSyncActivity[533]: read 0x04400000 /lib/libpthread.so.0 Mar 3 22:33:14 (none) Activity TvSyncActivity[533]: read 0x04600000 /lib/libutil.so.1 Mar 3 22:33:14 (none) Activity TvSyncActivity[533]: read 0x04800000 /lib/libtvutil.so Mar 3 22:33:14 (none) Activity TvSyncActivity[533]: read 0x04a00000 /lib/libtmk.so Mar 3 22:33:14 (none) Activity TvSyncActivity[533]: read 0x04c00000 /lib/libtvstructures.so Mar 3 22:33:14 (none) Activity TvSyncActivity[533]: read 0x2aaa8000 /lib/ld.so.1 Mar 3 22:33:14 (none) Activity TvSyncActivity[533]: read 0x2ab08000 /platform/lib/libmp3dec.so Mar 3 22:33:14 (none) Activity TvSyncActivity[533]: read 0x2ab58000 /platform/lib/libcdsassetsentinelasf.so Mar 3 22:33:14 (none) Activity TvSyncActivity[533]: read 0x2aba0000 /platform/lib/libmomcds.so Mar 3 22:33:14 (none) Activity TvSyncActivity[533]: read 0x2abe8000 /platform/lib/libmomasf.so Mar 3 22:33:14 (none) Activity TvSyncActivity[533]: read 0x2ac38000 /platform/lib/libhpkhl.so Mar 3 22:33:14 (none) Activity TvSyncActivity[533]: read 0x2ad18000 /lib/libhpkoss.so Mar 3 22:33:14 (none) Activity TvSyncActivity[533]: read 0x Mar 3 22:33:14 (none) Activity TvSyncActivity[533]: read 0x2ad68000 /platform/lib/libhpkll.so Mar 3 22:33:14 (none) Activity TvSyncActivity[533]: read 0x2adb0000 /lib/librt.so.1 Mar 3 22:33:14 (none) Activity TvSyncActivity[533]: read 0x2ae08000 /lib/libdl.so.2 Mar 3 22:33:14 (none) Activity TvSyncActivity[533]: 0x04a8979c 0x00694b90 0x00545694 0x0055005c 0x00d30848 0x00d3067c 0x00d4056c 0x00d40da4 0x00d3d6f4 0x00d3bf88 0x00d3bb48 0x00d2cc08 0x00d2b148 0x00d2b0a8 0x00d3ab74 0x00d3aa48 0x00d2e7dc 0x00d2a5c4 0x00d2ab8c 0x04a2d818 0x04a2d448 0x04a2cca0 0x04a2bc20 0x04a3067c 0x04a6956c 0x04a2d818 0x04a3054c 0x04a2e4ac 0x04a3bd2c 0x04a3bc30 0x04a3bae0 0x04a3acb4 Mar 3 22:33:14 (none) Activity TvSyncActivity[533]: Tmk Fatal Error: Activity TvSyncActivity <533>: assertion failure Mar 3 22:33:14 (none) Activity TvSyncActivity[533]: Tmk Fatal Error: Thread died due to signal -2 Mar 3 22:33:14 (none) Activity TvSyncActivity[533]: Invoking rule 834: rebooting system Mar 3 22:38:03 (none) Billboard[299]: ERROR READING BILLBOARD! id = 589831 (GroupId: 9, ItemId: 7) Mar 3 22:53:19 (none) TmkAssertionFailure[538]: : (Audit, line 38 ()) Mar 3 22:53:19 (none) Activity TvSyncActivity[538]: Tmk Fatal Error: Activity TvSyncActivity <538> strayed! (block timestamp 173754967250) Mar 3 22:53:19 (none) Activity TvSyncActivity[538]: bt -t /tvbin/tivoapp Mar 3 22:53:19 (none) Activity TvSyncActivity[538]: tcd 1 Mar 3 22:53:19 (none) Activity TvSyncActivity[538]: hpk Gen05 Mar 3 22:53:19 (none) Activity TvSyncActivity[538]: build b-11-0-mr @334825 2009.06.02-1007 release-mips [] Mar 3 22:53:19 (none) Activity TvSyncActivity[538]: pack 11.0d-01-2 Mar 3 22:53:19 (none) Activity TvSyncActivity[538]: read 0x00400000 /tvbin/tivoapp Mar 3 22:53:19 (none) Activity TvSyncActivity[538]: read 0x04000000 /lib/libc.so.6 Mar 3 22:53:19 (none) Activity TvSyncActivity[538]: read 0x04200000 /lib/libm.so.6 Mar 3 22:53:19 (none) Activity TvSyncActivity[538]: read 0x04400000 /lib/libpthread.so.0 Mar 3 22:53:19 (none) Activity TvSyncActivity[538]: read 0x04600000 /lib/libutil.so.1 Mar 3 22:53:19 (none) Activity TvSyncActivity[538]: read 0x04800000 /lib/libtvutil.so Mar 3 22:53:19 (none) Activity TvSyncActivity[538]: read 0x04a00000 /lib/libtmk.so Mar 3 22:53:19 (none) Activity TvSyncActivity[538]: read 0x04c00000 /lib/libtvstructures.so Mar 3 22:53:19 (none) Activity TvSyncActivity[538]: read 0x2aaa8000 /lib/ld.so.1 Mar 3 22:53:20 (none) Activity TvSyncActivity[538]: read 0x2ab08000 /platform/lib/libmp3dec.so Mar 3 22:53:20 (none) Activity TvSyncActivity[538]: read 0x2ab58000 /platform/lib/libcdsassetsentinelasf.so Mar 3 22:53:20 (none) Activity TvSyncActivity[538]: read 0x2aba0000 /platform/lib/libmomcds.so Mar 3 22:53:20 (none) Activity TvSyncActivity[538]: read 0x2abe8000 /platform/lib/libmomasf.so Mar 3 22:53:20 (none) Activity TvSyncActivity[538]: read 0x2ac38000 /platform/lib/libhpkhl.so Mar 3 22:53:20 (none) Activity TvSyncActivity[538]: read 0x2ad18000 /lib/libhpkoss.so Mar 3 22:53:20 (none) Activity TvSyncActivity[538]: read 0x2ad68000 /platform/lib/libhpkll.so Mar 3 22:53:20 (none) Activity TvSyncActivity[538]: read 0x2adb0000 /lib/librt.so.1 Mar 3 22:53:20 (none) Activity TvSyncActivity[538]: read 0x2ae08000 /lib/libdl.so.2 Mar 3 22:53:20 (none) Activity TvSyncActivity[538]: 0x04a8979c 0x00694b90 0x00545694 0x0055005c 0x00d30848 0x00d3067c 0x00d4056c 0x00d40da4 0x00d3d6f4 0x00d3bf88 0x00d3bb48 0x00d2cc08 0x00d2b148 0x00d2b0a8 0x00d3ab74 0x00d3aa48 0x00d2e7dc 0x00d2a5c4 0x00d2ab8c 0x04a2d818 0x04a2d448 0x04a2cca0 0x04a2bc20 0x04a3067c 0x04a6956c 0x04a2d818 0x04a3054c 0x04a2e4ac 0x04a3bd2c 0x04a3bc30 0x04a3bae0 0x04a3acb4 Mar 3 22:53:20 (none) Activity TvSyncActivity[538]: Tmk Fatal Error: Activity TvSyncActivity <538>: assertion failure Mar 3 22:53:20 (none) Activity TvSyncActivity[538]: Tmk Fatal Error: Thread died due to signal -2 Mar 3 22:53:20 (none) Activity TvSyncActivity[538]: Invoking rule 834: rebooting system Mar 3 22:58:05 (none) Billboard[304]: ERROR READING BILLBOARD! id = 589831 (GroupId: 9, ItemId: 7) Mar 3 23:13:22 (none) TmkAssertionFailure[528]: : (Audit, line 38 ()) Mar 3 23:13:22 (none) Activity TvSyncActivity[528]: Tmk Fatal Error: Activity TvSyncActivity <528> strayed! (block timestamp 173418656615) Mar 3 23:13:22 (none) Activity TvSyncActivity[528]: bt -t /tvbin/tivoapp Mar 3 23:13:22 (none) Activity TvSyncActivity[528]: tcd 1 Mar 3 23:13:22 (none) Activity TvSyncActivity[528]: hpk Gen05 Mar 3 23:13:22 (none) Activity TvSyncActivity[528]: build b-11-0-mr @334825 2009.06.02-1007 release-mips [] Mar 3 23:13:22 (none) Activity TvSyncActivity[528]: pack 11.0d-01-2 Mar 3 23:13:22 (none) Activity TvSyncActivity[528]: read 0x00400000 /tvbin/tivoapp Mar 3 23:13:22 (none) Activity TvSyncActivity[528]: read 0x04000000 /lib/libc.so.6 Mar 3 23:13:22 (none) Activity TvSyncActivity[528]: read 0x04200000 /lib/libm.so.6 Mar 3 23:13:22 (none) Activity TvSyncActivity[528]: read 0x04400000 /lib/libpthread.so.0 Mar 3 23:13:22 (none) Activity TvSyncActivity[528]: read 0x04600000 /lib/libutil.so.1 Mar 3 23:13:22 (none) Activity TvSyncActivity[528]: read 0x04800000 /lib/libtvutil.so Mar 3 23:13:22 (none) Activity TvSyncActivity[528]: read 0x04a00000 /lib/libtmk.so Mar 3 23:13:22 (none) Activity TvSyncActivity[528]: read 0x04c00000 /lib/libtvstructures.so Mar 3 23:13:22 (none) Activity TvSyncActivity[528]: read 0x2aaa8000 /lib/ld.so.1 Mar 3 23:13:22 (none) Activity TvSyncActivity[528]: read 0x2ab08000 /platform/lib/libmp3dec.so Mar 3 23:13:22 (none) Activity TvSyncActivity[528]: read 0x2ab58000 /platform/lib/libcdsassetsentinelasf.so Mar 3 23:13:22 (none) Activity TvSyncActivity[528]: read 0x2aba0000 /platform/lib/libmomcds.so Mar 3 23:13:22 (none) Activity TvSyncActivity[528]: read 0x2abe8000 /platform/lib/libmomasf.so Mar 3 23:13:22 (none) Activity TvSyncActivity[528]: read 0x2ac38000 /platform/lib/libhpkhl.so Mar 3 23:13:22 (none) Activity TvSyncActivity[528]: read 0x2ad18000 /lib/libhpkoss.so Mar 3 23:13:22 (none) Activity Mar 3 23:13:22 (none) Activity TvSyncActivity[528]: read 0x2ad68000 /platform/lib/libhpkll.so Mar 3 23:13:22 (none) Activity TvSyncActivity[528]: read 0x2adb0000 /lib/librt.so.1 Mar 3 23:13:22 (none) Activity TvSyncActivity[528]: read 0x2ae08000 /lib/libdl.so.2 Mar 3 23:13:22 (none) Activity TvSyncActivity[528]: 0x04a8979c 0x00694b90 0x00545694 0x0055005c 0x00d30848 0x00d3067c 0x00d4056c 0x00d40da4 0x00d3d6f4 0x00d3bf88 0x00d3bb48 0x00d2cc08 0x00d2b148 0x00d2b0a8 0x00d3ab74 0x00d3aa48 0x00d2e7dc 0x00d2a5c4 0x00d2ab8c 0x04a2d818 0x04a2d448 0x04a2cca0 0x04a2bc20 0x04a3067c 0x04a6956c 0x04a2d818 0x04a3054c 0x04a2e4ac 0x04a3bd2c 0x04a3bc30 0x04a3bae0 0x04a3acb4 Mar 3 23:13:22 (none) Activity TvSyncActivity[528]: Tmk Fatal Error: Activity TvSyncActivity <528>: assertion failure Mar 3 23:13:22 (none) Activity TvSyncActivity[528]: Tmk Fatal Error: Thread died due to signal -2 Mar 3 23:13:22 (none) Activity TvSyncActivity[528]: Invoking rule 834: rebooting system
pZ
Diamond Member
not too much to go on there
'TvSyncActivity' ties in largely with the tivo's xmpp services
disconnect the box from your network and see if it still reboots. additionally, wipe your logs, wait for it to crash, and zip up/attach the important ones (kernel,tvlog,tverr)
if you use tivo.com for remote scheduling, then my money is on a borked schedule request
Junior Member
Thanks for the suggestion, but it still reboots even when disconnected from my home network. I have use tivo.com remote scheduling on my THD, but not on this S3. Collected a fresh set of logs, please see attached.
pZ
Diamond Member
I don't have any real help but DDB doesn't seem to get many posts.
Did you try going back to your original tivoapp file?
Does BILLBOARD id = 589831...refer to a showcase entry? Is it possible the reboot cycle started after your showcases were updated.
Senior Member
Sorry to resurrect an old thread like this but it contains information that's identical to my situation.
I am getting reboots every 20 to 30 minutes but this problem has existed over several reinstalls all trying different things to solve the problem. One thing consistent about my problem is I get this same message just before each failure.
I find I can set my Tivo to use phone instead of network then tell it to dial 7 instead of 10 digits and the reboots go away. As soon as I let it connect normally either via phone or TCP I get reboots. I can force it to connect and that works just fine. It will download stuff and I can watch it organize the downloaded data until it's done. That is if it doesn't take longer than 20 or 30 minutes to organize the download.Code:Tmk Fatal Error: Activity TvSyncActivity <547> strayed!
The error the OP posted above is associated with "'TvSyncActivity' ties in largely with the tivo's xmpp services". Following the above link I learned that is how Tivo get season passes etc... scheduled from their website. I just noticed something odd, every time I either clear and delete everything or if I put a fresh install into action I consistently get 4 messages regarding season passes I tried to set up via the internet ages ago. One for example says "My online request for season Pass Gangland has been received. That message dates back to when I first got this Tivo and was trying to move my season passes from my old S2DT to this TivoHD via Tivo.com. When that failed I tried manually setting up each pass using their site but their site sucks so I gave up.
The fact that I consistently get these same 4 messages every time I either do a fresh install or clear and delete everything tells me they are probably stuck in my queue somehow and may be part of what's causing my reboots later down the road (two weeks or so). The recent episode started on 11/26 which coincidently is when I went from monthly service plan and the $99 lifetime kicked in.
Question... How can I clear those messages from my queue? I can delete them from the Tivo and they don't come back that I remember but they must be stuck on Tivo's servers since I get them consistently with each fresh install. I looked all over tivo.com and don't see anything that will clear the queue which means I may have to call Tivo. Anyone know what I should say so this doesn't get blamed on my hacking the Tivo but will be enough information for them to find the problem?
I figure I can tell them I pulled the drive and saw the error in the logs then googling I found information on what the error MIGHT be. Instead of mentioning fresh installs I can tell them I am going back to my stock drive and clearing and deleting everything and noticed I consistently get these 4 messages. Anything I should avoid saying on this call?
Last edited by Soapm; 11-29-2011 at 02:42 PM.
Junior Member
Sorry to hear you're having the same problem. I never was able to correct it, I had to revert back to my original drive, which has been working fine ever since (knock-on-wood).
pZ
Senior Member
Isn't that strange, I believe it only does this with my 2TB drive. I don't recall it happening with the stock drive now that you mention it. Maybe I'll take the 1TB drive out of my S2DT and call it a day...Originally Posted by phoenixZed
Senior Member
I'm still having the reboot problem every 20 to 30 minutes with my 2TB drive. Tivo runs fine on my 1TB drive and the stock 160GB drive. I would like to try one of two things and was hoping someone could point me to guided information;Code:Partition Maps #: type name length base ( size ) 1 Apple_partition_map Apple 63@1 ( 31.5K) 2 Image Bootstrap 1 1@309549120 ( 512.0 ) 3 Image Kernel 1 8192@309549121 ( 4.0M) 4 Ext2 Root 1 524288@309557313 ( 256.0M) 5 Image Bootstrap 2 1@310081601 ( 512.0 ) 6 Image Kernel 2 8192@310081602 ( 4.0M) 7 Ext2 Root 2 524288@310089794 ( 256.0M) 8 Swap Linux swap 262144@310614082 ( 128.0M) 9 Ext2 /var 524288@310876226 ( 256.0M) 10 MFS MFS application region 589824@311400514 ( 288.0M) 11 MFS MFS media region 137629696@171919424 ( 65.6G) 12 MFS MFS application region 2 589824@311990338 ( 288.0M) 13 MFS MFS media region 2 171919360@64 ( 82.0G) 14 Apple_Free Extra 1645@312580162 ( 822.5K) 15 MFS MFS media region 3 3594447361@312581807 ( 1.7T)
I would like to break partition 15 into two 850GB partitions to see if that is more likable to my Tivo.
Or, I would like to increase the size of partitions 11 and 13 by about 800GB to see if that smooths things out.
How doable is this and can someone point me to tools or step by step instructions that might assist?
Diamond Member
Unfortunately, no one who is talking knows enough about the MFS file system to be able to manage the MFS partitions with that sort of control, an none of the available tools allow that sort of granularity. Jamie has a lot more experience working with variable partition sizes, so he may be able to chime in, here. What I think may be possible is to create a truncated backup using Win_MFS or MFS-Live and then restore to a blank drive. I don't know if jmfs can offer any help, or not. DVR_Dude over on e-bay can probably work some magic, but he's going to charge for it.
Last edited by lrhorer; 12-03-2011 at 05:53 AM.
Having trouble with TyTool? Try TyTool Documentation
Need to hack an S3 / THD? Try S3 Hacking Script
Diamond Member
The "Apple_Free Extra" partition is normally the last partition on the disk and is a holding space for any unpartitioned space on the disk. Seems odd to have that as partition 14, with an active partition 15 after it. Is partition 14 part of the mfs device map? If so, that's likely to cause a problem. Normally I'd expect MFS partitions to come in pars, e.g. 10-11, 12-13, and 14-15. Is 14 actually an MFS partition and just mislabeled? By what process did you wind up with such a strange partition table? I'd question whether the tools actually did the right thing in expanding your MFS onto a 2TB disk. Might be best to start over from scratch with a known good image.
Senior Member
What command would I use to confirm this?I used Comer's jfms. I simply copied from the stock 160gb drive then expanded using jfms. One previous attempt I used WinMFS which I believe gave me a similar partition table. If I can find that file I will post it when I get on my windows machine.
PS... I have a stock image and don't mind starting from scratch but this is about the 4th or 5th time I followed this process and the results never change. I start getting these reboots every 20 to 30 minutes whenever the drive starts to fill.
PS. PS...I guess I was wrong, WinMFS did put the apple partition at the end of the drive but it also didn't use all the available space.
Code:Partition Maps #: type name length base ( size ) 1 Apple_partition_map Apple 63@1 ( 31.5K) 2 Image Bootstrap 1 1@309549120 ( 512.0 ) 3 Image Kernel 1 8192@309549121 ( 4.0M) 4 Ext2 Root 1 524288@309557313 ( 256.0M) 5 Image Bootstrap 2 1@310081601 ( 512.0 ) 6 Image Kernel 2 8192@310081602 ( 4.0M) 7 Ext2 Root 2 524288@310089794 ( 256.0M) 8 Swap Linux swap 262144@310614082 ( 128.0M) 9 Ext2 /var 524288@310876226 ( 256.0M) 10 MFS MFS application region 589824@311400514 ( 288.0M) 11 MFS MFS media region 137629696@171919424 ( 65.6G) 12 MFS MFS application region 2 589824@311990338 ( 288.0M) 13 MFS MFS media region 2 171919360@64 ( 82.0G) 14 MFS MFS App by Winmfs 2048@312580162 ( 1.0M) 15 MFS MFS Media by Winmfs 1640673280@312582210 ( 782.3G) 16 Apple_Free Extra 1953773677@1953255490( 931.6G)
Last edited by Soapm; 12-04-2011 at 04:31 AM.
Diamond Member
Dump the MFS superblock:You can see the device map at offset 0x24 in the dump (see /dev/hda10 ... if you look in the ascii formated output on the right.)Code:bash-2.02# hexdump -C -n 256 /dev/hda10 00000000 00 00 00 00 eb ba fe ed d0 d4 94 e2 00 00 00 10 |................| 00000010 00 00 00 01 00 00 00 40 00 00 02 40 00 00 00 01 |.......@...@....| 00000020 00 00 00 01 2f 64 65 76 2f 68 64 61 31 30 20 2f |..../dev/hda10 /| 00000030 64 65 76 2f 68 64 61 31 31 20 2f 64 65 76 2f 68 |dev/hda11 /dev/h| 00000040 64 61 31 32 20 2f 64 65 76 2f 68 64 61 31 33 00 |da12 /dev/hda13.| 00000050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 000000a0 00 00 00 00 00 00 00 00 00 00 00 00 e8 c6 40 00 |..............@.| 000000b0 00 00 00 00 00 00 00 01 00 00 00 00 00 4f 9f 27 |.............O.'| 000000c0 00 00 00 00 00 00 03 e9 00 00 00 00 00 00 00 00 |................| 000000d0 00 00 00 00 00 00 04 61 00 00 00 00 00 08 ff fe |.......a........| 000000e0 00 00 00 00 00 00 00 01 00 00 00 00 00 04 00 00 |................| 000000f0 00 00 00 00 00 04 00 00 00 00 00 78 00 00 03 e8 |...........x....| 00000100
Senior Member
I didn't know how to dump the superblock but I did find this entry in my kernel logs during startups.
hda: [mac] hda1 hda2 hda3 hda4 hda5 hda6 hda7 hda8 hda9 hda10 hda11 hda12 hda13 hda14 hda15
If I'm following your implications then this explains why WinMFS was a miserable failure in this case but it doesn't explain my current situation since hda15 is there.
I hate being defeated so I decided to wipe this drive and give it one more try. This time I hacked it manually with no scripts and I seem to have gotten everything working so far. I guess we'll see in a few weeks when te drive begins to fill if this was a waste of time or not.
Diamond Member
I listed the necessary hexdump command to dump the superblock: hexdump -C -n 256 /dev/hda10.
What you found in the kernel log does not tell us what is in the MFS superblock. The kernel knows nothing about MFS.
Starting over is not a bad idea. Does the new partition map seem more reasonable, or is there still an "Apple_Free Extra" partition in slot 14?
Senior Member
Still on 14... Here is the new partition map...
Superblock hex dump... I notice 14 isn't listed.Code:Partition map (with 512 byte blocks) on '/dev/hda' #: type name length base ( size ) 1: Apple_partition_map Apple 63 @ 1 ( 31.5K) 2: Image Bootstrap 1 1 @ 309549120 3: Image Kernel 1 8192 @ 309549121 ( 4.0M) 4: Ext2 Root 1 524288 @ 309557313 ( 256.0M) 5: Image Bootstrap 2 1 @ 310081601 6: Image Kernel 2 8192 @ 310081602 ( 4.0M) 7: Ext2 Root 2 524288 @ 310089794 ( 256.0M) 8: Swap Linux swap 262144 @ 310614082 ( 128.0M) 9: Ext2 /var 524288 @ 310876226 ( 256.0M) 10: MFS MFS application region 589824 @ 311400514 ( 288.0M) 11: MFS MFS media region 137629696 @ 171919424 ( 65.6G) 12: MFS MFS application region 2 589824 @ 311990338 ( 288.0M) 13: MFS MFS media region 2 171919360 @ 64 ( 81.9G) 14: Apple_Free Extra 1645 @ 312580162 ( 822.5K) 15: MFS MFS media region 3 3594447361 @ 312581807 ( 1.6T)
Code:FamRoom# hexdump -C -n 256 /dev/hda10 00000000 00 00 00 00 eb ba fe ed 8c 8a c0 02 00 00 00 10 |................| 00000010 00 00 00 01 00 00 00 40 00 00 02 40 00 00 00 01 |.......@...@....| 00000020 00 00 00 01 2f 64 65 76 2f 68 64 61 31 30 20 2f |..../dev/hda10 /| 00000030 64 65 76 2f 68 64 61 31 31 20 2f 64 65 76 2f 68 |dev/hda11 /dev/h| 00000040 64 61 31 32 20 2f 64 65 76 2f 68 64 61 31 33 20 |da12 /dev/hda13 | 00000050 2f 64 65 76 2f 68 64 61 31 35 00 00 00 00 00 00 |/dev/hda15......| 00000060 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 000000a0 00 00 00 00 00 00 00 00 00 00 00 00 e8 c4 40 00 |..............@.| 000000b0 00 00 00 00 00 00 00 01 00 00 00 00 00 03 36 6b |..............6k| 000000c0 00 00 00 00 00 00 03 e9 00 00 00 00 00 00 00 00 |................| 000000d0 00 00 00 00 00 00 04 61 00 00 00 00 00 08 ff fe |.......a........| 000000e0 00 00 00 00 00 00 00 01 00 00 00 00 00 04 00 00 |................| 000000f0 00 00 00 00 00 04 00 00 00 00 00 78 00 00 03 e8 |...........x....| 00000100
Posting Permissions
Reply With Quote