PDA

View Full Version : 3.1.5f upgrade to 6.3c fails - installSw.itcl


mclendon
03-03-2007, 10:17 PM
Running an HR10-250 with 3.1.5f works fine with hacks.

Now attempting to upgrade to 6.3c-01-2-357 - so I verified I had 6.3c on disk, modified my installSw.itcl, ran installSw.itcl 6.3c-01-2-357 and received the following output less a number of lines preceding that were informational:



Installing module kernel-Series2
Building basic filesystem skeleton on /install


Checking /install/etc/fstab

newroot is 4, leaving fstab alone
Creating symlinks for /install/etc files
Dismounting /install and checking its integrity

e2fsck: Only one the options -p/-a, -n or -y may be specified.
while executing
"exec e2fsck -p -f -n $dev$newroot"
(file "/var/utils/updateroot" line 169)
child process exited abnormally
while executing
"exec /var/utils/updateroot /dev/hda /install /var/packages $name >&@ stdout"
(object "::inst" method "::Installer::installSoftware" body line 46)
invoked from within
"inst installSoftware $name $Inc::TC_INSTALL_DIR "
(file "./installSw.itcl" line 182)
Tivo:/tvbin>

================

Looks like e2fsck in updateroot is the problem so I checked my e2fsck version as follows:

Here is the e2fsck version in my /bin directory (symbolic link to busybox):



Tivo:/> e2fsck
BusyBox v1.2.2 (2006.12.20-20:51+0000) multi-call binary

Usage: e2fsck [-panyrcdfvstDFSV] [-b superblock] [-B blocksize] [-I inode_buffer
_blocks] [-P process_inode_size] [-l|-L bad_blocks_file] [-C fd] [-j external_jo
urnal] [-E extended-options] device

Check a Linux ext2/ext3 file system.

Options:
-p Automatic repair (no questions)
-n Make no changes to the filesystem
-y Assume 'yes' to all questions
-c Check for bad blocks and add them to the badblock list
-f Force checking even if filesystem is marked clean
-v Be verbose
-b superblock Use alternative superblock
-B blocksize Force blocksize when looking for superblock
-j journal Set location of the external journal
-l file Add to badblocks list
-L file Set badblocks list



I would appreciate any pointers to get squared away here. Tnx - M

Jamie
03-03-2007, 10:31 PM
I would appreciate any pointers to get squared away here. Tnx - MWhat the heck are you doing with busybox installed in /bin? And why are you using a busybox e2fsck anyway?

In any case, the standard e2fsck is in /sbin, so it is probably still there. If you just make sure you have /sbin on your path in front of /bin, you may find that installSw.itcl will run okay.

mclendon
03-04-2007, 10:45 AM
Thanks Jaime. I unlinked the Busybox e2fsck in /bin (careless of me to install Busybox there) and the installSw.itcl script ran fine using the /bin version.