Discussion:
How can I mount the disk from a Serries 2 on a Linux X86 machine?
(too old to reply)
Stan Brown
2003-11-19 17:42:59 UTC
Permalink
I'm still beating my (quite bloddy) head against trying to resurecte my
Tivo.

Can anyone point me to instrunctions as to how to mount the partitions of
the disk I have removed from my Serries 2 box under Linux X86?
--
"They that would give up essential liberty for temporary safety deserve
neither liberty nor safety."
-- Benjamin Franklin
Ted
2003-11-19 19:10:29 UTC
Permalink
Put the disk in your PC, and use the mount command

ex.

mkdir tivo
mount /dev/hda9 /tivo
Post by Stan Brown
I'm still beating my (quite bloddy) head against trying to resurecte my
Tivo.
Can anyone point me to instrunctions as to how to mount the partitions of
the disk I have removed from my Serries 2 box under Linux X86?
--
"They that would give up essential liberty for temporary safety deserve
neither liberty nor safety."
-- Benjamin Franklin
Stan Brown
2003-11-19 19:59:46 UTC
Permalink
Post by Ted
Put the disk in your PC, and use the mount command
ex.
mkdir tivo
mount /dev/hda9 /tivo
OK, ask a stupid question ....

Lets try this again. Given that cfdisk cannot read the partition table of
the Tivo drive, how do I figure out what partitions are what? And is there
a way to access the MFS partions from a X86 Linux system?

More sensible questions?
--
"They that would give up essential liberty for temporary safety deserve
neither liberty nor safety."
-- Benjamin Franklin
Wes Newell
2003-11-19 19:15:58 UTC
Permalink
Post by Stan Brown
I'm still beating my (quite bloddy) head against trying to resurecte my
Tivo.
Can anyone point me to instrunctions as to how to mount the partitions of
the disk I have removed from my Serries 2 box under Linux X86?
Install the hd. For this I'll assume it's the slave of the primary disk
controller. It's device name is hdb.
First you need to verify the disk. Easily done with fdisk, sfdisk, or any
of the other fdisk type programs. Type "man fdisk" for full explaination
of fdisk. Here's an example of using fdisk to identify the drive and
partitions.
[***@wes2 wes]# fdisk -l /dev/hde

Disk /dev/hde: 60.0 GB, 60022480896 bytes
255 heads, 63 sectors/track, 7297 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hde1 1 1 8001 a OS/2 Boot Manager
/dev/hde2 2 393 3148740 b Win95 FAT32
/dev/hde4 394 7297 55456380 5 Extended
/dev/hde5 * 394 916 4200966 7 HPFS/NTFS
/dev/hde6 * 917 1001 682731 83 Linux
/dev/hde7 * 1002 1051 401593+ 82 Linux swap
/dev/hde8 * 1052 2369 10586803+ 83 Linux
/dev/hde9 * 2370 3318 7622811 83 Linux
/dev/hde10 * 3319 6022 21719848+ 83 Linux
/dev/hde11 * 6023 7297 10241406 7 HPFS/NTFS
[***@wes2 wes]#

Once you have this output, you know your drive is there and visible. Next,
you need a place to mount the partition(s). Create a mount point somewhere
for each partiton you want to mount, then mount the partiton to the mount
point. Type man mount for mount instructions. This operation could look
something like this for the partition. I'm going to mount hde2 since it a
valid partiton on my drive. It's already moounted in /mnt/windows, but you
can mount it in more than one place.
[***@wes2 mnt]# cd /
[***@wes2 /]# cd /mnt
[***@wes2 mnt]# mkdir hdb2
[***@wes2 mnt]# mount /dev/hde2 /mnt/hdb2
[***@wes2 mnt]# cd hdb2
[***@wes2 hdb2]# ls
asd.log* config.bak* KH0N.exe* nvidia/ tmp/
autoexec.bak* config.dos* lcr/ Program Files/ VIAhm/
autoexec.bat* config.sys* loan.exe* recycled/ windows.000/
autoexec.dos* detlog.txt* LtnFlash.exe* sat/ WINDOWS~000/
bootlog.prv* dos/ msdos.---* scandisk.log* wp root. sf*
bootlog.txt* drvspace.bin* msdos.sys* setupxlg.txt*
cldma.log* ea data. sf* My Documents/ suhdlog.---*
CO48KH0N.zip* frunlog.txt* My Music/ suhdlog.dat*
command.com* io.sys* netlog.txt* system.1st*
[***@wes2 hdb2]#

That's all folks. Be sure you umount it when done. umount /mnt/hdb2 in
this case. And you can't be in the dir when you unmount it.
--
Abit KT7-Raid (KT133) Tbred B core CPU @2400MHz (24x100FSB)
http://mysite.verizon.net/res0exft/cpu.html
Stan Brown
2003-11-19 20:12:40 UTC
Permalink
Post by Wes Newell
Post by Stan Brown
I'm still beating my (quite bloddy) head against trying to resurecte my
Tivo.
Can anyone point me to instrunctions as to how to mount the partitions of
the disk I have removed from my Serries 2 box under Linux X86?
Install the hd. For this I'll assume it's the slave of the primary disk
controller. It's device name is hdb.
First you need to verify the disk. Easily done with fdisk, sfdisk, or any
of the other fdisk type programs. Type "man fdisk" for full explaination
of fdisk. Here's an example of using fdisk to identify the drive and
partitions.
Ah, that sounds like what I was expecting. However, my recolection is that
fdisk does not like the partiton table on the disks I am using.

It's _possible_ that this is part of my problme. I'm trying to restore from
a downloaded image, as my backup appears to not give me a working disk.

I've been able to get the Tivo to boot from disks (note multiple) restiree
from the downlaoded image, but it does not work corectly all the time.

So, I will check this tonght when I get home.

These are new disks, do I need to do anything to prepare them for use by
tivo before I restore the image?
--
"They that would give up essential liberty for temporary safety deserve
neither liberty nor safety."
-- Benjamin Franklin
Wes Newell
2003-11-19 23:04:32 UTC
Permalink
Post by Stan Brown
These are new disks, do I need to do anything to prepare them for use by
tivo before I restore the image?
Everything you need should be here.

http://www.newreleasesvideo.com/hinsdale-how-to/index9.html
--
Abit KT7-Raid (KT133) Tbred B core CPU @2400MHz (24x100FSB)
http://mysite.verizon.net/res0exft/cpu.html
Stan Brown
2003-11-20 00:30:53 UTC
Permalink
Post by Wes Newell
Post by Stan Brown
These are new disks, do I need to do anything to prepare them for use by
tivo before I restore the image?
Everything you need should be here.
http://www.newreleasesvideo.com/hinsdale-how-to/index9.html
I must have read that doc 20 times now, and I still cant get this to work
:-(

My current theory on what is wrong (and I've had many!) is that I don't
have a valid parition table on my drivess. Is the mfstools restore supposed
to create a partition table? (used by fdisk and others).
--
"They that would give up essential liberty for temporary safety deserve
neither liberty nor safety."
-- Benjamin Franklin
Wes Newell
2003-11-20 08:08:50 UTC
Permalink
Post by Stan Brown
Post by Wes Newell
Post by Stan Brown
These are new disks, do I need to do anything to prepare them for use
by tivo before I restore the image?
Everything you need should be here.
http://www.newreleasesvideo.com/hinsdale-how-to/index9.html
I must have read that doc 20 times now, and I still cant get this to
work :-(
Then buy a preconfigured drive. I think they sell them.
--
Abit KT7-Raid (KT133) Tbred B core CPU @2400MHz (24x100FSB)
http://mysite.verizon.net/res0exft/cpu.html
Stan Brown
2003-11-20 12:01:40 UTC
Permalink
Post by Wes Newell
Post by Stan Brown
Post by Wes Newell
Post by Stan Brown
These are new disks, do I need to do anything to prepare them for use
by tivo before I restore the image?
Everything you need should be here.
http://www.newreleasesvideo.com/hinsdale-how-to/index9.html
I must have read that doc 20 times now, and I still cant get this to
work :-(
Then buy a preconfigured drive. I think they sell them.
First of all they are rway too expensive. Secind, a large part of my
frustration is based upon lack of understnading.

If all you can contribute to the discussion is RTFM, then I would ssuspect
you are clueless, and just giving caned advice.

If not, then I challenge you to contribute )one_ usefull post to the
discussion!
--
"They that would give up essential liberty for temporary safety deserve
neither liberty nor safety."
-- Benjamin Franklin
Wes Newell
2003-11-20 17:13:57 UTC
Permalink
Post by Stan Brown
Post by Wes Newell
Post by Stan Brown
Post by Wes Newell
Post by Stan Brown
These are new disks, do I need to do anything to prepare them for
use by tivo before I restore the image?
Everything you need should be here.
http://www.newreleasesvideo.com/hinsdale-how-to/index9.html
I must have read that doc 20 times now, and I still cant get this to
work :-(
Then buy a preconfigured drive. I think they sell them.
First of all they are rway too expensive. Secind, a large part of my
frustration is based upon lack of understnading.
If all you can contribute to the discussion is RTFM, then I would
ssuspect you are clueless, and just giving caned advice.
If not, then I challenge you to contribute )one_ usefull post to the
discussion!
I've already posted in complete detail, with examples, how to fdisk and
mount your drive using Linux. Iow's, I completely did it on my system and
pasted the exact proceedure here. You say you have new drives, so you
don't need to do anything to them prior to using the Hindsdale guide to
get them to work. I know you're frustrated at this point, but not being
there I can't do it for you, and since you can't seem to do it, a
suggestion of buying a preconfigured drive seemed to me like the best
alternative. I'm outta here. Good luck.
--
Abit KT7-Raid (KT133) Tbred B core CPU @2400MHz (24x100FSB)
http://mysite.verizon.net/res0exft/cpu.html
Stan Brown
2003-11-20 21:07:50 UTC
Permalink
Post by Wes Newell
Post by Stan Brown
Post by Wes Newell
Post by Stan Brown
Post by Wes Newell
Post by Stan Brown
These are new disks, do I need to do anything to prepare them for
use by tivo before I restore the image?
Everything you need should be here.
http://www.newreleasesvideo.com/hinsdale-how-to/index9.html
I must have read that doc 20 times now, and I still cant get this to
work :-(
Then buy a preconfigured drive. I think they sell them.
First of all they are rway too expensive. Secind, a large part of my
frustration is based upon lack of understnading.
If all you can contribute to the discussion is RTFM, then I would
ssuspect you are clueless, and just giving caned advice.
If not, then I challenge you to contribute )one_ usefull post to the
discussion!
I've already posted in complete detail, with examples, how to fdisk and
mount your drive using Linux. Iow's, I completely did it on my system and
pasted the exact proceedure here. You say you have new drives, so you
don't need to do anything to them prior to using the Hindsdale guide to
get them to work. I know you're frustrated at this point, but not being
there I can't do it for you, and since you can't seem to do it, a
suggestion of buying a preconfigured drive seemed to me like the best
alternative. I'm outta here. Good luck.
Sorry, I apolgize for letting my frustration show :-(

Do I need to do the fdisk manualyy, before I do the mfstools restore? If so
that's what I'm not doing.

It could be that simple.. (Wouldn't that be nice!).

Thanks for your help.
--
"They that would give up essential liberty for temporary safety deserve
neither liberty nor safety."
-- Benjamin Franklin
Wes Newell
2003-11-21 06:48:10 UTC
Permalink
Post by Stan Brown
Do I need to do the fdisk manualyy, before I do the mfstools restore? If
so that's what I'm not doing.
IIRC, all I did was to backup the old drive image, run something on it to
expand it, and then restore it to the new drive following the Hindsdale
guide. It's writing an image to the new HD, so it would write over any
partition table that was there anyway afaik. If you've already created
partions on the new drive, remove them with fdisk and then restore the
image to it. Double check guide. You may need to expand the image. It's
been close to 2 years since I upgraded mine. I went back in with just one
120 gig drive, and gave the old slowass 20gig tivo drive away.
--
Abit KT7-Raid (KT133) Tbred B core CPU @2400MHz (24x100FSB)
http://mysite.verizon.net/res0exft/cpu.html
Stan Brown
2003-11-20 00:27:57 UTC
Permalink
Post by Wes Newell
Post by Stan Brown
I'm still beating my (quite bloddy) head against trying to resurecte my
Tivo.
Can anyone point me to instrunctions as to how to mount the partitions of
the disk I have removed from my Serries 2 box under Linux X86?
OK, now I'm really coonfused :-(
Post by Wes Newell
Install the hd. For this I'll assume it's the slave of the primary disk
controller. It's device name is hdb.
First you need to verify the disk. Easily done with fdisk, sfdisk, or any
of the other fdisk type programs. Type "man fdisk" for full explaination
of fdisk. Here's an example of using fdisk to identify the drive and
partitions.
Here's what I get when I do that:

smokey:~# fdisk -l /dev/hdb

Disk /dev/hdb: 60.0 GB, 60022480896 bytes
255 heads, 63 sectors/track, 7297 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/hdb doesn't contain a valid partition table

I'm able to duplicate this same error in my normal Debian runtime, and
booted from the CD that comes with teh "Hacking Tivo" Book.

I tried restoring again using:

mfstools restore -xzpi <backup_name>

This appears to go OK. I did this using my backup, and 2 different backups
downloaded from tivostuff. The results are identical in all cases. If I run
mfstools info I get:

MFS volume set for /dev/hdb
The MFS volume set contains 4 partitions
/dev/hdb10
MFS Partition Size: 256MiB
/dev/hdb11
MFS Partition Size: 24790MiB
/dev/hdb12
MFS Partition Size: 256MiB
/dev/hdb13
MFS Partition Size: 31483MiB
Total MFS volume size: 56785MiB
Estimated hours in a standalone TiVo: 57
This MFS volume may be expanded 4 more times

But fdisk -l is still unhappy.

Booted from the CD, I tried mls on these 3 partitons, and just go errors.

Do I need to create a partiton table first? If so, howw do I do it.

If not what stupid mistake am I making.

You will have to forgive my tone, I've been fighting this for about 2 weeks
now, and I'm running out of patienance.
Post by Wes Newell
Disk /dev/hde: 60.0 GB, 60022480896 bytes
255 heads, 63 sectors/track, 7297 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hde1 1 1 8001 a OS/2 Boot Manager
/dev/hde2 2 393 3148740 b Win95 FAT32
/dev/hde4 394 7297 55456380 5 Extended
/dev/hde5 * 394 916 4200966 7 HPFS/NTFS
/dev/hde6 * 917 1001 682731 83 Linux
/dev/hde7 * 1002 1051 401593+ 82 Linux swap
/dev/hde8 * 1052 2369 10586803+ 83 Linux
/dev/hde9 * 2370 3318 7622811 83 Linux
/dev/hde10 * 3319 6022 21719848+ 83 Linux
/dev/hde11 * 6023 7297 10241406 7 HPFS/NTFS
BTW, I've tried this with 2 different hard drives, the original one that
came witht eh Tivo, and a 120G Maxtor. Same result :-(

I must be making some stupid mistake!
--
"They that would give up essential liberty for temporary safety deserve
neither liberty nor safety."
-- Benjamin Franklin
Ted
2003-11-20 16:31:48 UTC
Permalink
Does it show the correct partition tables while booting to linux (perhaps
using the mfstools cd?)...

Go off that..
Post by Stan Brown
Post by Wes Newell
Post by Stan Brown
I'm still beating my (quite bloddy) head against trying to resurecte my
Tivo.
Can anyone point me to instrunctions as to how to mount the partitions of
the disk I have removed from my Serries 2 box under Linux X86?
OK, now I'm really coonfused :-(
Post by Wes Newell
Install the hd. For this I'll assume it's the slave of the primary disk
controller. It's device name is hdb.
First you need to verify the disk. Easily done with fdisk, sfdisk, or any
of the other fdisk type programs. Type "man fdisk" for full explaination
of fdisk. Here's an example of using fdisk to identify the drive and
partitions.
smokey:~# fdisk -l /dev/hdb
Disk /dev/hdb: 60.0 GB, 60022480896 bytes
255 heads, 63 sectors/track, 7297 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk /dev/hdb doesn't contain a valid partition table
I'm able to duplicate this same error in my normal Debian runtime, and
booted from the CD that comes with teh "Hacking Tivo" Book.
mfstools restore -xzpi <backup_name>
This appears to go OK. I did this using my backup, and 2 different backups
downloaded from tivostuff. The results are identical in all cases. If I run
MFS volume set for /dev/hdb
The MFS volume set contains 4 partitions
/dev/hdb10
MFS Partition Size: 256MiB
/dev/hdb11
MFS Partition Size: 24790MiB
/dev/hdb12
MFS Partition Size: 256MiB
/dev/hdb13
MFS Partition Size: 31483MiB
Total MFS volume size: 56785MiB
Estimated hours in a standalone TiVo: 57
This MFS volume may be expanded 4 more times
But fdisk -l is still unhappy.
Booted from the CD, I tried mls on these 3 partitons, and just go errors.
Do I need to create a partiton table first? If so, howw do I do it.
If not what stupid mistake am I making.
You will have to forgive my tone, I've been fighting this for about 2 weeks
now, and I'm running out of patienance.
Post by Wes Newell
Disk /dev/hde: 60.0 GB, 60022480896 bytes
255 heads, 63 sectors/track, 7297 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hde1 1 1 8001 a OS/2 Boot Manager
/dev/hde2 2 393 3148740 b Win95 FAT32
/dev/hde4 394 7297 55456380 5 Extended
/dev/hde5 * 394 916 4200966 7 HPFS/NTFS
/dev/hde6 * 917 1001 682731 83 Linux
/dev/hde7 * 1002 1051 401593+ 82 Linux swap
/dev/hde8 * 1052 2369 10586803+ 83 Linux
/dev/hde9 * 2370 3318 7622811 83 Linux
/dev/hde10 * 3319 6022 21719848+ 83 Linux
/dev/hde11 * 6023 7297 10241406 7 HPFS/NTFS
BTW, I've tried this with 2 different hard drives, the original one that
came witht eh Tivo, and a 120G Maxtor. Same result :-(
I must be making some stupid mistake!
--
"They that would give up essential liberty for temporary safety deserve
neither liberty nor safety."
-- Benjamin Franklin
Stan Brown
2003-11-20 20:56:15 UTC
Permalink
Post by Ted
Does it show the correct partition tables while booting to linux (perhaps
using the mfstools cd?)...
No. fdisk -l reports an invalid parition table bothe before, and after
doing an mfstools restore, both booted intot my normal Debina system, and
booted from the CD included with "Hacking Tivo".

This is not right, is it?

Is there a step I'm missing to create the partion table? One of the drives
I ahve tried is a new one, and one is the oringal Tivo drive. Same results
with both.. I think I even created a parition table (single partion as I
recall) by hand using cfdisk, before one of the atempted restore.

I'm curently thinking this is at least some of my problem. Am I on the
right track here?
--
"They that would give up essential liberty for temporary safety deserve
neither liberty nor safety."
-- Benjamin Franklin
Ted
2003-11-20 21:16:04 UTC
Permalink
Post by Stan Brown
Post by Ted
Does it show the correct partition tables while booting to linux (perhaps
using the mfstools cd?)...
No. fdisk -l reports an invalid parition table bothe before, and after
doing an mfstools restore, both booted intot my normal Debina system, and
booted from the CD included with "Hacking Tivo".
Did I ask does it show the right partition when you do fdisk -l ? Nope...
Maybe you could post what it says while booting the mfstools CD? It will be
long... but I guess thats what will need to be done to show you the drives
with the paritions.
Post by Stan Brown
This is not right, is it?
Is there a step I'm missing to create the partion table? One of the drives
I ahve tried is a new one, and one is the oringal Tivo drive. Same results
with both.. I think I even created a parition table (single partion as I
recall) by hand using cfdisk, before one of the atempted restore.
I'm curently thinking this is at least some of my problem. Am I on the
right track here?
--
"They that would give up essential liberty for temporary safety deserve
neither liberty nor safety."
-- Benjamin Franklin
Bob Nielsen
2003-11-20 21:56:02 UTC
Permalink
Post by Ted
Post by Stan Brown
Post by Ted
Does it show the correct partition tables while booting to linux (perhaps
using the mfstools cd?)...
No. fdisk -l reports an invalid parition table bothe before, and after
doing an mfstools restore, both booted intot my normal Debina system, and
booted from the CD included with "Hacking Tivo".
Did I ask does it show the right partition when you do fdisk -l ? Nope...
Maybe you could post what it says while booting the mfstools CD? It will be
long... but I guess thats what will need to be done to show you the drives
with the paritions.
In mfstools.2/readme of the mfstools CD, it says:

"Unlike past MFS utilities released by others, the MFS Tools package
does not require a special kernel or boot parameters. In fact, it is
quicker without byte-swapping. The MFS Tools themself recognize both
swapped bytes and the TiVo partition format."

Since the mfstools kernel does not recognize a MFS partition, it cannot
be mounted in a Linux system running that kernel, nor will fdisk
correctly report the partition table. IF you had a kernel with MFS
support and a version of fdisk which recognized MFS, it would be a
different story.

The above quote implies that such kernels exist, but I don't know where
one could obtain a copy (or the necessary patches to compile your own).
If one had a copy of "past MFS utilities", merely copying the vmlinuz
file to a Linux system would probably not be sufficient, rather one
would need to have the kernel source and compile it with the same (or
compatible) libraries as exist on that system.
Stan Brown
2003-11-20 22:57:22 UTC
Permalink
Post by Ted
Post by Stan Brown
Post by Ted
Does it show the correct partition tables while booting to linux (perhaps
using the mfstools cd?)...
No. fdisk -l reports an invalid parition table bothe before, and after
doing an mfstools restore, both booted intot my normal Debina system, and
booted from the CD included with "Hacking Tivo".
Did I ask does it show the right partition when you do fdisk -l ? Nope...
Maybe you could post what it says while booting the mfstools CD? It will be
long... but I guess thats what will need to be done to show you the drives
with the paritions.
-- sniped for brvity.

OK, I understnad. So, Goes this mean that I can't mount the Linux paritions
at all?
--
"They that would give up essential liberty for temporary safety deserve
neither liberty nor safety."
-- Benjamin Franklin
Joe Smith
2003-11-21 02:41:06 UTC
Permalink
Post by Stan Brown
OK, I understnad. So, Goes this mean that I can't mount the Linux paritions
at all?
When I did my upgrade, the destination disk had no partition map at all
and I did nothing explict to create one. I simply ran mfsrestore, and
it copied the partition map that was inside the backup file over to
the new disk. (Somewhat like using 'dd' to write a valid partition map
onto the raw disk.) No fdisk required.

Since you are not seeing a valid partition map after running mfsrestore,
it could be that the backup file has errors.

As to kernels with MFS support, I've used both the mfstools boot floppy
and the boot CD-ROM from Silicon Dust.
http://www.silicondust.com/terms_of_use.html
(Haven't tried the CD-ROM from Jeff Keegan's book yet.)
-Joe
Stan Brown
2003-11-21 12:00:03 UTC
Permalink
Post by Joe Smith
Post by Stan Brown
OK, I understnad. So, Goes this mean that I can't mount the Linux paritions
at all?
When I did my upgrade, the destination disk had no partition map at all
and I did nothing explict to create one. I simply ran mfsrestore, and
it copied the partition map that was inside the backup file over to
the new disk. (Somewhat like using 'dd' to write a valid partition map
onto the raw disk.) No fdisk required.
So, are you saying that you had a valid partition table _after_ running
mfsrestore,? By valid, I mean readable by an X86 Linux box (perhaps
booted from the mfstools CD)?

I've tries 3 diferent backups, my original one, the 4.0 60 hour one from
tivostuff, and the 3.2 60 hour one from tivostuff.

BTW if I try to use the (comonly recomended) -s 127 option to mfsrestore, I
get a warning about the disk not being large enough, when I use the
otiginal Tivo disk.
Post by Joe Smith
Since you are not seeing a valid partition map after running mfsrestore,
it could be that the backup file has errors.
As to kernels with MFS support, I've used both the mfstools boot floppy
and the boot CD-ROM from Silicon Dust.
http://www.silicondust.com/terms_of_use.html
(Haven't tried the CD-ROM from Jeff Keegan's book yet.)
-Joe
Thnaks.

Any idea what I should try next?
--
"They that would give up essential liberty for temporary safety deserve
neither liberty nor safety."
-- Benjamin Franklin
Joe Smith
2003-11-23 21:47:10 UTC
Permalink
Post by Stan Brown
Post by Joe Smith
When I did my upgrade, the destination disk had no partition map at all
and I did nothing explict to create one. I simply ran mfsrestore, and
it copied the partition map that was inside the backup file over to
the new disk. (Somewhat like using 'dd' to write a valid partition map
onto the raw disk.) No fdisk required.
So, are you saying that you had a valid partition table _after_ running
mfsrestore,? By valid, I mean readable by an X86 Linux box (perhaps
booted from the mfstools CD)?
Yes. Before running mfsrestore: compeletely blank disk.
After running mfsrestore: disk with partition map and data.

Note that "mfstool mfsrestore" has many command-line options for
setting up the partition map, as shown on page 99 of the book.
In particular, -s, -p and -v.

I noticed a couple of things in Jeff Keegan's book.
1) The default boot is for series1, you need to explictly request
"series2" for HDVR2. (Page 106)
2) The examples of using restore (page 90) all use "-b" for series2.
3) The examples of listing the disk partitions use pdisk not fdisk.
Post by Stan Brown
I've tries 3 diferent backups, my original one, the 4.0 60 hour one from
tivostuff, and the 3.2 60 hour one from tivostuff.
BTW if I try to use the (comonly recomended) -s 127 option to mfsrestore, I
get a warning about the disk not being large enough, when I use the
otiginal Tivo disk.
In that case I would give up on using the original disk as the "A"
drive. Put a bigger driver in as "A" and make the original be "B".

-Joe

Stan Brown
2003-11-23 17:24:13 UTC
Permalink
Post by Stan Brown
Post by Ted
Post by Stan Brown
Post by Ted
Does it show the correct partition tables while booting to linux (perhaps
using the mfstools cd?)...
No. fdisk -l reports an invalid parition table bothe before, and after
doing an mfstools restore, both booted intot my normal Debina system, and
booted from the CD included with "Hacking Tivo".
Did I ask does it show the right partition when you do fdisk -l ? Nope...
Maybe you could post what it says while booting the mfstools CD? It will be
long... but I guess thats what will need to be done to show you the drives
with the paritions.
-- sniped for brvity.
OK, I understnad. So, Goes this mean that I can't mount the Linux paritions
at all?
I don't _think_ I ever quite got an answer to this.

The reason I wan't to do this, is to try to find some log files, once
I've run the machine for a while to helpo diagnose my problem.

This has been going on so long (weeks) that we have drifted away
from the original problem.

Let me re-state it for clarity.

I'e been able to create a disk (actually 2 different physical disks)
that will boot the Tivo. However, the unit does not work corectly.
I'm able to schedule recordings, and if I go into "Now Palying"
while the show is still being broadcast, I can then watch it, even if the

The only reply that I've recievd dirtly related to this, sugested that I
try to increase teh swap space. But when I try to use the -s 127
option, I get an error message about the disk not being big enough to do
this. This is using the original 60G disk from the Tivo, and a 60 hour
backup downloaded from tivostuff.

Should I try this with the biger drive?

broadcast ends while I'm still watching the show. As soon as I leave teh show, if it's not
still on the air, any atempt to replay it results in an error message about trying to record
when there is no siganl!

Programs that are scheduled and "recorded", and that I don't go into while still playing,
generate the same error message. Thus I'm unable to see any shows, unless I catch them while
they are being broadcast. Pretty useless.

I think that this indicates that I'm not getting a corect restore. Does that make sesne? I've
tried this with 2 different disks, the original Tivo one, and a brand new Maxtor 120G. Both
pass extensive disk diagnostics with flying colors.
--
"They that would give up essential liberty for temporary safety deserve
neither liberty nor safety."
-- Benjamin Franklin
Stan Brown
2003-11-20 22:54:59 UTC
Permalink
Post by Ted
Post by Stan Brown
Post by Ted
Does it show the correct partition tables while booting to linux (perhaps
using the mfstools cd?)...
No. fdisk -l reports an invalid parition table bothe before, and after
doing an mfstools restore, both booted intot my normal Debina system, and
booted from the CD included with "Hacking Tivo".
Did I ask does it show the right partition when you do fdisk -l ? Nope...
Maybe you could post what it says while booting the mfstools CD? It will be
long... but I guess thats what will need to be done to show you the drives
with the paritions.
OK, clearly I'm confused here.

Here's the (I think) relevant section of dmesg, booted from the CD from the
"Hacking Tivo" book:


Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: IDE controller on PCI bus 00 dev 39
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: VIA vt82c686b (rev 40) IDE UDMA100 controller on pci00:07.1
ide0: BM-DMA at 0xd400-0xd407, BIOS settings: hda:DMA, hdb:DMA
ide1: BM-DMA at 0xd408-0xd40f, BIOS settings: hdc:DMA, hdd:DMA
hda: IC35L040AVER07-0, ATA DISK drive
hdb: WDC WD600AW-00DDK1, ATA DISK drive
hdc: Hewlett-Packard CD-Writer cd16r, ATAPI CD/DVD-ROM drive
hdd: ATAPI-CD ROM-DRIVE-56MAX, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: 80418240 sectors (41174 MB) w/1916KiB Cache, CHS=5005/255/63, UDMA(100)
hdb: 117231408 sectors (60022 MB) w/2048KiB Cache, CHS=7297/255/63, UDMA(100)
hdc: ATAPI 40X CD-ROM CD-R/RW drive, 2048kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.12
hdd: ATAPI 56X CD-ROM drive, 128kB Cache, UDMA(33)
Partition check:
hda: hda1 hda2
hdb:Signature 9214, be16 Signature 1492
Blocks in Map = e
mac st=1 sz=3f name='Apple' t='Apple_partition_map' bim=e
hdb1 mac st=6de8c40 sz=1 name='Bootstrap 1' t='Image' bim=e
hdb2 mac st=6de8c41 sz=2000 name='Kernel 1' t='Image' bim=e
hdb3 mac st=6deac41 sz=40000 name='Root 1' t='Ext2' bim=e
hdb4 mac st=6e2ac41 sz=1000 name='Bootstrap 2' t='Image' bim=e
hdb5 mac st=6e2bc41 sz=1000 name='Kernel 2' t='Image' bim=e
hdb6 mac st=6e2cc41 sz=40000 name='Root 2' t='Ext2' bim=e
hdb7 mac st=6e6cc41 sz=20000 name='Linux swap' t='Swap' bim=e
hdb8 mac st=6e8cc41 sz=40000 name='/var' t='Ext2' bim=e
hdb9 mac st=6eccc41 sz=80000 name='MFS application region' t='MFS' bim=e
hdb10 mac st=3d7d840 sz=306b400 name='MFS media region' t='MFS' bim=e
hdb11 mac st=6f4cc41 sz=80000 name='Second MFS application region' t='MFS' bim=e
hdb12 mac st=40 sz=3d7d800 name='Second MFS media region' t='MFS' bim=e
hdb13 mac st=6fccc41 sz=2ef name='Extra' t='Apple_Free' bim=e
hdb14

Does that tell you what you are looking for?

So, booted into my normal Debian Linux environment, I can't see these
partitons at all? Is that what you are saying?

So, Im very confused by how the partioning works here. oes the disk not get
a normal partion table (Normal defined as eadable by an X86 machine)?

Do the mfstools utlities manage partion creation, adn sizing WO me having
to do anything oather than run them?
--
"They that would give up essential liberty for temporary safety deserve
neither liberty nor safety."
-- Benjamin Franklin
Joe Smith
2003-11-21 02:57:14 UTC
Permalink
Post by Stan Brown
Here's the (I think) relevant section of dmesg, booted from the CD from the
hda: IC35L040AVER07-0, ATA DISK drive
hdb: WDC WD600AW-00DDK1, ATA DISK drive
hdc: Hewlett-Packard CD-Writer cd16r, ATAPI CD/DVD-ROM drive
hdd: ATAPI-CD ROM-DRIVE-56MAX, ATAPI CD/DVD-ROM drive
hda: 80418240 sectors (41174 MB) w/1916KiB Cache, CHS=5005/255/63, UDMA(100)
hdb: 117231408 sectors (60022 MB) w/2048KiB Cache, CHS=7297/255/63, UDMA(100)
hdc: ATAPI 40X CD-ROM CD-R/RW drive, 2048kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.12
hdd: ATAPI 56X CD-ROM drive, 128kB Cache, UDMA(33)
hda: hda1 hda2
hdb:Signature 9214, be16 Signature 1492
Blocks in Map = e
mac st=1 sz=3f name='Apple' t='Apple_partition_map' bim=e
hdb1 mac st=6de8c40 sz=1 name='Bootstrap 1' t='Image' bim=e
hdb2 mac st=6de8c41 sz=2000 name='Kernel 1' t='Image' bim=e
hdb3 mac st=6deac41 sz=40000 name='Root 1' t='Ext2' bim=e
hdb4 mac st=6e2ac41 sz=1000 name='Bootstrap 2' t='Image' bim=e
hdb5 mac st=6e2bc41 sz=1000 name='Kernel 2' t='Image' bim=e
hdb6 mac st=6e2cc41 sz=40000 name='Root 2' t='Ext2' bim=e
hdb7 mac st=6e6cc41 sz=20000 name='Linux swap' t='Swap' bim=e
hdb8 mac st=6e8cc41 sz=40000 name='/var' t='Ext2' bim=e
hdb9 mac st=6eccc41 sz=80000 name='MFS application region' t='MFS' bim=e
hdb10 mac st=3d7d840 sz=306b400 name='MFS media region' t='MFS' bim=e
hdb11 mac st=6f4cc41 sz=80000 name='Second MFS application region' t='MFS' bim=e
hdb12 mac st=40 sz=3d7d800 name='Second MFS media region' t='MFS' bim=e
hdb13 mac st=6fccc41 sz=2ef name='Extra' t='Apple_Free' bim=e
hdb14
Does that tell you what you are looking for?
That looks like a perfectly fine TiVo disk label.
Post by Stan Brown
So, booted into my normal Debian Linux environment, I can't see these
partitons at all? Is that what you are saying?
Yes, ordinary Linux environments don't have kernel support for MFS
and don't recognize this style of partition map. You will need to
use the special Linux environment from the CD-ROM to do anything.
Post by Stan Brown
So, Im very confused by how the partioning works here. Does the disk not get
a normal partion table (Normal defined as eadable by an X86 machine)?
Correct. TiVo disks use an Apple Macintosh style partion map, not an
MS-DOS style. You'll have to use a version of fdisk that was explictly
compiled to understand Mac partitions to see anything.

You should be able to mount the three Ext2 partitions (Root 1, Root 2,
Var) with no problems. You should be able to run 'mls' as shown on
page 101 of the book.
-Joe
Stan Brown
2003-11-21 12:04:26 UTC
Permalink
Post by Joe Smith
Post by Stan Brown
Here's the (I think) relevant section of dmesg, booted from the CD from the
hda: IC35L040AVER07-0, ATA DISK drive
hdb: WDC WD600AW-00DDK1, ATA DISK drive
hdc: Hewlett-Packard CD-Writer cd16r, ATAPI CD/DVD-ROM drive
hdd: ATAPI-CD ROM-DRIVE-56MAX, ATAPI CD/DVD-ROM drive
hda: 80418240 sectors (41174 MB) w/1916KiB Cache, CHS=5005/255/63, UDMA(100)
hdb: 117231408 sectors (60022 MB) w/2048KiB Cache, CHS=7297/255/63, UDMA(100)
hdc: ATAPI 40X CD-ROM CD-R/RW drive, 2048kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.12
hdd: ATAPI 56X CD-ROM drive, 128kB Cache, UDMA(33)
hda: hda1 hda2
hdb:Signature 9214, be16 Signature 1492
Blocks in Map = e
mac st=1 sz=3f name='Apple' t='Apple_partition_map' bim=e
hdb1 mac st=6de8c40 sz=1 name='Bootstrap 1' t='Image' bim=e
hdb2 mac st=6de8c41 sz=2000 name='Kernel 1' t='Image' bim=e
hdb3 mac st=6deac41 sz=40000 name='Root 1' t='Ext2' bim=e
hdb4 mac st=6e2ac41 sz=1000 name='Bootstrap 2' t='Image' bim=e
hdb5 mac st=6e2bc41 sz=1000 name='Kernel 2' t='Image' bim=e
hdb6 mac st=6e2cc41 sz=40000 name='Root 2' t='Ext2' bim=e
hdb7 mac st=6e6cc41 sz=20000 name='Linux swap' t='Swap' bim=e
hdb8 mac st=6e8cc41 sz=40000 name='/var' t='Ext2' bim=e
hdb9 mac st=6eccc41 sz=80000 name='MFS application region' t='MFS' bim=e
hdb10 mac st=3d7d840 sz=306b400 name='MFS media region' t='MFS' bim=e
hdb11 mac st=6f4cc41 sz=80000 name='Second MFS application region' t='MFS' bim=e
hdb12 mac st=40 sz=3d7d800 name='Second MFS media region' t='MFS' bim=e
hdb13 mac st=6fccc41 sz=2ef name='Extra' t='Apple_Free' bim=e
hdb14
Does that tell you what you are looking for?
That looks like a perfectly fine TiVo disk label.
Post by Stan Brown
So, booted into my normal Debian Linux environment, I can't see these
partitons at all? Is that what you are saying?
Yes, ordinary Linux environments don't have kernel support for MFS
and don't recognize this style of partition map. You will need to
use the special Linux environment from the CD-ROM to do anything.
OK, that makes sens.

However booted from the mfstools CD, or the one from the "Hacking Tivo"
book, fdisk -l still fails, and mls also fails. This is not mornal, is it?
Post by Joe Smith
Post by Stan Brown
So, Im very confused by how the partioning works here. Does the disk not get
a normal partion table (Normal defined as eadable by an X86 machine)?
Correct. TiVo disks use an Apple Macintosh style partion map, not an
MS-DOS style. You'll have to use a version of fdisk that was explictly
compiled to understand Mac partitions to see anything.
OK, thta makes sesne. Would thta include the version on the mfstools CD,
and or the "Hacking Tivo" CD?
Post by Joe Smith
You should be able to mount the three Ext2 partitions (Root 1, Root 2,
Var) with no problems. You should be able to run 'mls' as shown on
page 101 of the book.
-Joe
AH! I wasn't setting the environment variable.

I'll try thta tonight when I get home

THANKS!
--
"They that would give up essential liberty for temporary safety deserve
neither liberty nor safety."
-- Benjamin Franklin
Tony
2003-11-22 03:01:19 UTC
Permalink
Stan,
I fully understand your frustration. I had the same thing just two weeks
ago. (Please continue to read at the end of your message - I do not want to
top-post).
Post by Stan Brown
Post by Joe Smith
Post by Stan Brown
Here's the (I think) relevant section of dmesg, booted from the CD from the
hda: IC35L040AVER07-0, ATA DISK drive
hdb: WDC WD600AW-00DDK1, ATA DISK drive
hdc: Hewlett-Packard CD-Writer cd16r, ATAPI CD/DVD-ROM drive
hdd: ATAPI-CD ROM-DRIVE-56MAX, ATAPI CD/DVD-ROM drive
hda: 80418240 sectors (41174 MB) w/1916KiB Cache, CHS=5005/255/63, UDMA(100)
hdb: 117231408 sectors (60022 MB) w/2048KiB Cache, CHS=7297/255/63, UDMA(100)
hdc: ATAPI 40X CD-ROM CD-R/RW drive, 2048kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.12
hdd: ATAPI 56X CD-ROM drive, 128kB Cache, UDMA(33)
hda: hda1 hda2
hdb:Signature 9214, be16 Signature 1492
Blocks in Map = e
mac st=1 sz=3f name='Apple' t='Apple_partition_map' bim=e
hdb1 mac st=6de8c40 sz=1 name='Bootstrap 1' t='Image' bim=e
hdb2 mac st=6de8c41 sz=2000 name='Kernel 1' t='Image' bim=e
hdb3 mac st=6deac41 sz=40000 name='Root 1' t='Ext2' bim=e
hdb4 mac st=6e2ac41 sz=1000 name='Bootstrap 2' t='Image' bim=e
hdb5 mac st=6e2bc41 sz=1000 name='Kernel 2' t='Image' bim=e
hdb6 mac st=6e2cc41 sz=40000 name='Root 2' t='Ext2' bim=e
hdb7 mac st=6e6cc41 sz=20000 name='Linux swap' t='Swap' bim=e
hdb8 mac st=6e8cc41 sz=40000 name='/var' t='Ext2' bim=e
hdb9 mac st=6eccc41 sz=80000 name='MFS application region' t='MFS' bim=e
hdb10 mac st=3d7d840 sz=306b400 name='MFS media region' t='MFS' bim=e
hdb11 mac st=6f4cc41 sz=80000 name='Second MFS application region' t='MFS' bim=e
hdb12 mac st=40 sz=3d7d800 name='Second MFS media region' t='MFS' bim=e
hdb13 mac st=6fccc41 sz=2ef name='Extra' t='Apple_Free' bim=e
hdb14
Does that tell you what you are looking for?
That looks like a perfectly fine TiVo disk label.
Post by Stan Brown
So, booted into my normal Debian Linux environment, I can't see these
partitons at all? Is that what you are saying?
Yes, ordinary Linux environments don't have kernel support for MFS
and don't recognize this style of partition map. You will need to
use the special Linux environment from the CD-ROM to do anything.
OK, that makes sens.
However booted from the mfstools CD, or the one from the "Hacking Tivo"
book, fdisk -l still fails, and mls also fails. This is not mornal, is it?
Post by Joe Smith
Post by Stan Brown
So, Im very confused by how the partioning works here. Does the disk not get
a normal partion table (Normal defined as eadable by an X86 machine)?
Correct. TiVo disks use an Apple Macintosh style partion map, not an
MS-DOS style. You'll have to use a version of fdisk that was explictly
compiled to understand Mac partitions to see anything.
OK, thta makes sesne. Would thta include the version on the mfstools CD,
and or the "Hacking Tivo" CD?
Post by Joe Smith
You should be able to mount the three Ext2 partitions (Root 1, Root 2,
Var) with no problems. You should be able to run 'mls' as shown on
page 101 of the book.
-Joe
AH! I wasn't setting the environment variable.
I'll try thta tonight when I get home
THANKS
I (Tony) had done a backup of my series-1 v1.3 disk 2 years ago, using the
Tiger/Dylan disks. At that time, I had expanded to a single 60G drive, later
running v2.0.1. I also bought the TivoNet (the early one), but I stopped at
just when I was successful in getting the Bash Prompt on another Tivo. This 60G
Tivo did not have the Bash prompt. I did not subscribe, and my Tivo time was
slipping, to about 10 minutes behind normal.
Two weeks ago, I decided to upgrade to 120G, and to get the bash prompt so
that I can manually set the clock. Being sluggish in the Tivo-thing after 2
years, I decided to experiment with my spare Tivo first. I have gathered 3
bootable ISO images and burned them to 3 CDRWs, and they are
a. mfstools2 - from9thTee.iso 10624KB (10/2/2003) (I called it RW2)
b. Kazymyr's TiVo Boot CD - also downloaded from 9thTee, that has MFSTools1.0.
(I called it RW3)
c. mfstools2- From the site below - recommended by Keegan's book - 11908KB
(11/08/2003) (http://star1.jongans.com/mfstools2.iso) - I called it RW5.

The backup/expansion went through very smoothly with all 3 bootable CDs.
However, when I tried to mount the 120G disk partitions, only RW3 (Kazymyr) can
do it. The other two all balk at the disk that they had created a moment ago.
Their creations (the 120G drive), however, all ran fine in Tivo. It is just
that RW2 and RW5 cannot recognise the partitions (and therefore, no mount)

As an experiment, I slipped a Redhat Linux 6.2 drive in as the Primary Slave.
RW3(Kazymyr) *cannot* recognise this Redhat drive partitions, but RW2 and RW5
*can*!!!
My conclusion - Kazymyr's Linux kernel was compiled differently, with MFS
partition consideration. The other twos are probably (that is purely
assumption, no fact to support this) just mainstream x86 linux, but can run the
MFSbackup and MFSrestore applications. They(RW2 and RW5) cannot be used to
mount the Tivo partitions, and therefore, in my case, cannot be used to get the
bash prompt.

I hope that helps.
Tony
Stan Brown
2003-11-23 17:37:36 UTC
Permalink
Post by Joe Smith
Post by Stan Brown
Here's the (I think) relevant section of dmesg, booted from the CD from the
hda: IC35L040AVER07-0, ATA DISK drive
hdb: WDC WD600AW-00DDK1, ATA DISK drive
hdc: Hewlett-Packard CD-Writer cd16r, ATAPI CD/DVD-ROM drive
hdd: ATAPI-CD ROM-DRIVE-56MAX, ATAPI CD/DVD-ROM drive
hda: 80418240 sectors (41174 MB) w/1916KiB Cache, CHS=5005/255/63, UDMA(100)
hdb: 117231408 sectors (60022 MB) w/2048KiB Cache, CHS=7297/255/63, UDMA(100)
hdc: ATAPI 40X CD-ROM CD-R/RW drive, 2048kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.12
hdd: ATAPI 56X CD-ROM drive, 128kB Cache, UDMA(33)
hda: hda1 hda2
hdb:Signature 9214, be16 Signature 1492
Blocks in Map = e
mac st=1 sz=3f name='Apple' t='Apple_partition_map' bim=e
hdb1 mac st=6de8c40 sz=1 name='Bootstrap 1' t='Image' bim=e
hdb2 mac st=6de8c41 sz=2000 name='Kernel 1' t='Image' bim=e
hdb3 mac st=6deac41 sz=40000 name='Root 1' t='Ext2' bim=e
hdb4 mac st=6e2ac41 sz=1000 name='Bootstrap 2' t='Image' bim=e
hdb5 mac st=6e2bc41 sz=1000 name='Kernel 2' t='Image' bim=e
hdb6 mac st=6e2cc41 sz=40000 name='Root 2' t='Ext2' bim=e
hdb7 mac st=6e6cc41 sz=20000 name='Linux swap' t='Swap' bim=e
hdb8 mac st=6e8cc41 sz=40000 name='/var' t='Ext2' bim=e
hdb9 mac st=6eccc41 sz=80000 name='MFS application region' t='MFS' bim=e
hdb10 mac st=3d7d840 sz=306b400 name='MFS media region' t='MFS' bim=e
hdb11 mac st=6f4cc41 sz=80000 name='Second MFS application region' t='MFS' bim=e
hdb12 mac st=40 sz=3d7d800 name='Second MFS media region' t='MFS' bim=e
hdb13 mac st=6fccc41 sz=2ef name='Extra' t='Apple_Free' bim=e
hdb14
Does that tell you what you are looking for?
That looks like a perfectly fine TiVo disk label.
Post by Stan Brown
So, booted into my normal Debian Linux environment, I can't see these
partitons at all? Is that what you are saying?
Yes, ordinary Linux environments don't have kernel support for MFS
and don't recognize this style of partition map. You will need to
use the special Linux environment from the CD-ROM to do anything.
Post by Stan Brown
So, Im very confused by how the partioning works here. Does the disk not get
a normal partion table (Normal defined as eadable by an X86 machine)?
Correct. TiVo disks use an Apple Macintosh style partion map, not an
MS-DOS style. You'll have to use a version of fdisk that was explictly
compiled to understand Mac partitions to see anything.
You should be able to mount the three Ext2 partitions (Root 1, Root 2,
Var) with no problems. You should be able to run 'mls' as shown on
page 101 of the book.
-Joe
OK, the disk is the primary slave, so I set the MFS_HDA environemnt
variable to "/dev/hdb", that's correct, right. Then I tried the example
from the book "mls /MessageBoard/MessageItem/" and got "No Such File
Or Directory!". What other directories can I try?

I also tried to mount the root partion, which seesm to be /dev/hdb3
acording to dmesg (booted from the "Hacking Tivo" book. I created
/tmp/mnt, and did "mount -t ext2 /dev/hdb3 /tmp/mnt". I got an eror
message saying that either I had the wrong FS type, or the superblock was bad.

I'm really desperate to get this working before I leave for Thanksgiving!
Can someone give me some idea what I'm doing wrong?
--
"They that would give up essential liberty for temporary safety deserve
neither liberty nor safety."
-- Benjamin Franklin
Joe Smith
2003-11-23 21:40:00 UTC
Permalink
Post by Joe Smith
Post by Stan Brown
Here's the (I think) relevant section of dmesg, booted from the CD from the
hda: IC35L040AVER07-0, ATA DISK drive
hdb: WDC WD600AW-00DDK1, ATA DISK drive
hdc: Hewlett-Packard CD-Writer cd16r, ATAPI CD/DVD-ROM drive
hdd: ATAPI-CD ROM-DRIVE-56MAX, ATAPI CD/DVD-ROM drive
hda: 80418240 sectors (41174 MB) w/1916KiB Cache, CHS=5005/255/63, UDMA(100)
hdb: 117231408 sectors (60022 MB) w/2048KiB Cache, CHS=7297/255/63, UDMA(100)
hdc: ATAPI 40X CD-ROM CD-R/RW drive, 2048kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.12
hdd: ATAPI 56X CD-ROM drive, 128kB Cache, UDMA(33)
hda: hda1 hda2
hdb:Signature 9214, be16 Signature 1492
Blocks in Map = e
mac st=1 sz=3f name='Apple' t='Apple_partition_map' bim=e
hdb1 mac st=6de8c40 sz=1 name='Bootstrap 1' t='Image' bim=e
hdb2 mac st=6de8c41 sz=2000 name='Kernel 1' t='Image' bim=e
hdb3 mac st=6deac41 sz=40000 name='Root 1' t='Ext2' bim=e
hdb4 mac st=6e2ac41 sz=1000 name='Bootstrap 2' t='Image' bim=e
hdb5 mac st=6e2bc41 sz=1000 name='Kernel 2' t='Image' bim=e
hdb6 mac st=6e2cc41 sz=40000 name='Root 2' t='Ext2' bim=e
hdb7 mac st=6e6cc41 sz=20000 name='Linux swap' t='Swap' bim=e
hdb8 mac st=6e8cc41 sz=40000 name='/var' t='Ext2' bim=e
hdb9 mac st=6eccc41 sz=80000 name='MFS application region' t='MFS' bim=e
hdb10 mac st=3d7d840 sz=306b400 name='MFS media region' t='MFS' bim=e
hdb11 mac st=6f4cc41 sz=80000 name='Second MFS application region' t='MFS' bim=e
hdb12 mac st=40 sz=3d7d800 name='Second MFS media region' t='MFS' bim=e
hdb13 mac st=6fccc41 sz=2ef name='Extra' t='Apple_Free' bim=e
hdb14
Does that tell you what you are looking for?
That looks like a perfectly fine TiVo disk label.
On second view, that does not look right.
In all the examples I've seen, the root partitions are
/dev/hdX4 and /dev/hdX7 with the var partition as /dev/hdX9.

Since you've got Jeff Keegan's book, note that Listing 4-1 on page 105
shows using pdisk (not fdisk) to list the partitions.

1) Does pdisk number the partitions the same way as the kernel messages?
2) Can you successfully mount /dev/hdb4, /dev/hdb7 or /dev/hdb9?
Stan Brown
2003-11-20 23:02:54 UTC
Permalink
Post by Ted
Post by Stan Brown
Post by Ted
Does it show the correct partition tables while booting to linux (perhaps
using the mfstools cd?)...
No. fdisk -l reports an invalid parition table bothe before, and after
doing an mfstools restore, both booted intot my normal Debina system, and
booted from the CD included with "Hacking Tivo".
Did I ask does it show the right partition when you do fdisk -l ? Nope...
Maybe you could post what it says while booting the mfstools CD? It will be
long... but I guess thats what will need to be done to show you the drives
with the paritions.
One more thing thta I meant to add to my first reply to this message.

Booted from teh "Hacking Tivo" CD, and having finally seen teh light,
thanks to you, as to how to determine what parition is what, then I tried
to do an "mls" on one of the MFS paritions, and just got an error.


One more question, is usign that CD OK, or do you want me to download, and
burn the original mfstools CD?

BTW, Im confused that your example does show fdisk as seeing the paritions,
and I can't seem to get that to work.... What important concept am I
missing here?
--
"They that would give up essential liberty for temporary safety deserve
neither liberty nor safety."
-- Benjamin Franklin
Stan Brown
2003-11-20 23:29:17 UTC
Permalink
Post by Stan Brown
Post by Ted
Post by Stan Brown
Post by Ted
Does it show the correct partition tables while booting to linux (perhaps
using the mfstools cd?)...
No. fdisk -l reports an invalid parition table bothe before, and after
doing an mfstools restore, both booted intot my normal Debina system, and
booted from the CD included with "Hacking Tivo".
Did I ask does it show the right partition when you do fdisk -l ? Nope...
Maybe you could post what it says while booting the mfstools CD? It will be
long... but I guess thats what will need to be done to show you the drives
with the paritions.
One more thing thta I meant to add to my first reply to this message.
Booted from teh "Hacking Tivo" CD, and having finally seen teh light,
thanks to you, as to how to determine what parition is what, then I tried
to do an "mls" on one of the MFS paritions, and just got an error.
One more question, is usign that CD OK, or do you want me to download, and
burn the original mfstools CD?
BTW, Im confused that your example does show fdisk as seeing the paritions,
and I can't seem to get that to work.... What important concept am I
missing here?
OK, one more data point.

I booted from a copy of the "genuine" MSFTools 2.0 CD, and had pretty much
the same result that I reported earlier. dmesg saw the paritions on boot. I
re-ran mfsrestore, and still mls can't read the MFS paritions. And fdisk
can't see the partiton tble, either.
--
"They that would give up essential liberty for temporary safety deserve
neither liberty nor safety."
-- Benjamin Franklin
Stan Brown
2003-11-20 21:04:34 UTC
Permalink
Post by Ted
Does it show the correct partition tables while booting to linux (perhaps
using the mfstools cd?)...
Go off that..
No, as you can see here.
Post by Ted
Post by Stan Brown
smokey:~# fdisk -l /dev/hdb
Disk /dev/hdb: 60.0 GB, 60022480896 bytes
255 heads, 63 sectors/track, 7297 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk /dev/hdb doesn't contain a valid partition table
I'm able to duplicate this same error in my normal Debian runtime, and
booted from the CD that comes with teh "Hacking Tivo" Book.
mfstools restore -xzpi <backup_name>
This appears to go OK. I did this using my backup, and 2 different backups
downloaded from tivostuff. The results are identical in all cases. If I
run
Post by Stan Brown
MFS volume set for /dev/hdb
The MFS volume set contains 4 partitions
/dev/hdb10
MFS Partition Size: 256MiB
/dev/hdb11
MFS Partition Size: 24790MiB
/dev/hdb12
MFS Partition Size: 256MiB
/dev/hdb13
MFS Partition Size: 31483MiB
Total MFS volume size: 56785MiB
Estimated hours in a standalone TiVo: 57
This MFS volume may be expanded 4 more times
But fdisk -l is still unhappy.
Booted from the CD, I tried mls on these 3 partitons, and just go errors.
Do I need to create a partiton table first? If so, howw do I do it.
If not what stupid mistake am I making.
You will have to forgive my tone, I've been fighting this for about 2
weeks
Post by Stan Brown
now, and I'm running out of patienance.
Post by Wes Newell
Disk /dev/hde: 60.0 GB, 60022480896 bytes
255 heads, 63 sectors/track, 7297 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hde1 1 1 8001 a OS/2 Boot Manager
/dev/hde2 2 393 3148740 b Win95 FAT32
/dev/hde4 394 7297 55456380 5 Extended
/dev/hde5 * 394 916 4200966 7 HPFS/NTFS
/dev/hde6 * 917 1001 682731 83 Linux
/dev/hde7 * 1002 1051 401593+ 82 Linux swap
/dev/hde8 * 1052 2369 10586803+ 83 Linux
/dev/hde9 * 2370 3318 7622811 83 Linux
/dev/hde10 * 3319 6022 21719848+ 83 Linux
/dev/hde11 * 6023 7297 10241406 7 HPFS/NTFS
BTW, I've tried this with 2 different hard drives, the original one that
came witht eh Tivo, and a 120G Maxtor. Same result :-(
I must be making some stupid mistake!
--
"They that would give up essential liberty for temporary safety deserve
neither liberty nor safety."
-- Benjamin Franklin
--
"They that would give up essential liberty for temporary safety deserve
neither liberty nor safety."
-- Benjamin Franklin
Stan Brown
2003-11-23 17:13:19 UTC
Permalink
Post by Wes Newell
Post by Stan Brown
I'm still beating my (quite bloddy) head against trying to resurecte my
Tivo.
Can anyone point me to instrunctions as to how to mount the partitions of
the disk I have removed from my Serries 2 box under Linux X86?
Install the hd. For this I'll assume it's the slave of the primary disk
controller. It's device name is hdb.
First you need to verify the disk. Easily done with fdisk, sfdisk, or any
of the other fdisk type programs. Type "man fdisk" for full explaination
of fdisk. Here's an example of using fdisk to identify the drive and
partitions.
Disk /dev/hde: 60.0 GB, 60022480896 bytes
255 heads, 63 sectors/track, 7297 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hde1 1 1 8001 a OS/2 Boot Manager
/dev/hde2 2 393 3148740 b Win95 FAT32
/dev/hde4 394 7297 55456380 5 Extended
/dev/hde5 * 394 916 4200966 7 HPFS/NTFS
/dev/hde6 * 917 1001 682731 83 Linux
/dev/hde7 * 1002 1051 401593+ 82 Linux swap
/dev/hde8 * 1052 2369 10586803+ 83 Linux
/dev/hde9 * 2370 3318 7622811 83 Linux
/dev/hde10 * 3319 6022 21719848+ 83 Linux
/dev/hde11 * 6023 7297 10241406 7 HPFS/NTFS
What were you booted from when you did this? Was this on a Series 2 Tivo?
--
"They that would give up essential liberty for temporary safety deserve
neither liberty nor safety."
-- Benjamin Franklin
Loading...