PLEASE HELP! hda4 Won't Mount!

[revx]

I have a problem with my SA Series 2 (24004A) I am attemptign to do an inplace upgrade from 7.2.2 to 7.2.2b. I got tired of the daily reboots... all seemed to be going ok... I dd'd the new new kernel and went to mount the 'new' filesystem (my active was on 7) and I got this:

bash-2.02# mount /dev/hda4 /mnt
mount: you must specify the filesystem type

so i tried this:

bash-2.02# mount -t ext2 /dev/hda4 /mnt
mount: wrong fs type, bad option, bad superblock on /dev/hda4,
or too many mounted file systems

now i'm very confused!

a quick bootpage -p
returns:
No device name given, assuming /dev/hda
root=/dev/hda4 dsscon=true console=2,115200 upgradesoftware=false

telling me my upgrade seems to have gone ok and now it'll boot off of partition 4... Any ideas???

Please HELP!
thx!
revx

[ScanMan]

I assume this was done after you ran the edited installSW.itcl? When it was done, did you get the "release" message - "Congratulations, you have received a tivo update..." indicating a successful install?

What is the output of the "mount" command?
You're not booted into a monte kernel, right?

Also, what is the output of "pdisk -l"? Is it showing /dev/hda4 as an Ext2 partition?

[revx]

I assume this was done after you ran the edited installSW.itcl? When it was done, did you get the "release" message - "Congratulations, you have received a tivo update..." indicating a successful install?
yes, this is after I ran my editied "instalSw.itcl" script. I have NOT rebooted, but I got the "Attempting reboot..." after the script ran and then exited with an "exit 0"

What is the output of the "mount" command?
bash-2.02# mount
/dev/hda7 on / type ext2 (rw)
/dev/hda9 on /var type ext2 (rw)
/proc on /proc type proc (rw)

You're not booted into a monte kernel, right?
No... killhdinitrd'd 3.1.5 kernel from the $5 pvrupgrade disk.

Also, what is the output of "pdisk -l"? Is it showing /dev/hda4 as an Ext2 partition?
Yes, hda4 is showing as an ext2 partition...

bash-2.02# pdisk -l
pdisk: can't open file '/dev/sda' (No such device or address)
pdisk: can't open file '/dev/sdb' (No such device or address)
pdisk: can't open file '/dev/sdc' (No such device or address)

Partition map (with 512 byte blocks) on '/dev/hda'
#: type name length base ( size )
1: Apple_partition_map Apple 63 @ 1
2: Image Bootstrap 1 4096 @ 76181568 ( 2.0M)
3: Image Kernel 1 4096 @ 76185664 ( 2.0M)
4: Ext2 Root 1 262144 @ 76189760 (128.0M)
5: Image Bootstrap 2 1 @ 76451904
6: Image Kernel 2 8192 @ 76451905 ( 4.0M)
7: Ext2 Root 2 262144 @ 76460097 (128.0M)
8: Swap Linux swap 260096 @ 76722241 (127.0M)
9: Ext2 /var 262144 @ 76982337 (128.0M)
10: MFS MFS application region 524288 @ 77244481 (256.0M)
11: MFS MFS media region 33190912 @ 42990656 ( 15.8G)
12: MFS Second MFS application region 524288 @ 77768769 (256.0M)
13: MFS Second MFS media region 42990592 @ 64 ( 20.5G)
14: MFS New MFS Application 1024 @ 78293057
15: MFS New MFS Media 161824768 @ 78294081 ( 77.2G)
16: Apple_Free Extra 2879 @ 240118849 ( 1.4M)

Partition map (with 512 byte blocks) on '/dev/hdb'
#: type name length base ( size )
1: Apple_partition_map Apple 63 @ 1
2: MFS New MFS Application 1024 @ 64
3: MFS New MFS Media 240115712 @ 1088 (114.5G)
4: Apple_Free Extra 4928 @ 240116800 ( 2.4M)

pdisk: can't open file '/dev/scd0' (No such device or address)
pdisk: can't open file '/dev/scd1' (No such device or address)
pdisk: can't open file '/dev/scd2' (No such device or address)
pdisk: can't open file '/dev/scd3' (No such device or address)

Thank-you for the quick reply... am i in trouble here??

[ScanMan]

Everything looks OK, but I wouldn't reboot as is. Why do you have /dev/hda7 mounted (rw) try and umount and remount as (ro)
mount -o remount,ro /
Then try to mount /dev/hda4 again.

If you don't get anywhere, I might write new bootpage params changing it back to /dev/hda7 and flip the bootpage back to 6; just in case tivo reboots on you in the middle of the night...

[ocntscha]

Partition map (with 512 byte blocks) on '/dev/hda'
#: type name length base ( size )
1: Apple_partition_map Apple 63 @ 1
2: Image Bootstrap 1 4096 @ 76181568 ( 2.0M)
3: Image Kernel 1 4096 @ 76185664 ( 2.0M)
4: Ext2 Root 1 262144 @ 76189760 (128.0M)
5: Image Bootstrap 2 1 @ 76451904
6: Image Kernel 2 8192 @ 76451905 ( 4.0M)
7: Ext2 Root 2 262144 @ 76460097 (128.0M)
8: Swap Linux swap 260096 @ 76722241 (127.0M)
9: Ext2 /var 262144 @ 76982337 (128.0M)
10: MFS MFS application region 524288 @ 77244481 (256.0M)
11: MFS MFS media region 33190912 @ 42990656 ( 15.8G)
12: MFS Second MFS application region 524288 @ 77768769 (256.0M)
13: MFS Second MFS media region 42990592 @ 64 ( 20.5G)
14: MFS New MFS Application 1024 @ 78293057
15: MFS New MFS Media 161824768 @ 78294081 ( 77.2G)
16: Apple_Free Extra 2879 @ 240118849 ( 1.4M)

What exactly did you do when you "dd'd the new kernel"?

If you perhaps did dd if=/dev/hda6 of=/dev/hda3 I think that would likely explain what your seeing. hda6 is 4 Meg and hda3 is 2Meg. So you would have overwrote the first 2 Meg of hda4.

[Jamie]

If you perhaps did dd if=/dev/hda6 of=/dev/hda3 I think that would likely explain what your seeing. hda6 is 4 Meg and hda3 is 2Meg. So you would have overwrote the first 2 Meg of hda4.Nope. Partition devices don't work like that. You can't write beyond the end of the device.

It *does* seem like hda4 got clobbered though. I'm thinking the OP might have used of=/dev/hda4 in the dd. I've done it!

[revx]

What exactly did you do when you "dd'd the new kernel"?

If you perhaps did dd if=/dev/hda6 of=/dev/hda3 I think that would likely explain what your seeing. hda6 is 4 Meg and hda3 is 2Meg. So you would have overwrote the first 2 Meg of hda4.
ok.... i think i may have (very likely) dd'd hda6. but it would have been 'dd if=vmlinux.px of=/dev/hda6'. i mis-read the directions i was following. so? what do you think? I don't see a pending reset... it's not scheduled to call in until 3pm tomorrow. ok to let it go tonight? any way to fix this without pulling the HD's?

thanks again!

[revx]

Nope. Partition devices don't work like that. You can't write beyond the end of the device.

It *does* seem like hda4 got clobbered though. I'm thinking the OP might have used of=/dev/hda4 in the dd. I've done it!
hmmm... should i re-write my bootpage? would that even help at this point?
thx!

[Jamie]

hmmm... should i re-write my bootpage? would that even help at this point?
thx!I'd run installSW.itcl again. You might have to force it (EMERGENCY_RESINTALL?) to get it to load again. Perhaps you are right, you should flip the bootpage back first. Tread carefully (read and understand installSW.itcl) if you don't want to have to pull the drive to repair it.

[revx]

I'd run installSW.itcl again. You might have to force it (EMERGENCY_RESINTALL?) to get it to load again. Perhaps you are right, you should flip the bootpage back first. Tread carefully (read and understand installSW.itcl) if you don't want to have to pull the drive to repair it.
I flipped my bootpage back over to hda7 and tried re-running the install script... it said something to the effect that it was already run. so I issued a "echo mls /SwSystem | tivosh" and noticed that it already thinks that it's active:
Name Type FsId Date Time Size
---- ---- ---- ---- ---- ----
7.2.2-oth.01-2-140 tyDb 365385 05/08/06 22:53 844
7.2.2b-oth-01-2-140 tyDb 501912 05/08/06 22:53 868
ACTIVE tyDb 501912 05/08/06 22:53 868

FsId and Size are the same...
How would I go about doing an 'emergency_reinstall' ?

I tried re-mounting hda7 as suggested "mount -o remount,ro /" and then tried to mount hda4 again with the same results... (must specify the filesystem type).

I've got the bootpage pointed at my original partition (hda7) so I *think* it'll be ok if it reboots. I'm hoping after I choose to reboot it, I'll be able to start over?? Or am I about to get a fresh new Tivo harddrives?

Once again, thanks for all the help and suggestions. Any other ideas would be greatly appreciated.
-=reVx=-

[Jamie]

How would I go about doing an 'emergency_reinstall' ?
Read and understand the installSw.itcl script. It might be as easy as setting EMERGENCY_REINSTALL in the environment.

[ScanMan]

I've got the bootpage pointed at my original partition (hda7) so I *think* it'll be ok if it reboots. I'm hoping after I choose to reboot it, I'll be able to start over?? Or am I about to get a fresh new Tivo harddrives?
It's important to note that if you do decide to reboot, you need to reset your bootpage parameters to root=/dev/hda7 as well as flipping the bootpage to boot from /dev/hda6. Simply setting root=/dev/hda7 does not "flip" the bootpage. You may be able to just type "bootpage -f /dev/hda" or you can do it manually. Check it first with "bootpage -b /dev/hda" - that will tell you the active boot partition. Similarly, "bootpage -a /dev/hda" will show you the alternate. You can set it manually with "bootpage -B 6 /dev/hda" and "bootpage -A 3 /dev/hda" to set active and alternate respectively. Make sure both of these as well as root=/dev/hda7 are straight before you reboot. A list of bootpage options can be found here. (http://www.courtesan.com/tivo/bootpage.html)

For future reference: tivo uses two sets of partitions in booting your system and mounting the root filesystem - 3/4 and 6/7, one is active while the other is alternate. When root=/dev/hda4, the 3rd partition is the kernel that boots and the 4th partition is the root filesystem. Similarly, with the 6/7 pair. In your example if your active was originally /dev/hda7, tivo would have installed the new software in the 3/4 pair. Thus, you should have dd'd your killhdinitrd kernel into /dev/hda3 and made changes to the root filesystem at /dev/hda4 as you were trying.

[revx]

It's important to note that if you do decide to reboot, you need to reset your bootpage parameters to root=/dev/hda7 as well as flipping the bootpage to boot from /dev/hda6. Simply setting root=/dev/hda7 does not "flip" the bootpage. You may be able to just type "bootpage -f /dev/hda" or you can do it manually. Check it first with "bootpage -b /dev/hda" - that will tell you the active boot partition. Similarly, "bootpage -a /dev/hda" will show you the alternate. You can set it manually with "bootpage -B 6 /dev/hda" and "bootpage -A 3 /dev/hda" to set active and alternate respectively.
Thanks for the info and the link...

At this point I'm going to try to avoid rebooting. I'm going to verify what my bootpage is set to, if needed flip it back over to hda7 (bootpage before I started all this) and then using the tips from Jamie, edit my installSw.itcl changing the emergency flag to 1 and try to reinstall.

Does that sound about right? I'm hoping I'll be able to pull this one off... no matter how it turns out, I do have to say thanks to everybody again; this is always a learning experience and I do have fun with it. If I lose my Tivo HD's I can always start over and it is, after all, only TV. :cool:
thx!
reVx

[revx]

I updated my installSw.itcl with the Emergency_Reinstall flag set to 1... Ran it and got a slightly different response... this software is already Active.

So I verified my bootpage parameters where correct and rebooted. That was a very long "amost there message..." (not really it just felt that way) and it came back up! Not only that, but it looks like all my hacks are still there. I can telnet in and ftp responded and all looks ok. I’m assuming this is because I’m still on my original partition (6/7).

What’s got me confused now is that the Tivo is reporting the new SW version (7.2.2b-oth-01-2-140) when I go to the system information page. I verified this:

bash-2.02# echo mls /SwSystem | tivosh
Directory of /SwSystem starting at ''

Name Type FsId Date Time Size
---- ---- ---- ---- ---- ----
7.2.2-oth.01-2-140 tyDb 365385 05/08/06 22:53 844
7.2.2b-oth-01-2-140 tyDb 501912 05/08/06 22:53 868
ACTIVE tyDb 501912 05/08/06 22:53 868

I still cannot mount hda4; same error message and same info from "pdisk -l"... I also tried to mount hda3 with the same error.

I’m open for suggestions at this point... everything seems ok, but I don't think it really is. I never have copied my hacks over to the #4 partition (obviously because I can't mount it) and I’m curious why the old SW version is still in the SwSystem. I’m also wondering when the alternate partition is used… just for SW upgrades or are there other reasons?
Thx!
-=reVx=-

[ScanMan]

I’m curious why the old SW version is still in the SwSystem.
That's normal; tivo always displays the last version as well as the active.
I’m also wondering when the alternate partition is used… just for SW upgrades As far as I know, yes only for SW upgrades.

I guess the obvious question is are you sure your original root was /dev/hda7? You definitely have some weirdness going on there. I just completed a successful upgrade to 7.2.2b-oth-01-2-140 using the same process. No problems; the curious thing was I did a "pdisk -l /dev/hda" BEFORE doing anything (b/c you piqued my curiousity) and similar to you my /dev/hda3 was 2M while /dev/hda6 was 4M. It ultimately didn't matter as the 3.1.5 killhd kernel is less than 2M anyway so it took fine. Don't know how the partitions got to be different sizes. I did an MFSTools upgrade way back but nothing else. The only other thing of note is that the upgrade to 7.2.2b appears fairly minimal; it probably only took 10-15 minutes to complete upon reboot. Unlike when I upgraded from 7.2.0 to 7.2.2 it took a lot longer like 30-40 minutes.

[revx]

I guess the obvious question is are you sure your original root was /dev/hda7?
yes, i'm sure it was on hda7 before i started because i wrote it down. the upgrade process (http://www.dealdatabase.com/forum/showthread.php?t=48925) i followed referenced his as hda4, and i remember thinking i didn't want to get confused... a lot of good that did me!

The only other thing of note is that the upgrade to 7.2.2b appears fairly minimal; it probably only took 10-15 minutes to complete upon reboot.
unless it did it some time that i wasn't watching, i never saw the upgrade screen on my tivo after a reboot. maybe it did do it at 2am?? are there any system logs floating around i could look at?
thx!
revx

[ScanMan]

i never saw the upgrade screen on my tivo after a reboot.
Neither did I to tell you truth! My tivo was in another room and when I finally checked it like 10-15 later it was already at the Tivo Central screen. Since I didn't see it, do you know if the "Processing upgrade...this may take up to an hour" splash screen appeared?
are there any system logs floating around i could look at?
Yes, you can look in /var/log for the kernel log.

[Jamie]

Check the md5sum on your (stock unhacked) tivoapp. That should tell you for sure if your root partition is from 7.2.2 or 7.2.2b.
839b41d7b3cbc353a04f4e8dc7fc7b56 tivoapp-7.2.2-oth.01-2
302906e1c1ca5f194d36d75fd77f4920 tivoapp-7.2.2b-oth
I suspect you still have a root partition from 7.2.2 since you messed around with bootpage manually. The on screen version display probably comes from mfs (SwSystemName attribute in dbobj /State/ServiceConfig), but you might still be running the old tivoapp and other files from the old root partition. This *must* be the case if your hacks are still present.

You don't want to leave it in this state. If you can't figure out any other way to fix it, you can copy the root partition from a known good stock 7.2.2b image. Be sure to check /etc/fstab to make sure it matches your root partitition (that is, change /dev/hda4 to /dev/hda7 or vice versa, if necessary).

[revx]

You don't want to leave it in this state. If you can't figure out any other way to fix it, you can copy the root partition from a known good stock 7.2.2b image. Be sure to check /etc/fstab to make sure it matches your root partitition (that is, change /dev/hda4 to /dev/hda7 or vice versa, if necessary).
i know it's been a while but a thought an update was in order...

against my better judgement and the advice of Jamie and others, i left my tivo in an odd state for about 3 months. i just didn't have the time or energy to deal with it and i figured if it did crash hard i could always start over... it rebooted now and then (more than normal) but never crashed, and more importantly - i didn't lose any shows.

when i got the 7.3.1-oth-01-2-140 upgrade this week, i decited it was time to fix it, so i repeated the upgrade process; being EXTREMELY careful this time. and hey - the upgrade worked. I know have a happy 7.3.1 with KZ installed and hacks in place.

just wanted to say thanks again to everybody that helped me before. it is apprciated!
reVx