Laptop hard drive

[kernaltao]

I have been trying to get a laptop drive (2.5") to work in a Samsung S4040R DTivo with version 6.2 with no luck. The 2.5" drive is a Hitachi 80GB, and I am using a 2.5" to 3.5" drive adapter (see attached picture). Here is what I have done:

1. Backup working hacked image from 80gb 3.5" drive (mfsbackup -f 9999 -so /mnt/tivo.bak /dev/hdc).
2. Test image by restoring to a different 80gb 3.5" drive. Boots fine in TiVo.
3. Connect 2.5" drive to PC using adapter and boot to PTV LBA CD; Linux recognizes drive at hdc just fine.
4. Restore image to drive using same method as in #2 above (mfsrestore -bzpi /mnt/tivo.bak /dev/hdc); install in DTivo; here is the serial output:

read_sector got timeout
autoboot failed to read boot sector
Initializing USB ethernet
Device on dev=13 fnc=0 port=0
ASIX on dev=13 fnc=0 port=0
is ASIX......... full duplex
USB's mac address 0:10:60:84:cc:c5
USB ethernet initialized
Sent 0th bootp request.
Sent 1th bootp request.
Sent 2th bootp request.
Sent 3th bootp request.

5. Since it failed to read the boot sector and began trying to boot from the network, I tried disconnecting the USB network adapter (Linksys USB200M); this is the serial output:

read_sector got timeout
autoboot failed to read boot sector
Initializing USB ethernet
init there is no device
Ram size = 64
Service number is 3810000E03649A1.
What is password?

6. Obviously, it wasn't finding the boot sector on the drive, so I tried placing a jumper on the pins. According to the drive, if there is no jumper, it is Device0; if there is a jumper furthest from pin 1, it is Device1; if the jumper is across the bottom pins, it is Cable Select. I tried each of these, and in each case, I received the same serial output as above (#4). I even tried every other combination, and I still received the same serial output.

7. I then tried a different IDE cable that I had purchased from 9thTee. Same output as #4 above.

8. I then tried a different 80GB 2.5" drive. Same output as #4 above.

9. I checked to be sure the drive wasn't locked (grasping at straws now!). It wasn't.

So, it seems that the DTivo is not recognizing the drive at all. The only thing I can think is that the 2.5" to 3.5" adapter is causing the problem. Here is the adapter that I purchased:

http://www.ecost.com/ecost/shop/detail~dpno~158393.asp

Has someone been successful using a different adapter?

Any other suggestions?

BTW, the bootpage is set to: root=/dev/hda4 dsscon=true console=2,115200 upgradesoftware=false

Please do not comment on whether or not I should be using a laptop drive. That is not the type of assistance I am requesting. I KNOW that I can use a 3.5" drive; I want to get a 2.5" drive to work. If you want to discuss the merits/issues with using a laptop drive, please begin a new thread. If you have suggestions on how to get a laptop drive to work in a DTivo, I would very much appreciate your assistance.

Thanks,
kernaltao

[fantmn]

There is a thread here (http://www.dealdatabase.com/forum/showthread.php?t=47329)that discusses some boot problems. It does not look like they got it resolved, but the first couple of post have some ideas. Has the drive ever been used in a laptop? There are some issues that can occur if XP ever touched the drive. I have one of these adapters and noticed that it is very easy to get the cable plugged in upside down with mine (pin 1 on the wrong end). Just an idea.

[kernaltao]

fantmn,

Thanks for the quick reply. I read that thread, and I didn't really find anything that may help. I may try modifying the bootpage to /dev/hdb rather than /dev/hda in case the adapter is causing the drive not to be recognized as Master.

I did check the partitions on the drive, and they seem to be fine (same partition structure as the 3.5" drive that boots fine). The Hitachi 80GB drive is brand new with no existing partitions. The other 2.5" drive that I tried did have WinXP on it at one time, but I made sure to clear all partitions and MBR with fdisk before applying the Tivo image.

Thanks,
kernaltao

[kernaltao]

Also, I did make sure the adapter was connected correctly. It wouldn't have worked in my PC if it wasn't. On the other side of the adapter, it was easy to figure out how to connect the IDE cable because of the pin-out and the notch on the outside of the connector.

[fantmn]

I don't think fdisk clears all the crap XP puts there. It may be a pain, but a low-level format (all zeros) of that drive before laying the image on it might help. As for the new drive one would think it would be clean. One more thing to try might be to put the big drive and the Tivo with the laptop drive set as secondary. Then boot the tivo and get to the bash prompt and see if the Tivo sees the laptop drive during bootup etc. I think it should show up as hdb. If so, try pdisk, mount, etc on it and see what happens. That might tell you something. Can you hear the drive spin up in the Tivo? Just some more ideas here. Also I lay my drive upside down to make sure nothing is touching the circuit board.

[eastwind]

I've never tried running a laptop drive, but it makes sense to me except for the expense. At this point I would try running an executable on the drive called make_tivo_bootable (or something like that). Otherwise, check the MBR and compare it to the MBR of a working 3.5" drive to see what's different. If the drive came out of a laptop I would suspect some foolishness in the MBR to check for special keys at bootup, but since it wasn't ever in a laptop I don't think that should be an issue unless laptop's all use the same code and the manufacturers write it there.

ew

[kernaltao]

fantmn,

I may try the low-level format later, but because I believe it will just return the drive to the way it was when I received it, I am not confident that it will do the trick. I really think it has to do with the MBR (as eastwind mentioned in his post). I did mount the 2.5" drive as a secondary in the Tivo (3.5" as primary), and it did see the laptop drive at hdb. Once the Tivo booted, I was able to mount the partitions, see the partitions in pdisk, etc. Everything looked fine.

eastwind,

Is there such an executable? If so, do you know where I can find it? How can I compare the MBR of the two disks? Is there a way using pdisk?

[eastwind]

Of course there is such an executable..link (http://www.tivocommunity.com/tivo-vb/showthread.php?p=1193407&&#post1193407)

What boot CD did you use? Have you already ruled out byteswapping issues? I think some of the boot Cds have MakeTivoBootable on them (not sure about the capitalization).

ew

[fantmn]

MakeTivoBootable seems to be here (http://alt.org/wiki/index.php/MakeTivoBootable). With instructions. I found it in a thread using the search function.

Edit: Eastwind beat me to it. Guess he types faster.

[kernaltao]

I am using the PTVUpgrade lba48 v4.01 CD, so byteswapping is not enabled. It didn't have the MakeTiVoBootable utility on it, so I downloaded it from the link that you provided. I booted to the PTV CD with the drive attached as Secondary Master (Cable Select on Master IDE connector connected to IDE2) and the MakeTiVoBootable utility on a FAT32 partition on the C drive, and then issued the following commands:

mount /dev/hda1 /mnt
cd /mnt
MakeTiVoBootable -d /dev/hdc --pk 3 --ak 6 --bp root=/dev/hda4

I probably could have done it in that one command, but I then changed the bootpage back using:

bootpage -P "root=/dev/hda4 dsscon=true console=2,115200 upgradesoftware=false" -C /dev/hdc

I installed the drive in the TiVo and still got the same result (see #4 in my first post).

Any other ideas?

[rpl]

Are sure the drive jumper is set at master and not cable select. You didn't mention checking the jumper. If it is set at master try cable select. Some of my tivos came with the jumper on CS. ??

[kernaltao]

rpl,

Yes, in my first post above, I mention that I checked that (#6 in my post).

Thanks

[fantmn]

What does bootpage -b return. Also if you capture the kernel log when you booted with the laptop drive in as the second drive, maybe someone will spot something in it or get reminded of something else to try. It seems that you are breaking new ground here (duh). Do you have a prom password set so if you boot with it and get the prom password prompt (same as #4) you may be able to use some of the prom functions (at the direction of others) to diagnose the problem. There may be commands that can be done while the 2.5" drive is in the Tivo. You set the prom password with the command: crypto -u -srp password where password is the value you want as your password. This command must be run on the Tivo. For you that means boot the 3.5" disk, set the password, then backup and restore. It might be worthwhile to post the output from the pdisk -l on the restored 2.5" drive. The more info posted the more likely it is that one of the really experienced Tivo guys might spot something.

[ocntscha]

I looked at the picture of your adapter and noticed only 2 wires coming off the molex power connector. I have a theory which a little Googling has told me might be right.. I don't know but I think maybe the Tivo power supply only outputs 12 Volts. Whereas your adapter is trying to use red wire to get 5 volts but even though the Tivo molex connectors have the red wire maybe there isn't actually 5 volts there. In other words, when you stick the 2.5" drive in your Tivo its not getting any power. This is mostly just speculation on my part. A bit of Googling seemed to support the idea. If you have a volt meter just measure the voltage across the red and black wires that your trying to supply voltage to your 2.5" drive with. I think maybe your 2.5" drive needs 5 volts but is either getting no voltage or 12 volts.

[sucram65]

I would not use a laptop drive for a Tivo. They are not designed for that kind of usage like a 3.5 inch drive is. I think you'll be lucky if it lasted a year at best.

[ocntscha]

I would not use a laptop drive for a Tivo. They are not designed for that kind of usage like a 3.5 inch drive is. I think you'll be lucky if it lasted a year at best.I think your wrong. I don't think the original poster cares what either of us thinks since he made the following statement in the first post..If you want to discuss the merits/issues with using a laptop drive, please begin a new thread.

[rpl]

Most desktop hd require both 12 & 5 volts so I'm sure the tivo is ps is putting out both. Notebook hd usally just req 5 volts, so I'm guessing that is why the adapter only has 2 wires.

It looks like your using a 80 conductor cable and I wonder if that adapter is a ATA33? I put a 40 conductor cable in my tivo and had the same error you did. While that doesn't prove that is your problem since my hd was probably an ATA100. Good luck, it will be interesting to see if you get this hd working with a tivo. The extra 40 conductors are grounded to reduce noise, I would also try to go ahead and put the mounting screws on your hd to your mounting adapter since this will also help to reduce common mode noise. Kind of a long shot.

[kernaltao]

What does bootpage -b return.

I wasn't sure when to run this. When I run it with the drive connected to my PC and booted to the PTV CD, I get

Boot Partition: 4

When I run it on the TiVo with both drives connected (booted to 3.5" drive), I just get "3" when I run it on either drive (hda and hdb).

Also if you capture the kernel log when you booted with the laptop drive in as the second drive, maybe someone will spot something in it or get reminded of something else to try. It seems that you are breaking new ground here (duh).

The kernel log is attached (kernel.txt). This is when I had both drives connected to the Tivo and booting from the 3.5".

You set the prom password with the command: crypto -u -srp password where password is the value you want as your password. This command must be run on the Tivo. For you that means boot the 3.5" disk, set the password, then backup and restore.

I have now done this. Therefore, the 2.5" drive now has the prom password.

It might be worthwhile to post the output from the pdisk -l on the restored 2.5" drive. The more info posted the more likely it is that one of the really experienced Tivo guys might spot something.

Attached is the pdisk output for both the 3.5" and 2.5" drives. This was run while both were installed in the Tivo and booted from the 3.5" drive (40gb).

In other words, when you stick the 2.5" drive in your Tivo its not getting any power.


t looks like your using a 80 conductor cable and I wonder if that adapter is a ATA33?

Thank you both for these suggestions, but I don't believe either are valid. The reason being that I can attach the 2.5" drive as secondary to the 3.5" drive, boot the Tivo to the 3.5" drive and the 2.5" drive is recognized. I can then mount partitions from the 2.5" drive, run pdisk against it, etc. Therefore, it is getting enough power and the cable is correct. Obviously, this is using the Master/Slave cable that I purchased from 9thTee, not the single one that came with the Tivo, so I tried booting the 2.5" drive from the double cable with no luck (same serial output as #4 in my original post).

Lastly, I have attached the serial output when booting the Tivo from the 3.5" drive and the 2.5" drive connected as slave (tivo-25hdb.txt).

Interstingly, when I tried switching the bootpage on the 2.5" drive to /dev/hdb4 (along with the dsscon, serial and softwareupgrade params), here is the serial output:

Partition 0 signature is false, trying alternate
diskboot found partition 0 signature is false.
Ram size = 64
Service number is 3810000E03649A1.
What is password?

It seems to me that it sees the boot partition, but it is incorrect for some reason (kernel is pointing to hda? some other pointers to hda?).

Any ideas anyone?

[eastwind]

Since the 3.5" is working and the 2.5" isn't, what happens if you dd the 3.5" to the 2.5" and reboot (first without expanding, then after expanding)?

ew

[kernaltao]

Since the 3.5" is working and the 2.5" isn't, what happens if you dd the 3.5" to the 2.5" and reboot (first without expanding, then after expanding)?


I already tried that. It didn't work. I tried booting the Tivo before expanding and after. In both instances, I got the same serial output (as #4 in my original post). I even tried a piped mfsbackup | mfsrestore. Didn't work either. I tried the mfsrestore with -bzpi then mkswap and mfsadd; I tried mfsrestore with -xzpi.

I'm stumped!

[eastwind]

I already tried that. It didn't work. I tried booting the Tivo before expanding and after. In both instances, I got the same serial output (as #4 in my original post). I even tried a piped mfsbackup | mfsrestore. Didn't work either. I tried the mfsrestore with -bzpi then mkswap and mfsadd; I tried mfsrestore with -xzpi.

I'm stumped!
Sorry, I guess I didn't see where you documented that you tried dd (I still don't except here).

ew

[fantmn]

Maybe try using hexdump to dump the boot area of each drive and compare them. Maybe some byte is different. I like the hexdump in the devbin utilities found HERE (http://tivoutils.sourceforge.net/)because it supports the -C option to yield the format below. The hexdump in the current busybox utilities does not support the -C option. I included a dump of one of my working drives below.

./hexdump -C /dev/hda -n 300
00000000 14 92 03 06 72 6f 6f 74 3d 2f 64 65 76 2f 68 64 |....root=/dev/hd|
00000010 61 34 20 64 73 73 63 6f 6e 3d 74 72 75 65 20 63 |a4 dsscon=true c|
00000020 6f 6e 73 6f 6c 65 3d 32 2c 31 31 35 32 30 30 20 |onsole=2,115200 |
00000030 75 70 67 72 61 64 65 73 6f 66 74 77 61 72 65 3d |upgradesoftware=|
00000040 66 61 6c 73 65 00 00 00 00 00 00 00 00 00 00 00 |false...........|
00000050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
00000080 00 00 00 00 75 6e 6e 61 6d 65 64 00 00 00 00 00 |....unnamed.....|
00000090 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
000000a0 00 00 00 00 0a 6f 4c da 28 71 b0 0a 5a f0 3c 00 |.....oL.(q..Z.<.|
000000b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
00000120 00 00 00 00 00 00 00 00 00 00 00 00 |............|
0000012c


I am stumped too. I guess hexdumping different things and see what the differences are might help. Also I assume the kernel you are using on the drive is LBA48 enabled. I don;t think it would prevent it from booting, but I figured I would ask. I did a quick scan of the thread and did not notice it mentioned, but I did not read real closely either. Also the geometry of the 2.5" drive looks way different from the 3.5". Maybe there is something there.

[fantmn]

I got to thinking about the LBA48 thing and remembered this is a 120GB drive so it should not matter. I wonder if maybe the laptop drive is not powering up fast enough to be seen by the tivo for booting. Maybe some powersave mode or something. There is a thread HERE (http://www.dealdatabase.com/forum/showthread.php?t=48434)that goes over some of the information about using the prom menu to boot the Tivo. From your output (1st post #4) it looks like you are getting the prom menu. Now that you have the password set try using the prom menu to boot after a min. or two to make sure the 2.5" drive is all the way active.

[kernaltao]

Sorry, I guess I didn't see where you documented that you tried dd (I still don't except here).

I apologize that my post came across as somewhat harsh. I didn't intend for it to seem that I was reprimanding you for not reading my post. I hadn't mentioned it before. I was just saying that I did try that and it didn't work. I should have thanked you for your suggestion and explained that I did try it before, but that I didn't mention it in my first post. I am sorry for the miscommunication on my part.

[kernaltao]

Maybe try using hexdump to dump the boot area of each drive and compare them. Maybe some byte is different. I like the hexdump in the devbin utilities found HERE (http://tivoutils.sourceforge.net/)because it supports the -C option to yield the format below. The hexdump in the current busybox utilities does not support the -C option. I included a dump of one of my working drives below.

./hexdump -C /dev/hda -n 300
00000000 14 92 03 06 72 6f 6f 74 3d 2f 64 65 76 2f 68 64 |....root=/dev/hd|
00000010 61 34 20 64 73 73 63 6f 6e 3d 74 72 75 65 20 63 |a4 dsscon=true c|
00000020 6f 6e 73 6f 6c 65 3d 32 2c 31 31 35 32 30 30 20 |onsole=2,115200 |
00000030 75 70 67 72 61 64 65 73 6f 66 74 77 61 72 65 3d |upgradesoftware=|
00000040 66 61 6c 73 65 00 00 00 00 00 00 00 00 00 00 00 |false...........|
00000050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
00000080 00 00 00 00 75 6e 6e 61 6d 65 64 00 00 00 00 00 |....unnamed.....|
00000090 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
000000a0 00 00 00 00 0a 6f 4c da 28 71 b0 0a 5a f0 3c 00 |.....oL.(q..Z.<.|
000000b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
00000120 00 00 00 00 00 00 00 00 00 00 00 00 |............|
0000012c


I am stumped too. I guess hexdumping different things and see what the differences are might help. Also I assume the kernel you are using on the drive is LBA48 enabled. I don;t think it would prevent it from booting, but I figured I would ask. I did a quick scan of the thread and did not notice it mentioned, but I did not read real closely either. Also the geometry of the 2.5" drive looks way different from the 3.5". Maybe there is something there.


Here are the hexdumps from the two drives. The first is from the 3.5" drive (hda) and the second is from the 2.5" (hdb):

TiVo1: {/hacks} % hexdump -C /dev/hda -n 300
00000000 14 92 03 06 72 6f 6f 74 3d 2f 64 65 76 2f 68 64 |....root=/dev/hd|
00000010 61 34 20 64 73 73 63 6f 6e 3d 74 72 75 65 20 63 |a4 dsscon=true c|
00000020 6f 6e 73 6f 6c 65 3d 32 2c 31 31 35 32 30 30 20 |onsole=2,115200 |
00000030 75 70 67 72 61 64 65 73 6f 66 74 77 61 72 65 3d |upgradesoftware=|
00000040 66 61 6c 73 65 00 00 00 00 00 00 00 00 00 00 00 |false...........|
00000050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
00000080 00 00 00 00 75 6e 6e 61 6d 65 64 00 00 00 00 00 |....unnamed.....|
00000090 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
000000a0 00 00 00 00 0a 3c 19 d3 0f d4 a1 34 7a 58 76 6d |.....<.....4zXvm|
000000b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
00000120 00 00 00 00 00 00 00 00 00 00 00 00 |............|
0000012c


TiVo1: {/hacks} % hexdump -C /dev/hdb -n 300
00000000 14 92 03 06 72 6f 6f 74 3d 2f 64 65 76 2f 68 64 |....root=/dev/hd|
00000010 61 34 20 64 73 73 63 6f 6e 3d 74 72 75 65 20 63 |a4 dsscon=true c|
00000020 6f 6e 73 6f 6c 65 3d 32 2c 31 31 35 32 30 30 20 |onsole=2,115200 |
00000030 75 70 67 72 61 64 65 73 6f 66 74 77 61 72 65 3d |upgradesoftware=|
00000040 66 61 6c 73 65 00 00 00 00 00 00 00 00 00 00 00 |false...........|
00000050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
00000080 00 00 00 00 75 6e 6e 61 6d 65 64 00 00 00 00 00 |....unnamed.....|
00000090 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
000000a0 00 00 00 00 0a 3c 19 d3 0f d4 a1 34 7a 58 76 6d |.....<.....4zXvm|
000000b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
00000120 00 00 00 00 00 00 00 00 00 00 00 00 |............|
0000012c

Unless I missed something, they are both the same.

Yes, the kernel is LBA48 aware. The 2.5" drive is an 80GB, though, so it doesn't really matter.

I wonder if maybe the laptop drive is not powering up fast enough to be seen by the tivo for booting. Maybe some powersave mode or something. There is a thread HERE that goes over some of the information about using the prom menu to boot the Tivo. From your output (1st post #4) it looks like you are getting the prom menu. Now that you have the password set try using the prom menu to boot after a min. or two to make sure the 2.5" drive is all the way active.

I will give that a try when I get a chance; probably tomorrow.

Thank you everyone for the attention and suggestions. Hopefully we can get this figured out!

[kernaltao]

SUCCESS! Well, partial success, anyway. I was able to boot the Tivo from the 2.5" drive through the prom menu. Here is the serial output:

read_sector got timeout
autoboot failed to read boot sector
Initializing USB ethernet
Device on dev=13 fnc=0 port=0
ASIX on dev=13 fnc=0 port=0
is ASIX......... full duplex
USB's mac address 0:10:60:84:cc:c5
USB ethernet initialized
Sent 0th bootp request.
Sent 1th bootp request.
Sent 2th bootp request.
Sent 3th bootp request.
Sent 4th bootp request.
Sent 5th bootp request.
Sent 6th bootp request.


read_sector got timeout
autoboot failed to read boot sector
Initializing USB ethernet
init there is no device
Ram size = 64
Service number is 3810000E03649A1.
What is password? pw
Build target = TiVo/mips/brcm/rel
Build version = 2.5
reset -
color_bars -
msw - [ -32 | -16 | -8 ] <address> <value>
msr - [ -32 | -16 | -8 ] <address>
help -
param - [ <new boot args> ]
netboot - [ -skip ] [ -f <file> ] [ <boot string> ]
boot - [ -skip ] [ -3 | -6 ] [ <boot string> ]
ememtest -
identify -
What? boot -3
Attempting to disk load partition 3
3900
3800
3700
3600
3500
3400
3300
3200
3100
3000
2900
2800
2700
2600
2500
2400
2300
2200
2100
2000
1900
1800
1700
1600
1500
1400
1300
1200
1100
1000
900
800
700
600
500
400
300
200
100

Kernel signed by 'Kernel release key'
Hashing kernel... done
Checking signature... done.
Signed, valid for release
CPU revision is: 00005430
FPU revision is: 00005410
Primary instruction cache 32kb, linesize 32 bytes.
Primary data cache 32kb, linesize 32 bytes.
Linux version 2.4.20 (build@buildmaster5) (gcc version 3.0) #22 Fri Feb 20 18:19:25 PST 2004
Determined physical RAM map:
memory: 04000000 @ 00000000 (usable)
On node 0 totalpages: 16384
zone(0): 16384 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line: root=/dev/hda4 dsscon=true console=2,115200 upgradesoftware=false
Monotonic time calibrated: 81.00 counts per usec
Calibrating delay loop... 161.79 BogoMIPS
Contiguous region 1: 8388608 bytes @ address 0x80d00000
Contiguous region 2: 1048576 bytes @ address 0x81500000
Contiguous region 8: 10485760 bytes @ address 0x81600000
Contiguous region of 19922944 bytes total reserved at 0x80d00000.
Memory: 43820k/65536k available (1222k kernel code, 21716k reserved, 81k data, 64k init, 0k highmem)
Dentry cache hash table entries: 8192 (order: 4, 65536 bytes)
Inode cache hash table entries: 4096 (order: 3, 32768 bytes)
Mount-cache hash table entries: 1024 (order: 1, 8192 bytes)
Buffer-cache hash table entries: 4096 (order: 2, 16384 bytes)
Page-cache hash table entries: 16384 (order: 4, 65536 bytes)
Checking for 'wait' instruction... unavailable.
POSIX conformance testing by UNIFIX
PCI: Probing PCI hardware
ttyS00 at iomem 0xb4100100 (irq = 79) is a 16550A
ttyS00 at port 0xbc010000 (irq = 133) is a unknown
ttyS00 at iomem 0xb4100140 (irq = 81) is a 16550A
ttyS00 at iomem 0xb4100120 (irq = 80) is a 16550A
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
Starting kswapd
Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI enabled
ttyS00 at 0xb4100100 (irq = 79) is a 16550A
ttyS01 at 0xbc010000 (irq = 133) is a unknown
ttyS02 at 0xb4100140 (irq = 81) is a 16550A
ttyS03 at 0xb4100120 (irq = 80) is a 16550A
Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
hda: HTS541080G9AT00, ATA DISK drive
ide0 at 0x400-0x407,0x438 on irq 87
hda: 156301488 sectors (80026 MB) w/7539KiB Cache, CHS=9729/255/63
Partition check:
hda: [mac] hda1 hda2 hda3 hda4 hda5 hda6 hda7 hda8 hda9 hda10 hda11 hda12 hda13 hda14
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
PPP generic driver version 2.4.2
PPP Deflate Compression module registered
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 4096 bind 8192)
ip_conntrack version 2.1 (512 buckets, 4096 max) - 152 bytes per conntrack
ip_tables: (C) 2000-2002 Netfilter core team
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 64k freed
Starting rc.sysinit
Running boot Stage A_PreKickstart scripts
Scanning for configuration files
starting test.conf
starting /init/*.init
/etc/rc.d/rc.sysinit: /init/*.init: No such file or directory
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
usb.c: starting integrated EHCI driver
ehci_hcd 00:0d.2: PCI device 1033:00e0
ehci_hcd 00:0d.2: irq 6, pci mem b4002000
usb.c: new USB bus registered, assigned bus number 1
PCI: 00:0d.2 PCI cache line size set incorrectly (0 bytes) by BIOS/FW, correcting to 32
ehci_hcd 00:0d.2: USB 2.0 enabled, EHCI 0.95, driver 2003-Dec-29/2.4
hub.c: USB hub found
hub.c: 5 ports detected
usb.c: EHCI initialization succeeded
usb.c: registered new driver usbnet
usb-ohci.c: USB OHCI at membase 0xb4000000, IRQ 5
usb-ohci.c: usb-00:0d.0, PCI device 1033:0035
usb.c: new USB bus registered, assigned bus number 2
hub.c: USB hub found
hub.c: 3 ports detected
usb-ohci.c: USB OHCI at membase 0xb4001000, IRQ 3
usb-ohci.c: usb-00:0d.1, PCI device 1033:0035
usb.c: new USB bus registered, assigned bus number 3
hub.c: USB hub found
hub.c: 2 ports detected
Invoking startup scripts for:
platform 'trinity'
implementation 'Series2'
implementer 'TiVo'
Releasing /initrd and clearing ramdisk, if they exist
warning: can't open /var/mtab: No such file or directory
umount: /initrd: not mounted
Activating swap partitions
Adding Swap: 65532k swap-space (priority -1)
Loading core system drivers
Parallel modem driver loaded, 1 ports starting at /dev/ttyS1
Loading ircatch
Found rev 'F' Si2433 modem on /dev/cua1
Checking for Kickstart panic signal
Running boot Stage B_PostKickstart scripts
Cleanup /dev/hda9 pass 1
ext2fs_check_if_mount: No such file or directory while determining whether /dev/hda9 is mounted.
/dev/hda9 was not cleanly unmounted, check forced.
Inode 6152, i_blocks wrong 132 (counted=130). Set i_blocks to counted? yes
Inode 6159, i_blocks wrong 52 (counted=40). Set i_blocks to counted? yes
Inode 6156, i_blocks wrong 622 (counted=614). Set i_blocks to counted? yes
Inode 16391, i_blocks wrong 16 (counted=2). Set i_blocks to counted? yes
Fix summary information? yes
/dev/hda9: 273/32768 files (4.8% non-contiguous), 12067/131072 blocks
Cleanup /dev/hda9 pass 2
ext2fs_check_if_mount: No such file or directory while determining whether /dev/hda9 is mounted.
/dev/hda9: clean, 273/32768 files, 12067/131072 blocks
/dev/hda9 is clean after pass 2
Mounting /var
/dev/hda9 on /var type ext2 (rw)
Cleaning up files in /var
Checking space in /var
Mounting initial environment
Starting logging daemons
Found Silicon Labs "Si2433" modem, rev F, skipping modem patch
Scanning for phase1 repair scripts
Running boot Stage C_MediaInitialization scripts
Loading input section drivers
cobra module was successfully installed, LNBPA 0x10 LNBPB 0x16
Loading output section drivers
Splash the screen
Running boot Stage D_PreMfs scripts
Remote control is TIVO
MFS partition on /dev/hda10
Loading Trinity dssapp
Look for debug board
/tvbin/dssappAV: DSS Interface Version 1.24, compiled on Nov 12 2004
Loading irblast
Loading ideturbo
Loading fan
Loading therm
Loading TvBus router
Updating system clock
Time set to: Mon Mar 27 13:39:09 2006
Enabling local route
Setting TCP keepalive parameters
Checking for additional disk
Start fan control
First temperature parameters set:
Terminal temp: 71
Critical temp: 62
Logging temp: 60
Target temp: 50
Lowest fan speed: 7
/tvbin/fancontrol is running in the background.
Starting TvLauncher
PokeFirewallPort: Poking hole through firewall at port 2191, protocol tcp
iptables: No chain/target/match by that name
Waiting for launcher to start.
Launcher is running.
Scanning for phase2 repair scripts
Running boot Stage E_PreApplication scripts
Checking for database conversions
No upgrade to load
Not upgrading software
Scanning for phase3 repair scripts
Running boot Stage F_ApplicationLaunch scripts
Starting Services.
Microcode version is TiVo!
Found hpk front panel model 1
PokeFirewallPort: Poking hole through firewall at port 2190, protocol udp
iptables: No chain/target/match by that name
PokeFirewallPort: Poking hole through firewall at port 2190, protocol tcp
iptables: No chain/target/match by that name
using driver frame iter
ApgLogFrequency( 0 sec )
Finished creating ApgDriverFrameIter
Using a smartSorter!
Unable to preload cache! err = errNmNameNotFound
Calling ReadStream()s
....started status session
Initialize with 2 live caches
AddInputSection 1
AddInputSection 2
TvMomMediaSwitchSource::DoSetup()
TvMomMediaSwitchSource::DoSetup()
AddInputSection 3
ApgManager Transition from state INIT to BOOT
....sending Booting event
....started status session
iptables: No chain/target/match by that name
Scanning for phase4 repair scripts
Running boot Stage G_PostApplication scripts
declare -x DEBUG_BOARD="false"
declare -x EMERGENCY_REINSTALL="0"
declare -x HDA_ID="MP288BXBGBRHXE"
declare -x HDB_ID="Unknown"
declare -x HOME="/"
declare -x HOSTNAME="(none)"
declare -x HOSTTYPE="i686"
declare -x IrdSerialNumber="533649A1"
declare -x LD_LIBRARY_PATH="/lib"
declare -x MACHTYPE="i686-pc-linux-gnu"
declare -x MFS_DEVICE="/dev/hda10"
declare -x MODEM_DEVICE="/dev/cua1"
declare -x MODEM_REV="F"
declare -x MODEM_TYPE="Si2433"
declare -x OSTYPE="linux-gnu"
declare -x PATH="/bin:/sbin:/tvbin"
declare -x PROMVERSION="
TiVo/mips/brcm/rel version 2.5"
declare -x PWD="/var/tmp"
declare -x SHELL="/bin/sh"
declare -x SHLVL="2"
declare -x SerialNumber="3810000E03649A1"
declare -x SwSystem="6.2-01-2"
declare -x TERM="linux"
declare -x TIVO_REMOTE="TIVO"
declare -x TIVO_ROOT=""
declare -x TV_STD="NTSC"
declare -x dsscon="true"
declare -x root="/dev/hda4"
declare -x upgradesoftware="false"
declare -x varpartition="/dev/hda9"
/etc/rc.d/rc.sysinit.author: /busybox/fakecall.tcl: Permission denied
rc.sysinit is complete
ApgManager Transition from state BOOT to ACQUIRE_MARKER

I wouldn't get the prom password prompt unless I disconnected the USB network adapter. When the adapter is present, the TiVo attempts to boot to the network via a bootp server (see the first attempt in the serial output above). This would be quite an interesting endeavor: to investigate how to setup a bootp server that would boot the TiVo without a hard drive! I would imagine that you wouldn't have as quick access to the recordings since they would have to be transferred over the network, but it would be fun to try it out! The TiVo would certainly be quiter (probably silent!) and run cooler. Well, that's for a separate thread.

Anyway, as to the problem at hand. It seems that you were right, fantmn, about the drive not spinning up quickly enough. Do you know how to introduce a delay or increase the autoboot/read_sector timeout time? I will do some searches to see if anything comes up. Thanks for the help; we're almost there!

[kernaltao]

Well, our assumption that the drive is not spinning up fast enough is incorrect. I came to this conclusion by doing the following:

1. Connect power cable of 2.5" drive to power supply of a second Tivo unit
2. Connect IDE of 2.5" drive to primary unit
3. Apply power to second Tivo unit so that 2.5" drive powers up
4. Apply power to primary unit to boot from 2.5" drive that has already spun up
5. Result: the same serial output (#4 of my original post)

Therefore, it has to do with how the unit is attempting to boot. When I enter the prom menu and issue the command boot -3, it boots just fine. Is there a way to permanently modify the boot loader to tell it to boot -3?

Any other ideas?

[fantmn]

The drive may be looking for a signal on the IDE cable (from the primary Tivo) before it starts. Can you hear / feel it spinning when the power is applied? Just another idea. I suspect that you may be in for a prom mod to make this happen. Remove, socket, program, the whole deal. There might be a way to trick the drive into spinning up sooner by jumpering some pins or something. I think some googleing for info about how 2.5" laptop drives power up might be in order.

[kernaltao]

The drive may be looking for a signal on the IDE cable (from the primary Tivo) before it starts. Can you hear / feel it spinning when the power is applied? Just another idea. I suspect that you may be in for a prom mod to make this happen. Remove, socket, program, the whole deal. There might be a way to trick the drive into spinning up sooner by jumpering some pins or something. I think some googleing for info about how 2.5" laptop drives power up might be in order.

Yes, the drive has definitely spun up. I can hear it, and if I touch the drive, I can feel it spinning.

I think you are right about the prom mod. I don't think I am up for that, though. Looks like I will have to scrap this project. I'm so frustrated that I couldn't get it to work, though! Thanks again for all your help. If you think of anything else, please go ahead and post it.

Kernaltao

[ocntscha]

Well, our assumption that the drive is not spinning up fast enough is incorrect. I came to this conclusion by doing the following:

1. Connect power cable of 2.5" drive to power supply of a second Tivo unit
2. Connect IDE of 2.5" drive to primary unit
3. Apply power to second Tivo unit so that 2.5" drive powers up
4. Apply power to primary unit to boot from 2.5" drive that has already spun up
5. Result: the same serial output (#4 of my original post)

Therefore, it has to do with how the unit is attempting to boot. When I enter the prom menu and issue the command boot -3, it boots just fine. Is there a way to permanently modify the boot loader to tell it to boot -3?

Any other ideas?Here's a stab in the dark, how about getting this feature tool V2.0 (http://www.hitachigst.com/hdd/support/download.htm) from Hitachi (about 2/3 of the way down the page) and horsing around with it. A few options it lets you set look to me like they could possibly have a bearing, Change Advanced Power Mode, Switch the Ultra DMA mode, Enable or disable the read-ahead or write cache.

[kernaltao]

Here's a stab in the dark, how about getting this feature tool V2.0 (http://www.hitachigst.com/hdd/support/download.htm) from Hitachi (about 2/3 of the way down the page) and horsing around with it. A few options it lets you set look to me like they could possibly have a bearing, Change Advanced Power Mode, Switch the Ultra DMA mode, Enable or disable the read-ahead or write cache.

Already ahead of you! I tried that yesterday. I tried changing some of the features, but it didn't help. Each time, I would change one feature and then try to boot the drive in the TiVo. None of the features had to do with spinning up the drive early or not waiting for a signal on the IDE channel. If it truly is waiting for an IDE signal, I wonder if there is a 2.5" to 3.5" adapter that would send a signal to make the drive spin up properly?

[fantmn]

I have a 2.5 to 3.5 adapter as well. I will try to find some time to give it a try as well. I have a busy schedule the rest of this week and all of next week so I may not be able to work it in. My adapter is a generic one I got from a friend, so I do not expect any different results, but I'll give it a try anyway (I might be able to work it in over the weekend). I'll have to look at my drive and see what brand it is. I think it is a Hitachi travelstar as well. There is some interesting reading here (http://www.interfacebus.com/Design_Connector_IDE.html)as well about IDE (ATA) interfaces. When I googled I saw someone over at TCF seems to have gotten this working. I saw you post as well. So I guess we are missing something.

[matt1981m]

that would be awesome to use a laptop drive... the only suggestion i have is to use a hard drive caddy to keep the HD from shorting out... i think that the antistatic bag may be preventing the drive from booting..... you can get a HD caddy off of ebay for a IBM HD or any brand for that matter pretty cheap....

i would use the following command to load the image on the drive...
dd if=/dev/hdX of=/dev/hdY bs=1024k

in this command replace X with the location of your working 3.5 tivo drive and Y with your 2.5 laptop drive.... i.e. if the tivo drive is Secondary Master, and the destination 2.5 drive was set as the Secondary Slave the script would look like this

dd if=/dev/hdc of=/dev/hdd bs=1024k

.... i know you probably would have figured out the drive assignments but there might have been someone else reviewing this post that may have been clueless......

also one thing i want to point out is that this will copy the exact image over... if you are going from a 40GB to an 80GB drive you will only be able to use 40GB of the drive with this setup... but this WILL allow you to test your setup to see if the HD will work as desired....

[kernaltao]

that would be awesome to use a laptop drive... the only suggestion i have is to use a hard drive caddy to keep the HD from shorting out... i think that the antistatic bag may be preventing the drive from booting..... you can get a HD caddy off of ebay for a IBM HD or any brand for that matter pretty cheap....

i would use the following command to load the image on the drive...
dd if=/dev/hdX of=/dev/hdY bs=1024k

in this command replace X with the location of your working 3.5 tivo drive and Y with your 2.5 laptop drive.... i.e. if the tivo drive is Secondary Master, and the destination 2.5 drive was set as the Secondary Slave the script would look like this

dd if=/dev/hdc of=/dev/hdd bs=1024k

.... i know you probably would have figured out the drive assignments but there might have been someone else reviewing this post that may have been clueless......

also one thing i want to point out is that this will copy the exact image over... if you are going from a 40GB to an 80GB drive you will only be able to use 40GB of the drive with this setup... but this WILL allow you to test your setup to see if the HD will work as desired....


I doubt that the anti-static bag is shorting out the drive. I boot my TiVo for testing like this all the time with a 3.5" drive.

EDIT: During testing, I did use another drive that was in a caddy. As I thought, no difference.

I already tried dd'ing a 80GB 3.5" drive to the 80GB 2.5" drive. It didn't work. If you read all of the posts, you will see that I was able to get it to boot the TiVo through the prom command. Therefore, the image on the drive is correct. It has to be that the drive isn't spinning up completely in time for the autoboot timeout. Our best guess is that the drive is waiting for a signal on the IDE channel before spinning up completely, but the TiVo expects to have a 'ready' drive immediately. If there was some way to induce a delay or increase the timeout, it would probably work, but that would entail modifying the prom.

[matt1981m]

I doubt that the anti-static bag is shorting out the drive. I boot my TiVo for testing like this all the time with a 3.5" drive.

EDIT: During testing, I did use another drive that was in a caddy. As I thought, no difference.

I already tried dd'ing a 80GB 3.5" drive to the 80GB 2.5" drive. It didn't work. If you read all of the posts, you will see that I was able to get it to boot the TiVo through the prom command. Therefore, the image on the drive is correct. It has to be that the drive isn't spinning up completely in time for the autoboot timeout. Our best guess is that the drive is waiting for a signal on the IDE channel before spinning up completely, but the TiVo expects to have a 'ready' drive immediately. If there was some way to induce a delay or increase the timeout, it would probably work, but that would entail modifying the prom.
sorry to hear it didnt work... i have used an anti static bag as a "buffer" between components and had them short out because of it.... that is why i thought of that.... i see the post you are talking about... somehow i must have skipped over it...

[ralphyoung]

I'm having the same trouble with a 2.5" 120g Toshiba. I've read positive results from others. Perhaps the issue is unique to the vendor?

[ralphyoung]

kernaltao resonded to say he tried both Seagate and Samung laptop drives and they both failed to boot. If anyone has had success please post your model number. Thanks!!!

[ralphyoung]

Success!
I'm not sure if it was the change of software or hardware but my 2.5" Toshiba drive works perfectly with Series1 hardware and software (GXCEB0T). If others wanting to make Series2 DirecTiVo work try loading a modern Standalone OS. That might help.

[claibinis]

I am speculating a little here, but this may be a possibility. From what I understand the 2.5" drives architecture is a little more advanced than 3.5" drives to allow things like power throttling and also hard drive passwords. The hard drive password may be the issue here. It is written in the maintenance cylinder on the drive, so following the ATA specs the drives is powered on by either having a laptop power up, or wakeup from a sleep mode. The first thing the specs tell the drive to do is read the maintenance cylinder to check for a password (whether or not one exists does not matter). If TiVo is not strictly adhering to ATA standards and implementing the whole feature set, this primary function may be left out. Which would not allow the drive to be read, due to the layout of the drive existing in the maintenance cylinder as well.