PDA

View Full Version : How do I fix a file I can't access?


Shadal
03-06-2004, 07:37 PM
I screwed up my rc.sysinit.author file. Now my USB ports don't have any power it seems, so I can't get an ethernet connection established. I was thinking to try a serial connection but reading around it seems that bash is enabled via rc.sysinit.author so i'm assuming I won't get anywhere with a serial connection. I've pulled the hard drive and mounted it using the mfstools CD but in the rc.d directory the file's not listed and if I type "edit rc.sysinit.author" figuring maby it's hidden or something it doesn't come up..

Yelp!
Thx

SR712
03-06-2004, 08:26 PM
You are looking in the /etc/rc.d/ of the CD drive. Remember, after you mount the TiVo disk, you have to go to the /etc/rc.d/ of the TiVo drive. Ie... if you mounted it as /mnt/tivo, then you need to change directory to /mnt/tivo/etc/rc.d/ .

Shadal
03-06-2004, 08:28 PM
i typed:

mkdir /mnt/tivo
mount /dev/hdc4 /mnt/tivo
cd /mnt/tivo/etc/rc.d
all that was showing was rc.sysinit and one other file, no rc.sysinit.author. and a lot of directorys in he root folder were missing also.

i also tried
mount /dev/hdc9 /mnt/tivo (hdc9 was the only other way it would mount)
that showd more folders in the root directory, but shows most of them were empty except for the 'log' folder.

SR712
03-06-2004, 08:33 PM
Try /dev/hdc7/

tytyty
03-06-2004, 08:33 PM
first do a mount /dev/hdc4 /mnt/tivo
then ls /mnt/tivo
if you do not see an tvbin dir you are on wrong mountpoint

umount /mnt/tivo
mount /dev/hdc7 /mnt/tivo
ls /mnt/tivo is tvbin there if yes
cd /mnt/tivo/etc/rc.d
ls hopefully rc.sysinit.author is there

proceed with repairs

Shadal
03-06-2004, 08:35 PM
hdc7 wouldn't mount.. think it said i needed to specify a filesystem type

SR712
03-06-2004, 08:55 PM
Try a different boot CD, like 25xtreme.

Shadal
03-06-2004, 09:18 PM
I GOT IN!
I dono what the heck I did yesterday when I tried it, but i just pulled the drive and tried mounting hdc7 and it worked.. I editied the file and it had a blue M at the end of each line. I'm assuming that's what the problem was, i hope.. cuz' what originally happened is i didn't use a dostounix converter when i edited the file originally and transfered it over. I just removed all the blue M's and put the drive back in, waiting to see if my ethernet adapter powers on...

doesn't look like it.. the rest of the file looks alright, what else would I need to fix?

captain_video
03-06-2004, 10:17 PM
Did you make the file executable using chmod 755 after you transferred it? If not your hacks will never be called at bootup and therefore won't work.

Shadal
03-06-2004, 10:28 PM
ok, now everything is 100 times worse...

I broke down are just restored the backup i created when I first got the system. Now right after it says "powering up, please wait" i just get a black screen with 7 lines of small white dots running down the left side of the screen, and it just sits there... Now it won't boot at all..

Why is this so hard!! *cries*

It's a series 2 DSR704 and I followed all the hinsdale instructions exactly for series 2 tivos... So If my original backup was bad.. And i've already overwritten the original HD, What are my options now?

SR712
03-06-2004, 11:08 PM
If this is a series 2, and you had a bash prompt and networking... then it had to be hacked with something like sleeper's iso. Did you buy this unit already hacked or did you do it yourself? BTW, Hindsdale's Backup will not fully backup a series 2 with all the hacks. There are threads on that here. There are additional processes you will have to do, and they all are here in various threads. If you need another backup, you'll have to go find it on a file-sharing network.

PlainBill
03-06-2004, 11:11 PM
ok, now everything is 100 times worse...

I broke down are just restored the backup i created when I first got the system. Now right after it says "powering up, please wait" i just get a black screen with 7 lines of small white dots running down the left side of the screen, and it just sits there... Now it won't boot at all..

Why is this so hard!! *cries*

It's a series 2 DSR704 and I followed all the hinsdale instructions exactly for series 2 tivos... So If my original backup was bad.. And i've already overwritten the original HD, What are my options now?

I'll skip the lecture. Take a look at the Image begging thread. Or just go to www.emule-project.net. download the emule client, and search for 3.1.1b.

On second thought, there is a reason we always say "Do NOT alter your original drive."

PlainBill

dt2004
04-04-2004, 01:56 AM
ok, now everything is 100 times worse...

I broke down are just restored the backup i created when I first got the system. Now right after it says "powering up, please wait" i just get a black screen with 7 lines of small white dots running down the left side of the screen, and it just sits there... Now it won't boot at all..

Why is this so hard!! *cries*

Did you make sure the IDE cable is plugged in on both sides securely?

Dustin

hart316
04-04-2004, 03:32 AM
I screwed up my rc.sysinit.author file.


Earlier today I was toying with my tivo, trying to automate mfs_ftp & tserver_mfs7 in my rc.sysint.author also. I basically did one test... it worked, then applied my second test, (using textpad, it works great), I transferred it over to tivo and rebooted. I walked away while it was rebooting and immediately said "OH S*@$!!!" I forgot to chmod 755. I monte'd my SD-DVR40, used mfstools bootdisk to backup/restore, but never messed with my "tivo" drive in a pc, besides restoring and backing up.

I searched and searched on how to do this and I found this post, along with others. I too was getting errors when I tried to:

mount /dev/hdc4 /mnt/tivo
or
mount /dev/hdc7 /mnt/tivo

(I was using mfstools bootdisk)


I was fustrated...I tried 25xtreme (whatever that is...as I still am not sure),but I must have had a bad .iso as it would not let me burn it to CD.


So I tried burning the mfstools.iso (CD version), burnt the CD, booted it up

followed tytyty's suggestions and IT WORKED!!!!


I guess the mfstools bootdisk doesn't work for this....now I know!!!

I restored my rc.sysinit.author from my rc.sysinit.author.bak file; booted up; transferred my "new" rc.sysinit.author... and did the chmod 755 OF COURSE!!!!!!

Now I am a happy man as all is well. Now I don't have to disconnect the tivo, bring it to my cpu room and connect to my cpu with bash/ftp to start tserver and mfs_ftp.

I do have a LONG cable running from my living room to my cpu room, who cares right... that is until new wireless drivers are available!


MY POINT IS...I had the same problem, I knew someone already on this forum had done the same thing already.. and the next guy will too...but I knew better than to just post for help. (that's how you learn...right!)


That is why EVERYONE suggests to read and search the posts before asking for help!!


THANKS guys!!!

Shadal
04-04-2004, 10:34 AM
well mine's all fixed.. I ended up sending it out to the guy that set it up for me, had him restore it..

i ended up giving up after a while..

Thanks for the suggestions from all of you guys!

JohnSorTivo
04-04-2004, 11:48 AM
I guess the mfstools bootdisk doesn't work for this....now I know!!!
Hmm... The mfstools boot disk has worked flawlessly for me when needing to boot to and mount my tivo drives in emergencies.

At any rate, I'm wondering why people just don't modify their files directly on the unit by telneting in, rather than FTPing back and forth, which makes it quite easy to forget to chmod it each time.

I know 'vi' may be a bit overwhelming at first, but after a day or so of tooling with it, it's pretty straight forward and powerful. You can also install 'joe', which is even easier.

Learning and using one of these editing programs will save you a lot of time and headaches in the long run.