View unanswered posts    View active topics

All times are UTC - 6 hours





Post new topic Reply to topic  [ 12 posts ] 
Print view Previous topic   Next topic  
Author Message
Search for:
PostPosted: Wed Sep 12, 2007 2:11 pm 
Offline
Joined: Sun Sep 05, 2004 7:06 pm
Posts: 690
Last night I upgraded my main box from R5E50 to R5F27. The installation went fine but when I rebooted the system lilo came up with the error

"Loading LinuxEBDA is big; kernel setup stack overlaps LILO second stage. "

So I searched the forum and found this post

http://mysettopbox.tv/phpBB2/viewtopic. ... =linuxebda

So I thought why not boot the cd and see what's up

Following Cesman's post

Code:
mount  - rw /dev/hda1 /mnt/hda1
chroot /mnt/hda1
then ran lilo -v 


But the same error came up. Next, I checked the size of the files in the /boot directory on the drive but they were exactly the same size as the ones on the cd. At this time I thought it wise to get some sleep. When I booted the system this morning I get a "Eminent Smart Drive Failure Error." This made me quite uneasy but I read from TJC's post the patience is important. So I opened up the case replaced the ide cable and set the jumper on master. When I booted the system it came up so I went thru the migration. At this point I realized that something was wrong because the backend would not come up even thought I had the nic working with the weather. Hmm so that made me think maybe something with wrong with the upgrade so I ran the knoppmyth Restore. It started but it only ran for 30 seconds so I knew it it did not work. So I did some more googling on commands and came up with

Code:
cat /proc/partitions 


that showed me that my partitions were intact so that was :wink: a big releaf. Next I booted the cd and looked at the partition info. It told me that the swap partition had no lablel and that /myth partition was EXT3. I tried to mount the swap partition but it failed

Code:
mount -t ext3 /dev/hda2 /swap


it did work with

Code:
mount -t ext3 /dev/hda3 /myth


I used Xedit and I can now see all my shows in /myth/tv and /myth/pretty

At startup the system mounted
/dev/hda1 /boot

but I also need

/dev/hda2/ /swap
/dev/hda3/ /myth

So I decided that this is where I need a little assitance. What exactly is the rule of thumb in regards to the mount points and making them permanent at startup when they do not happen automatically??? Moreovever, what needs to happen with the database since the upgrade is done but it did not upgrade my schema since the partition was not mounted? Feels like the twilight zone...


Last edited by RacerX on Wed Sep 12, 2007 7:30 pm, edited 1 time in total.


Top
 Profile  
 
 Post subject:
PostPosted: Wed Sep 12, 2007 2:22 pm 
Offline
Joined: Wed Nov 16, 2005 8:55 pm
Posts: 1381
Location: Farmington, MI USA
What is the contents of your /etc/fstab?


Top
 Profile  
 
 Post subject:
PostPosted: Wed Sep 12, 2007 2:41 pm 
Offline
Joined: Sun Sep 05, 2004 7:06 pm
Posts: 690
As requested

# /etc/fstab: filesystem table.
#
# filesystem mountpoint type options dump pass
/dev/hda1 / ext3 defaults,errors=remount-ro 0 1
/dev/hda3 /dev/hda3 auto defaults,auto 0 2

proc /proc proc defaults 0 0
/dev/fd0 /floppy vfat defaults,user,noauto,showexec,umask=022 0 0
usbfs /proc/bus/usb usbfs devmode=0666 0 0
sysfs /sys sysfs defaults 0 0
tmpfs /dev/shm tmpfs defaults 0 0
/dev/cdrom /cdrom auto defaults,ro,user,noexec,noauto 0 0
# Added by KNOPPIX
/dev/hda2 none swap defaults 0 0


Top
 Profile  
 
 Post subject:
PostPosted: Wed Sep 12, 2007 2:50 pm 
Offline
Joined: Sun Sep 25, 2005 3:50 pm
Posts: 1013
Location: Los Angeles
RacerX wrote:
/dev/hda3 /dev/hda3 auto defaults,auto 0 2


I believe your 2nd reference to /dev/hda3 in this line should be /myth

_________________
Mike
My Hardware Profile


Top
 Profile  
 
 Post subject:
PostPosted: Wed Sep 12, 2007 2:57 pm 
Offline
Joined: Mon Jul 31, 2006 10:41 pm
Posts: 149
# /etc/fstab: filesystem table.
#
# filesystem mountpoint type options dump pass
...
/dev/hda3 /dev/hda3 auto defaults,auto 0 2
...

Mine shows:
/dev/hda3 /myth ext3 defaults,auto 0 2

Perhaps that would work.


Top
 Profile  
 
 Post subject:
PostPosted: Wed Sep 12, 2007 3:01 pm 
Offline
Joined: Sun Sep 05, 2004 7:06 pm
Posts: 690
Hello

"/dev/hda3 /myth ext3 defaults,auto 0 2 "

Looks good to me, but what does it say for?

/dev/hda2

Thanks for helping


Top
 Profile  
 
 Post subject:
PostPosted: Wed Sep 12, 2007 3:22 pm 
Offline
Joined: Sat Sep 02, 2006 9:17 am
Posts: 359
RacerX wrote:
Looks good to me, but what does it say for?

/dev/hda2

Code:
/dev/hda2 none swap defaults 0 0

Your mount command above wouldn't have worked, because swap space doesn't get mounted like other filesystems. -- if you were to do it by hand you would use the swapon command. If you're not sure if your swap is active use
Code:
cat /proc/swaps


Top
 Profile  
 
 Post subject:
PostPosted: Wed Sep 12, 2007 3:57 pm 
Offline
Joined: Sun Sep 05, 2004 7:06 pm
Posts: 690
You are correct I checked

Code:
cat /proc/swaps


and it shows the swapfile on hda2

Thanks

I also made the change to

/etc/fstab

and that makes the correction for the mount points


Now what about the upgrade since my schema was not migrated what is the best way to sync up the system. Any thoughts on that one?


Top
 Profile  
 
 Post subject:
PostPosted: Wed Sep 12, 2007 4:37 pm 
Offline
Joined: Wed Nov 16, 2005 8:55 pm
Posts: 1381
Location: Farmington, MI USA
RacerX wrote:
Now what about the upgrade since my schema was not migrated what is the best way to sync up the system. Any thoughts on that one?
Did the system bootup as expected? If so, I would:

* - Check /var/log/mythtv/mythbackend.log - If you find a bunch of lines that say "Upgrading to schema version XXXX" then I would guess your system is upgraded. If not then

* - Assuming you still have your backup in /myth/backup (double-check), you could simply perform another upgrade.


Top
 Profile  
 
 Post subject:
PostPosted: Wed Sep 12, 2007 5:57 pm 
Offline
Joined: Sun Sep 05, 2004 7:06 pm
Posts: 690
Yes, the system booted up just fine with the change to FSTAB.

However, the schema change ran this morning before I fixed that
problem. :cry:

So right now when I run mythtv-setup for example it shows schedules direct setup page. But I need to run part or all of the upgrade to update my schema and any other config setttings that it ran so that mythbackend starts to see my data. It is not clear to me what is the best course of action in this case since the ungrade is only partially compleated. I have three choices, mythtv restore, mythtv upgrade, or mythtv partial upgrade. I need some more info in order to choose the correct path.


Top
 Profile  
 
 Post subject:
PostPosted: Wed Sep 12, 2007 6:48 pm 
Offline
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location: Arlington, MA
Unless you've made recordings in the meantime just redo the upgrade or run the restore script then reboot.


Top
 Profile  
 
 Post subject:
PostPosted: Wed Sep 12, 2007 7:29 pm 
Offline
Joined: Sun Sep 05, 2004 7:06 pm
Posts: 690
I reran the update to R5F27 and everything worked fine. Everything is back to normal


THANKS to everyone who helped


Problem Solved :)


Top
 Profile  
 

Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 12 posts ] 


All times are UTC - 6 hours




Who is online

Users browsing this forum: No registered users and 11 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Jump to:  
cron
Powered by phpBB® Forum Software © phpBB Group

Theme Created By ceyhansuyu