Tar backup

Hi
Earlier I used to take tar backup (cold backup) of my R12 database(10g) with the below command and it was taking around 4 hours
tar cvEf - oraprod |gzip -c > /backup/cold/PROD/oraprod.tgz
but from last two backup it is taking around 12 hours, I don't know what is the issue
Only change is I configured Data Guard
Please suggest

Moderator Action:
This post was originally posted to the Solaris 10 General Discussion forum.
This post is likely to receive better understanding in the Dataguard forum.
It is therefore moved for closer topic alignment.
Recent posting history shows an post to the EBS forum for an upgrade question:
Database upgrade
None of that suggests this is an issue with the OS, but rather hints the issue is with everything else.

Similar Messages

Restore Tar Backup

Hi all
can anyone tell me how to restore tar backup (complete procedure) or give url where i can find some pdf or so.
One more q. tar backup is complete os and sap backup or only for os

Tar is used to create archive of files,
for some OS it has additional functionality to do compression .
Detailed options available in your OS can be checked by typing "man tar".
To simply extract file_name.tar to working directory you can use tar xvf file_name.tar
Before doing extraction of any tar files, it is recommended to check the file contents first,
by using tar tvf file_name.tar
You can backup any 'static' file using tar,
that means you should bring the database down before create the tar of its data files .
Rgds,
TS WINEDYA

What is a .tar backup file and can I delete it?

I'm cleaning up files on my iMac and noticed a file in my Documents folder (where I keep applications installation files) that is called "backup-fri-feb-08-15_42_35-2013.tar". This file is over 7 gb so I would like to remove it but I can't find anywhere what it is. I found a wiki page that explains that .tar files are old Unix format but what do I need it for and what program created it?

I use an external drive but I use Carbon Copy Cloner instead of Time Machine and I have TM turned off. I'm wondering if it is a backup file from a program I don't even use any longer. I also use Parallels for 2 Windows programs and I'm finding that some of the Windows programs create backups of stuff I don't need or use. Sounds like it would be safe to delete it.
Thanks so much.

Tar backups to usbdrive...

Hi,
I'm trying out using tar to backup system files to my usbdrive
This command
tar -cvzf /dev/sdd1 -g /backups/etc.snap /etc
backs up /etc to usbdrive & puts a snapshot of files in //backup/etc.snap idea being that I will only have to update changed files or new files
thing is atm it just drops a filename call z in /dev/sdd1 which means nothing lol
Would be nicer to have it named something like etcbackup.taz.gz
/me looks at manual
Atm I would like a simple cli way of backing up /home /etc [maybe pacman stuff!] :?:

Mr Green wrote:would rather use cli ... rsync never had no luck with it ... KDE!!!! nooooo lol
Now just what in the *hell* do you mean you can't get rsync to work? Its the greatest thing since sliced bread.
Lem'me show 'ya somethin'!:
tyler@tungsten ~ $ cat /etc/cron.daily/archbu
#!/bin/bash
backupdir="/mnt/hdb5/backup/arch"
[ ! -f $backupdir ] && mkdir -p $backupdir
rsync -av --delete /etc /home/tyler $backupdir
Look at that. Just look at it. Exact mirror copy. Beautiful.

Tar-backup: gui tool for backups using tar

Hi everybody.
I made little application to simplify process of creating backups. It use tar, openssl (for encrypting archives). Written in QT4
Links:
github
AUR
PKGBUILD
Screenshots:
Main window
Restore tab
Output tab
Backup settings
Tell me what you think. Any feedback is welcome. Thanks.
Last edited by marazmista (2013-07-31 22:45:13)

Wow the GUI looks great.
Sadly, it's of no use to me as I personally am satisfied with rsync. But, I am sure others will find it useful.
Edit: By the way, you should put qt qt4 (whichever version you are using (I am blind )), in the PKGBUILD depends array.
Last edited by x33a (2013-07-18 05:47:55)

[solved] udev /run folder and tar backups

Hi,
I usually make my backups of arch using something like this
tar -cvpzf /media/root-`date +%d%m%y`.tar.gz --exclude=/{dev,lost+found,mnt,media,proc,sys,tmp}/* / | grep tar:
My restore procedure is simple, extract the tar , chroot + mkinitcpio -p + grub and all go fine.
Now the latest updates (initscripts,udev) create a new folder /run , is safe to exclude this folder in the tar file?
Thanks in advance.
/run is a tmpfs so I think is safe to exclude. mark as solved.
Last edited by andrews (2011-05-03 20:46:54)

There are a couple of obvious problems: first, your rule file has to end in .rules (not .rule). See http://www.reactivated.net/writing_udev … tml#syntax
Also, rule files are sorted in lexical order, so you may want to prepend a high number to your rule: 90-logitech-mouse.rules, for example. See http://www.freedesktop.org/software/sys … /udev.html
Finally, if the RUN+= key is blocked, look at using SYSTEMD_WANTS: see `man systemd.device`.

Exempting directories in TAR backups

Hi all,
Although this is a Unix question, I suppose anyone using user managed backups may have encountered this problem:
Let's suppose I've got a directory /u01 and subdirectories a,b,c....up to Z in that directory (ie.u01). If I need to tar up all directories with the exemption_ of x,y and z, what command do I need to run to achieve this.
Regards
Baffy

Hi Laura,
Thanks for your help so far. If I've got 3 directories to exemp (samples01, samples03, samples03), which of the following would be correct:
a) $ tar -cvf sam.tar * --exclude samples01 samples02 samples03
------or-------
b) $ tar -cvf sam.tar * exclude samples01 exclude samples02 --exclude samples03
Regards

How to un tar required file?

Hello All,
I used TAR backup as below.
tar -cvf test01.tar /uo1/oracle/bin/java
its created testo1.tar file.
Now i wanted to untar or recovery only one file instaed of whole tar file.
for e.g: i wanted to recovery only file under bin folder callled config.
how to un tar file?
Any help will be appreciated. Thanks
D

You can look inside the tar using the 't' command:
tar tvf file.tar And you can untar only one file with:
frits@gateway:~/download$ mkdir t
frits@gateway:~/download$ cd t
frits@gateway:~/download/t$ touch a
frits@gateway:~/download/t$ touch b
frits@gateway:~/download/t$ tar czf ab.tgz *
frits@gateway:~/download/t$ ls
a ab.tgz b
frits@gateway:~/download/t$ tar tzf ab.tgz
a
b
frits@gateway:~/download/t$ rm a
frits@gateway:~/download/t$ ls
ab.tgz b
frits@gateway:~/download/t$ tar xzf ab.tgz a
frits@gateway:~/download/t$ ls
a ab.tgz b
frits@gateway:~/download/t$

Help needed.. i can't restore my data backup using Link, it says incompatible...

hi..
i'm loosing all my data now because Link is piece of junk
i have Q10 SQN100-3 with firmware 10.1.0.xxxx i don't remember, and then using autoloader from JSanders posts... i update it to the newest 10.2 available on that post.. afterwards i'm trying to restore my previous backup and it says file isn't compatible with the version of the device software that you are currently running...
so now i lost all my data inside .. please any advice on getting back data from my backup?
maybe you guys have solution for this kind of problem? i saw many threads with similar problems but not solution yet...

yes it was the same device with the same PIN and BB ID.. i have manage to extract the backup file and the manifest.xml contains the software version it was backup to and i can see the blackberry id is the same one i have used..
<?xml version="1.0" encoding="UTF-8"?>
<BlackBerry_Backup><Version>4.0</Version><Client platform="windows" osversion="Microsoft Windows NT 5.1.2600 Service Pack 3" dtmversion="1.2.3.56"/><SourceDevice pin="i hide this" hwid="8600270A" revision="1"><Platform type="QNX" version="10.2.1.2141"/></SourceDevice><QnxOSDevice><Archives><Archive id="app" name="Application Data" count="152" bytesize="615636100" keyid="i hide this" perimetertype="0"/><Archive id="media" name="Media" count="3112" bytesize="908993604" keyid="cece_i hide this" perimetertype="0"/><Archive id="settings" name="Settings" count="1639" bytesize="10474116" keyid="i hide this" perimetertype="0"/></Archives></QnxOSDevice></BlackBerry_Backup>
i get also 3 files app.tar, media.tar, setting.tar this is all 3 data backups from link extract, could we modify it to make another restore files or somehow decrypt the tar backups?

Hot Backup Mannual Pls review for 9i

Hi All,
I am a forms developer for 9 years and new to dba/backup. I have to review a mannual hot backup for a 9i database in Solaris.
There 2 scripts
1) Script to backup all data files (system, users...) runs once in a day and Ftp to a ftp server
2) Script which runs every one hour which takes a backup of redo log files, archive files and control file. And this is ftp to a ftp server.
Q1 Does this good enough to recover the data up to last one hour ?
Q2 Here is my Script 2. Is this correct?
sqlplus "/ as sysdba" << EOF
alter system switch logfile;
EOF
# Sleep for sometime, till the log file is complete
sleep 60
sqlplus "/ as sysdba" << EOF
! rm -Rf /backup/OHotBackup/XX/arch
alter database backup controlfile to '/backup/OHotBackup/XXctrl.ctl';
! cp -r /opt/oracle/product/9.2.0/dbs/arch /backup/OHotBackup/XX
! mv /backup/OHotBackup/XX/ctrl.ctl /backup/OHotBackup/XX/arch/ctrl.ctl
! cp -r /opt/oracle/product/9.2.0/oradata/XX/*.log /backup/XX/arch
! compress /backup/OHotBackup/XX/arch/*.*
! rm /backup/OHotBackup/XX/arch_files.tar
! tar -cvf /backup/OHotBackupXX/arch_files.tar /backup/OHotBackup/XX/arch
select to_char(sysdate,'mm-dd-yyyy:hh:mm:ss.ss') endtime from dual;
disconnect
exit
Thanks in Advance. I read that RMAN backup is better than mannual but for some reasons my company is using this script.
Rajesh ALex

Hi Tom,
Thanks for the reply. First script backs up all the data files.
Here is the script.
PATH=$PATH:$ORACLE_HOME/bin
sqlplus "/as sysdba" << EOF
select to_char(sysdate,'mm-dd-yyyy:hh:mm:ss.ss') astarttime from dual;
SET TERMOUT OFF
SET FEEDBACK OFF
set serveroutput on
SPOOL /opt/oracle/admin/BackupScripts/CopyFiles.sql
declare
cursor c1 is
select distinct(tablespace_name)
from dba_data_files;
cursor c2(ts_name in varchar2) is
select file_name
from dba_data_files
where tablespace_name=ts_name;
data_rec dba_data_files.file_name%type;
ts_rec dba_data_files.tablespace_name%type;
begin
open c1;
loop
fetch c1 into ts_rec;
exit when c1%notfound;
dbms_output.put_line('alter tablespace '||ts_rec||' begin backup;');
open c2(ts_rec);
loop
fetch c2 into data_rec;
exit when c2%notfound;
dbms_output.put_line('!cp -p '||data_rec||' /backup/OHotBackup/OFDAP');
end loop;
close c2;
dbms_output.put_line('alter tablespace '||ts_rec||' end backup;');
end loop;
close c1;
dbms_output.put_line('ALTER SYSTEM ARCHIVE LOG CURRENT;');
dbms_output.put_line('!rm /backup/OHotBackup/OFDAP/ht.ctl');
dbms_output.put_line('alter database backup controlfile to ' || '''/backup/OHotBackup/OFDAP/ht.ctl'''||';');
dbms_output.put_line('alter database backup controlfile to trace;');
dbms_output.put_line('!rm /backup/OHotBackup/OFDAP/initOFDAP.ora');
dbms_output.put_line('!cp -p /opt/oracle/product/9.2.0/admin/OFDAP/pfile/initOFDAP.ora /backup/OHotBackup/OFDAP');
dbms_output.put_line('!rm /backup/OHotBackup/OFDAP/*.dbf.Z');
dbms_output.put_line('!compress /backup/OHotBackup/OFDAP/*.dbf');
end;
spool off;
!perl -pi -e 's/Statement processed.//g' /opt/oracle/admin/BackupScripts/CopyFiles.sql
@/opt/oracle/admin/BackupScripts/CopyFiles.sql
select to_char(sysdate,'mm-dd-yyyy:hh:mm:ss.ss') aendtime from dual;
disconnect
Thanks
Rajesh

[SOLVED] /bin/tar: Cannot utime: Read-only file system

While doing a tar backup on my servers, I get this error:
/bin/tar: /usr/local/bin/sendEmail: Cannot utime: Read-only file system
The error happens on all files in /usr that I'm trying to backup. I know why the error is happening -- I deliberately mount /usr as read-only.
I'd like to know why tar is trying to "utime" my files and how I can stop that behaviour if possible?
This is my tar command:
tar cjf /mnt/backup/backup.tar.bz2 --label='backup_090116' --atime-preserve --no-wildcards-match-slash --files-from=/root/backup.include --exclude-from=/root/backup.exclude
TIA
Last edited by fukawi2 (2009-01-17 07:53:02)

Isn't it quite pointless to preserve timestamps on files from a filesystem on which timestamps aren't modified? Maybe tar tries to update the timestaps prior to archiving the file and is that giving troubles.

How to full HDD clone (backup)?

Hi,
Any idea how to easy full clone (backup) 1:1 the same size hdd with sda1, sda2, sda3, sda4 (home folder dm-crypt and LUKS encrypted)?
I just would like to keep full system with all documents on spare hdd in any hardware failure...
Regards,
Slav

arokh wrote:You can achieve the same thing by doing an rsync or tar backup as well, and it should be tons faster than dd.
I was using rsync (via rsnapshot). I was disappointed at how much time it took to make a backup, although I admit, there's a possibility I was doing something wrong. Eventually I decided that if it's gonna take that long anyway, I might as well just copy everything.
Plus, there are reasons why many of my files change very frequently, which would make an incremental backup less convenient:
Arch Linux is rolling release, which means the operating system files often change.
I have three other operating systems installed that either get updated or just reinstalled.
I rearrange my personal files kind of frequently (for example, moving 8 GB from "Downloads" to "Movies")
Plus plus, I have partitions that don't even have read-write capabilities in Arch Linux (UFS for FreeBSD, BeFS for Haiku), although it sure would be convenient to me for someone to prove me wrong in that regard.
So, for someone with a "complicated" configuration, like tho OP, I think a dd command would be quite suitable.
Just partition the backup drive the same way, mount it all under /mnt and find a backup tutorial in the wiki to make your own script. Remember to install a bootloader on the backup drive as well.
You prefix all that with the word "just", but it really sounds a lot more complicated than my one dd command... I don't even have to test my backup. I tested it the first time (I was able to boot from my backup, everything worked fine), and now I just look for errors from the dd command. If the original works, then the backup works.

Valid One-Time Backup Strategy?

I wanted to get some feedback on a one-time backup strategy. We currently run RMAN incremental level 0 backups once a week, then run incremental level 1 backups nightly. These seem sufficient for our needs.
In the near future, though, we are planning an upgrade of 9i to 10g. In case we need to undo the upgrade, I want to make sure I have all bases covered when performing this upgrade. My strategy is:
- Run a level 1 incremental right before starting the upgrade.
- Shut down the instance
- Backup the entire ORACLE_HOME(without the data files) using OS commands(tar)
- Backup the entire oraInventory directory.
If I needed to restore the 9i database to its pre-upgrade condition, I would simply untar the ORACLE_HOME, the oraInventory and then run an rman restore and recover.
Is there any flaw in this strategy?
Thanks, Nick

RMAN Compatibility Matrix and Guide (Note:73431.1)
https://metalink.oracle.com/metalink/plsql/showdoc?db=NOT&id=73431.1&blackframe=1
Bye, Aron

[Solved] Can't boot into Arch after deleting some partitons

About 6 months ago I installed Arch on a machine that used to run Ubuntu. Had some trouble at the time getting to boot into Arch but somehow managed. Now eventually decided to delete the old Ubuntu partitons to free up some space using gparted. Arch partition number changed from sda12 to sda6.
On rebooting after deleting ubuntu partitions with gparted, I got an ubuntu splash screen and a whole lot of ubuntu boot options. Somehow these were all contained in my Arch's /boot/grub/menu.lst. Arch is all on one partition and no separate boot partition (which I had with Ubuntu - maybe I haven't deleted that and this is the problem?). Will need to check that out.
I can chroot into Arch and did the following -
grub> find /boot/grub/stage1
(hd0,5)
grub> root (hd0,5)
Filesystem type is ext2fs, partition type 0x83
grub> setup (hd0)
Checking if "/boot/grub/stage1" exists... yes
Checking if "/boot/grub/stage2" exists... yes
Checking if "/boot/grub/e2fs_stage1_5" exists... yes
Running "embed /boot/grub/e2fs_stage1_5 (hd0)"... 16 sectors are embedded.
succeeded
Running "install /boot/grub/stage1 (hd0) (hd0)1+16 p (hd0,5)/boot/grub/stage2 /boot/grub/menu.lst"... succeed
ed
Done.
grub>
The Arch /boot/grub/menu.lst had a whole lot of ubuntu stuff in it but I edited to the following -
# menu.lst - See: grub(8), info grub, update-grub(8)
# grub-install(8), grub-floppy(8),
# grub-md5-crypt, /usr/share/doc/grub
# and /usr/share/doc/grub-doc/.
## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
# WARNING: If you are using dmraid do not use 'savedefault' or your
# array will desync and will not let you boot your system.
default 0
## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout 3
## hiddenmenu
# Hides the menu by default (press ESC to see the menu)
hiddenmenu
# Pretty colours
#color cyan/blue white/blue
## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line) and entries protected by the
# command 'lock'
# e.g. password topsecret
# password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret
# examples
# title Windows 95/98/NT/2000
# root (hd0,0)
# makeactive
# chainloader +1
# title Linux
# root (hd0,1)
# kernel /vmlinuz root=/dev/hda2 ro
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST
## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,3)
title Arch uuid
#root (hd0,5)
uuid d15cf4f9-18ca-4ec5-95bc-db0f6f264736
kernel /boot/vmlinuz26 root=/dev/sda6 ro vga=775
intrd /boot/kernel26.img
title Arch hd
root (hd0,5)
kernel /boot/vmlinuz26 root=/dev/sda6
intrd /boot/kernel26.img
I have a bootinfo script which gives the following (from the chroot environment) -
Boot Info Script 0.55 dated February 15th, 2010
============================= Boot Info Summary: ==============================
=> Grub 0.97 is installed in the MBR of /dev/sda and looks on the same drive
in partition #6 for /boot/grub/stage2 and /boot/grub/menu.lst.
=> No boot loader is installed in the MBR of /dev/sdb
sda1: _________________________________________________________________________
File system: swap
Boot sector type: -
Boot sector info:
sda2: _________________________________________________________________________
File system: Extended Partition
Boot sector type: -
Boot sector info:
sda5: _________________________________________________________________________
File system: ext3
Boot sector type: -
Boot sector info:
Mounting failed:
mount: /dev/sda5 already mounted or sda5 busy
sda6: _________________________________________________________________________
File system: ext3
Boot sector type: -
Boot sector info:
Mounting failed:
mount: /dev/sda5 already mounted or sda5 busy
mount: /dev/sda6 already mounted or sda6 busy
sda7: _________________________________________________________________________
File system: ext3
Boot sector type: -
Boot sector info:
Operating System:
Boot files/dirs:
sda3: _________________________________________________________________________
File system: ext3
Boot sector type: -
Boot sector info:
Operating System: Ubuntu 10.04.1 LTS
Boot files/dirs: /etc/fstab
sda4: _________________________________________________________________________
File system: ext3
Boot sector type: -
Boot sector info:
Operating System:
Boot files/dirs: /grub/menu.lst /grub/grub.cfg /grub/core.img
sdb1: _________________________________________________________________________
File system: xfs
Boot sector type: -
Boot sector info:
Operating System:
Boot files/dirs:
=========================== Drive/Partition Info: =============================
Drive: sda ___________________ _____________________________________________________
Disk /dev/sda: 750.2 GB, 750155292160 bytes
255 heads, 63 sectors/track, 91201 cylinders, total 1465147055 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
Partition Boot Start End Size Id System
/dev/sda1 417,690 6,554,519 6,136,830 82 Linux swap / Solaris
/dev/sda2 25,414,954 1,465,144,064 1,439,729,111 5 Extended
/dev/sda5 25,414,956 1,360,287,809 1,334,872,854 83 Linux
/dev/sda6 1,360,287,873 1,423,198,349 62,910,477 83 Linux
/dev/sda7 1,423,198,413 1,465,144,064 41,945,652 83 Linux
/dev/sda3 6,554,520 25,414,829 18,860,310 83 Linux
/dev/sda4 * 63 417,689 417,627 83 Linux
Drive: sdb ___________________ _____________________________________________________
Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
Partition Boot Start End Size Id System
/dev/sdb1 2,048 1,953,523,711 1,953,521,664 83 Linux
blkid -c /dev/null: ____________________________________________________________
Device UUID TYPE LABEL
/dev/loop0 squashfs
/dev/sda1 2a95d85a-45fe-4584-88dd-0ee20e651ec5 swap
/dev/sda2: PTTYPE="dos" PART_ENTRY_SCHEME="dos" PART_ENTRY_TYPE="0x5" PART_ENTRY_NUMBER="2"
/dev/sda3 32495e1a-227c-4d23-9f63-b1319def0dd9 ext3
/dev/sda4 d6dc69b0-967d-4886-b62d-8c0d6be06b41 ext3
/dev/sda5 37971286-b8d3-4a1b-9f94-4008288fed6d ext3 data
/dev/sda6 d15cf4f9-18ca-4ec5-95bc-db0f6f264736 ext3 30GB-02
/dev/sda7 eb736131-b558-4404-9b83-7f1e6d9e76ae ext3 var
/dev/sda: PTTYPE="dos"
/dev/sdb1 0e83045d-a0bd-4d36-b61d-bdb905130dc2 xfs 1TB-04
/dev/sdb: PTTYPE="dos"
============================ "mount | grep ^/dev output: ===========================
Device Mount_Point Type Options
/dev/sda12 / ext3 (rw,commit=0)
=============================== sda3/etc/fstab: ===============================
# /etc/fstab: static file system information.
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# /dev/sda1 = swap
/dev/sda1 none swap sw 0 0
# /dev/sda3 = root
#UUID=32495e1a-227c-4d23-9f63-b1319def0dd9
/dev/sda3 / ext3 relatime,errors=remount-ro 0 1
# /dev/sda4 = boot
# UUID=d6dc69b0-967d-4886-b62d-8c0d6be06b41
/dev/sda4 /boot ext3 relatime 0 2
# /dev/sda5 = home
# UUID=670eee83-0a3e-429c-863f-b9ecced9f97e
/dev/sda5 /home ext3 relatime 0 2
#/dev/sda6
#UUID=37971286-b8d3-4a1b-9f94-4008288fed6d
/dev/sda6 /home/ben/Data ext3 defaults,relatime 0 0
# /dev/sda7
# UUID=fdb14ca4-d71d-489f-a00e-6e608770674c
/dev/sda7 /var ext3 relatime 0 2
# /dev/sda8
/dev/sda8 /opt ext3 relatime 0 2
# /dev/sda10 - Arch
/dev/sda10 /mnt/arch ext3 relatime 0 2
# Not sure what this is doing here
# Have commented it out - May be the reason why xbmc and mythtv were crashing on dvd insert and play
# /dev/hda /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0
# /dev/sde1
# uuid appears to be 644406B3570C1846 -> ../../sde1
#/dev/sde1 /home/ben/Data/TVRecordings-1TB01 xfs defaults,relatime 0 0
#1TB-01
UUID=76f3823a-81dc-45c9-a0b7-2bc6c3beb2f8 /media/1TB-01 xfs noatime,nodiratime,allocsize=512m 0 0 #remove
d defaults, relatime
# 1TB-02
UUID=59cbf7a1-7008-40d0-96ed-c6f231823d4f /media/1TB-02 xfs noatime,nodiratime,allocsize=512m 0 0 #remove
d defaults, relatime
# 1TB-03
UUID=0e936800-3c53-4b87-abc8-19be0ffca7f9 /media/1TB-03 xfs noatime,nodiratime,allocsize=512m 0 0 #remove
d defaults, relatime
# 750GB-02 ext3 Partition
# UUID giving problems, trying with dev
# UUID=c23b9c9a-66fc-4256-9211-73156c1ac64a /media/750GB-02_ext3 ext3 defaults,relatime 0 0
/dev/sde2 /media/750GB-02_ext3 ext3 defaults,relatime 0 0
============================= sda4/grub/menu.lst: =============================
# menu.lst - See: grub(8), info grub, update-grub(8)
# grub-install(8), grub-floppy(8),
# grub-md5-crypt, /usr/share/doc/grub
# and /usr/share/doc/grub-doc/.
## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
# WARNING: If you are using dmraid do not use 'savedefault' or your
# array will desync and will not let you boot your system.
default 0
## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout 3
## hiddenmenu
# Hides the menu by default (press ESC to see the menu)
hiddenmenu
# Pretty colours
#color cyan/blue white/blue
## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line) and entries protected by the
# command 'lock'
# e.g. password topsecret
# password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret
# examples
# title Windows 95/98/NT/2000
# root (hd0,0)
# makeactive
# chainloader +1
# title Linux
# root (hd0,1)
# kernel /vmlinuz root=/dev/hda2 ro
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST
### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default options below
## DO NOT UNCOMMENT THEM, Just edit them to your needs
## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specific kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
## kopt_2_6_8=root=/dev/hdc1 ro
## kopt_2_6_8_2_686=root=/dev/hdc2 ro
# kopt=root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro
## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,3)
## should update-grub create alternative automagic boot options
## e.g. alternative=true
## alternative=false
# alternative=true
## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
## lockalternative=false
# lockalternative=false
## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=quiet splash
## should update-grub lock old automagic boot options
## e.g. lockold=false
## lockold=true
# lockold=false
## Xen hypervisor options to use with the default Xen boot option
# xenhopt=
## Xen Linux kernel options to use with the default Xen boot option
# xenkopt=console=tty0
## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
## altoptions=(recovery) single
# altoptions=(recovery mode) single
## controls how many kernels should be put into the menu.lst
## only counts the first occurence of a kernel, not the
## alternative kernel options
## e.g. howmany=all
## howmany=7
# howmany=all
## should update-grub create memtest86 boot option
## e.g. memtest86=true
## memtest86=false
# memtest86=true
## should update-grub adjust the value of the default booted system
## can be true or false
# updatedefaultentry=false
## should update-grub add savedefault to the default options
## can be true or false
# savedefault=false
## ## End Default Options ##
title Ubuntu 10.04.1 LTS, kernel 2.6.32-26-generic
root (hd0,3)
kernel /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
initrd /initrd.img-2.6.32-26-generic
quiet
title Ubuntu 10.04.1 LTS, kernel 2.6.32-26-generic (recovery mode)
root (hd0,3)
kernel /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
initrd /initrd.img-2.6.32-26-generic
title Ubuntu 10.04.1 LTS, kernel 2.6.32-24-generic
root (hd0,3)
kernel /vmlinuz-2.6.32-24-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
initrd /initrd.img-2.6.32-24-generic
quiet
title Ubuntu 10.04.1 LTS, kernel 2.6.32-24-generic (recovery mode)
root (hd0,3)
kernel /vmlinuz-2.6.32-24-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
initrd /initrd.img-2.6.32-24-generic
title Ubuntu 10.04.1 LTS, kernel 2.6.32-23-generic
root (hd0,3)
kernel /vmlinuz-2.6.32-23-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
initrd /initrd.img-2.6.32-23-generic
quiet
title Ubuntu 10.04.1 LTS, kernel 2.6.32-23-generic (recovery mode)
root (hd0,3)
kernel /vmlinuz-2.6.32-23-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
initrd /initrd.img-2.6.32-23-generic
title Ubuntu 10.04.1 LTS, kernel 2.6.32-22-generic
root (hd0,3)
kernel /vmlinuz-2.6.32-22-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
initrd /initrd.img-2.6.32-22-generic
quiet
title Ubuntu 10.04.1 LTS, kernel 2.6.32-22-generic (recovery mode)
root (hd0,3)
kernel /vmlinuz-2.6.32-22-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
initrd /initrd.img-2.6.32-22-generic
title Ubuntu 10.04.1 LTS, memtest86+
root (hd0,3)
kernel /memtest86+.bin
quiet
### END DEBIAN AUTOMAGIC KERNELS LIST
============================= sda4/grub/grub.cfg: =============================
# DO NOT EDIT THIS FILE
# It is automatically generated by /usr/sbin/grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
load_env
fi
set default="0"
if [ ${prev_saved_entry} ]; then
set saved_entry=${prev_saved_entry}
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z ${boot_once} ]; then
saved_entry=${chosen}
save_env saved_entry
fi
function recordfail {
set recordfail=1
if [ -n ${have_grubenv} ]; then if [ -z ${boot_once} ]; then save_env recordfail; fi; fi
insmod ext2
set root='(hd0,3)'
search --no-floppy --fs-uuid --set 32495e1a-227c-4d23-9f63-b1319def0dd9
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=640x480
insmod gfxterm
insmod vbe
if terminal_output gfxterm ; then true ; else
# For backward compatibility with versions of terminal.mod that don't
# understand terminal_output
terminal gfxterm
fi
fi
insmod ext2
set root='(hd0,4)'
search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
set locale_dir=($root)/grub/locale
set lang=en
insmod gettext
if [ ${recordfail} = 1 ]; then
set timeout=-1
else
set timeout=10
fi
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=white/black
set menu_color_highlight=black/light-gray
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Ubuntu, with Linux 2.6.32-26-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd0,4)'
search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
linux /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
initrd /initrd.img-2.6.32-26-generic
menuentry 'Ubuntu, with Linux 2.6.32-26-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu -
-class os {
recordfail
insmod ext2
set root='(hd0,4)'
search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
echo 'Loading Linux 2.6.32-26-generic ...'
linux /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
echo 'Loading initial ramdisk ...'
initrd /initrd.img-2.6.32-26-generic
menuentry 'Ubuntu, with Linux 2.6.32-24-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd0,4)'
search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
linux /vmlinuz-2.6.32-24-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
initrd /initrd.img-2.6.32-24-generic
menuentry 'Ubuntu, with Linux 2.6.32-24-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu -
-class os {
recordfail
insmod ext2
set root='(hd0,4)'
search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
echo 'Loading Linux 2.6.32-24-generic ...'
linux /vmlinuz-2.6.32-24-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
echo 'Loading initial ramdisk ...'
initrd /initrd.img-2.6.32-24-generic
menuentry 'Ubuntu, with Linux 2.6.32-23-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd0,4)'
search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
linux /vmlinuz-2.6.32-23-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
initrd /initrd.img-2.6.32-23-generic
menuentry 'Ubuntu, with Linux 2.6.32-23-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu -
-class os {
recordfail
insmod ext2
set root='(hd0,4)'
search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
echo 'Loading Linux 2.6.32-23-generic ...'
linux /vmlinuz-2.6.32-23-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
echo 'Loading initial ramdisk ...'
initrd /initrd.img-2.6.32-23-generic
menuentry 'Ubuntu, with Linux 2.6.32-22-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd0,4)'
search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
linux /vmlinuz-2.6.32-22-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
initrd /initrd.img-2.6.32-22-generic
menuentry 'Ubuntu, with Linux 2.6.32-22-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu -
-class os {
recordfail
insmod ext2
set root='(hd0,4)'
search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
echo 'Loading Linux 2.6.32-22-generic ...'
linux /vmlinuz-2.6.32-22-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
echo 'Loading initial ramdisk ...'
initrd /initrd.img-2.6.32-22-generic
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry "Memory test (memtest86+)" {
insmod ext2
set root='(hd0,4)'
search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
linux16 /memtest86+.bin
menuentry "Memory test (memtest86+, serial console 115200)" {
insmod ext2
set root='(hd0,4)'
search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
linux16 /memtest86+.bin console=ttyS0,115200n8
### END /etc/grub.d/20_memtest86+ ###
### BEGIN /etc/grub.d/30_os-prober ###
menuentry "Arch Linux (on /dev/sda10)" {
insmod ext2
set root='(hd0,10)'
search --no-floppy --fs-uuid --set 26851879-58d1-4d65-90b4-e0845fe1176c
linux /boot/vmlinuz26 root=/dev/sda10 ro
initrd /boot/kernel26.img
menuentry "Arch Linux Fallback (on /dev/sda10)" {
insmod ext2
set root='(hd0,10)'
search --no-floppy --fs-uuid --set 26851879-58d1-4d65-90b4-e0845fe1176c
linux /boot/vmlinuz26 root=/dev/sda10 ro
initrd /boot/kernel26-fallback.img
#### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
# From Arch grub menu.lst
# (0) Arch Linux
#title Arch Linux [/boot/vmlinuz26]
#root (hd0,0)
#kernel /vmlinuz26 root=/dev/sda3 ro
#initrd /kernel26.img
#Note: With a separate boot partition, omit /boot from the path, (i.e. type set prefix=(hdX,Y)/grub and insmod
(hdX,Y)/grub/linux.mod).
#This introduces the "linux" and "initrd" commands, which should be familiar (see #Configuration).
#An example, booting Arch Linux:
#set root=(hd0,5)
#linux /boot/vmlinuz26 root=/dev/sda5
#initrd /boot/kernel26.img
#boot
###menuentry "Arch1" {
###insmod ext2
###set root='(hd0,10)'
#search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41 = FOR UBUNTU THIS IS THE BOOT
PARTITION
#linux /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash = FOR
UBUNTU THIS IS THE ROOT PARTITION
#initrd /initrd.img-2.6.32-26-generic
###search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41 # UBUNTU'S BOOT PARTITION UU
ID
###linux /boot/vmlinuz-26 root=635d7d02-3f5b-4af6-9c74-16b2af8cc7fd ro quiet splash # ARCH'S ROOT UUID
###initrd /boot/kernel26.img
# /dev/sda10 uuid = 635d7d02-3f5b-4af6-9c74-16b2af8cc7fd - obtain using ls -l /dev/disk/by-uuid/
###menuentry "Arch2" {
###insmod ext2
###set root='(hd0,4)' #= TRYING UBUNTU'S BOOT
#search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41 = FOR UBUNTU THIS IS THE BOOT
PARTITION
#linux /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash = FOR
UBUNTU THIS IS THE ROOT PARTITION
#initrd /initrd.img-2.6.32-26-generic
#search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41 # UBUNTU'S BOOT PARTITION UUID
###linux /boot/vmlinuz-26 root=/dev/sda10 ro quiet splash # TRYING ARCH'S ROOT DEVICE FORMAT
###initrd /boot/kernel26.img
# /dev/sda10 uuid = 635d7d02-3f5b-4af6-9c74-16b2af8cc7fd - obtain using ls -l /dev/disk/by-uuid/
###menuentry "Arch3" {
###insmod ext2
###set root='(hd0,10)' #= TRYING UBUNTU'S BOOT IN HD FORMAT
#search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41 = FOR UBUNTU THIS IS THE BOOT
PARTITION
#linux /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash = FOR
UBUNTU THIS IS THE ROOT PARTITION
#initrd /initrd.img-2.6.32-26-generic
#search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41 # UBUNTU'S BOOT PARTITION UUID
###linux /boot/vmlinuz-26 root=/dev/sda10 ro quiet splash # TRYING ARCH'S ROOT DEVICE FORMAT
###initrd /boot/kernel26.img
# /dev/sda10 uuid = 635d7d02-3f5b-4af6-9c74-16b2af8cc7fd - obtain using ls -l /dev/disk/by-uuid/
### END /etc/grub.d/40_custom ###
=================== sda4: Location of files loaded by Grub: ===================
.0GB: grub/core.img
.0GB: grub/grub.cfg
.0GB: grub/menu.lst
.0GB: grub/stage2
.0GB: initrd.img-2.6.32-22-generic
.0GB: initrd.img-2.6.32-23-generic
.1GB: initrd.img-2.6.32-24-generic
.1GB: initrd.img-2.6.32-26-generic
.0GB: vmlinuz26
.0GB: vmlinuz-2.6.32-22-generic
.0GB: vmlinuz-2.6.32-23-generic
.1GB: vmlinuz-2.6.32-24-generic
.0GB: vmlinuz-2.6.32-26-generic
=============================== StdErr Messages: ===============================
No volume groups found
mdadm: No arrays found in config file or automatically
[/quote]
Output of fdisk -l from chroot is -
[quote]Disk /dev/sda: 750.2 GB, 750155292160 bytes
255 heads, 63 sectors/track, 91201 cylinders, total 1465147055 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0000b084
Device Boot Start End Blocks Id System
/dev/sda1 417690 6554519 3068415 82 Linux swap / Solaris
/dev/sda2 25414954 1465144064 719864555+ 5 Extended
/dev/sda3 6554520 25414829 9430155 83 Linux
/dev/sda4 * 63 417689 208813+ 83 Linux
/dev/sda5 25414956 1360287809 667436427 83 Linux
/dev/sda6 1360287873 1423198349 31455238+ 83 Linux
/dev/sda7 1423198413 1465144064 20972826 83 Linux
Partition table entries are not in disk order
Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00025bd3
Device Boot Start End Blocks Id System
/dev/sdb1 2048 1953523711 976760832 83 Linux
I need to post this now and come back from a different machine to note the error messages I am now getting on boot. ...
Note that when I boot and press esc to get the menu I get the menu.lst I created (in the second quote) above in /dev/sda6, ie the one with the Arch hd and uuid entries - so grub is looking there and finding that menu.lst, but something goes wrong after that.
OK. Have now booted the machine and after pressing esc and selecting the uuid entry (the same thing happens with the hd entry) I get a whole lot of stuff, but what seems relevant is (typing it out) -
List of all partitions:
No filesystem could mount root, tried:
Kernel panic - not syncing: VS: Unable to mount root fs on unknown-block(0,0)
Pid: 1, comm: swapper Not tainted 2.6.39-Arch #1
If anyone can help I'd really appreciate it. This is my MythTV machine so the WAF is about to take a big dive!
If I could just install grub to the MBR as if this was a new installation of Arch that would be great.
I am really lost as to what is going on, which I'm sure is evident.
Thanks a lot
belbo
Last edited by belbo (2011-08-12 13:31:23)

Hi. Unfortunately that didn't help.
So next, based on this post https://wiki.archlinux.org/index.php/Ke … el_version I chrooted into Arch and (a) rolled back and (b) reinstalled my kernel but that didn't help either. I suspected it wouldn't because the kernel was working fine before I deleted the partitions in question.
[2011-08-08 23:32] ==> Image generation successful
[2011-08-08 23:32] upgraded kernel26 (2.6.39.3-1 -> 2.6.39.3-1)
I then did a pacman -Suy and the linux package has now replaced kernel26. ( See this wiki entry http://www.archlinux.org/news/changes-t … filenames/). I didn't change anything in menu.lst owing to this and it seems there is no need to. Unfortunately this hasn't helped either - still getting the kernel panic.
Pacman.log relating to the new kernel package below -
[2011-08-09 00:22] Running 'pacman -Suy'
[2011-08-09 00:22] synchronizing package lists
[2011-08-09 00:23] starting full system upgrade
[2011-08-09 00:23] Running 'pacman -Suy'
[2011-08-09 00:23] synchronizing package lists
[2011-08-09 00:23] starting full system upgrade
[2011-08-09 00:26] removed python-mygpoclient (1.5-1)
[2011-08-09 00:26] removed kernel26 (2.6.39.3-1)
[2011-08-09 00:26] warning: /boot/grub/menu.lst installed as /boot/grub/menu.lst.pacnew
[2011-08-09 00:26] upgraded grub (0.97-17 -> 0.97-19)
[2011-08-09 00:26] upgraded icu (4.8-1 -> 4.8.1-1)
[2011-08-09 00:26] upgraded linux-firmware (20110512-2 -> 20110727-1)
[2011-08-09 00:26] >>> Updating module dependencies. Please wait ...
[2011-08-09 00:26] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2011-08-09 00:26] ==> Building image from preset: 'default'
[2011-08-09 00:26] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2011-08-09 00:26] ==> Starting build: 3.0-ARCH
[2011-08-09 00:26] -> Parsing hook: [base]
[2011-08-09 00:26] -> Parsing hook: [udev]
[2011-08-09 00:26] -> Parsing hook: [autodetect]
[2011-08-09 00:26] -> Parsing hook: [pata]
[2011-08-09 00:26] -> Parsing hook: [scsi]
[2011-08-09 00:26] -> Parsing hook: [sata]
[2011-08-09 00:26] -> Parsing hook: [filesystems]
[2011-08-09 00:26] -> Parsing hook: [usbinput]
[2011-08-09 00:26] ==> Generating module dependencies
[2011-08-09 00:26] ==> Creating gzip initcpio image: /boot/initramfs-linux.img
[2011-08-09 00:26] 7079 blocks
[2011-08-09 00:26] ==> Image generation successful
[2011-08-09 00:26] ==> Building image from preset: 'fallback'
[2011-08-09 00:26] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2011-08-09 00:26] ==> Starting build: 3.0-ARCH
[2011-08-09 00:26] -> Parsing hook: [base]
[2011-08-09 00:26] -> Parsing hook: [udev]
[2011-08-09 00:26] -> Parsing hook: [pata]
[2011-08-09 00:26] -> Parsing hook: [scsi]
[2011-08-09 00:26] -> Parsing hook: [sata]
[2011-08-09 00:26] -> Parsing hook: [filesystems]
[2011-08-09 00:26] -> Parsing hook: [usbinput]
[2011-08-09 00:26] ==> Generating module dependencies
[2011-08-09 00:26] ==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
[2011-08-09 00:26] 23360 blocks
[2011-08-09 00:26] ==> Image generation successful
[2011-08-09 00:26] installed linux (3.0.1-1)
I don't think I've mentioned that my old menu.lst seems to have disappeared and so must have been on one of the partitions that were deleted. I did have 2 Arch installations when I was setting things up months ago and that menu.lst may have been on the other partition but pointing to this partiton's kernel for booting. Presumably that's possible since this partiton is definitely the one I have been using for the last several months (confirmed by log and other files updated in the last few days etc). Even so, I suppose that probably wouldn't be relevant to this issue, since grub is finding the menu.lst on this partition when it boots so it is looking in the intended place now.
It seems I'm at a bit of a dead end. It seems these kernel panics are usually because there is something wrong with the kernel - which there wasn't with mine (and presumably the kernel in the new linux package is fine) or there is a typo in menu.lst (I can't see one and nobody has pointed one out yet) or menu.lst is pointing to the wrong partition (mine is pointing to the same partition and /boot directory that is found by grub - which is where my boot image is located - so it seems to be correct). I have nevertheless tried editing the menu.lst entry when booting to boot from different partitions but so far that hasn't worked either.
If anybody has other ideas I'd really appreciate it.
If not, some suggestions on re-installing would also be appreciated. I have a recent tar archive of the partition, but presumably reinstalling that wouldn't be of much use since it would just put back what is currently there. I guess that I need to format the partition, create a separate boot partition, do a fresh install of Arch into the formatted partition (and with boot in the new boot partition). And then restore my tar backup (excluding the boot directory) into the formatted partition?
Any assistance greatly appreciated.
Thanks
belbo
Last edited by belbo (2011-08-08 23:17:49)

Error after oracle software cloning

Hi all ,
I have a database(10.2.0.5.0) in solaris 10 , i simply take a tar backup of ORACLE_HOME and
extracted them into another server (which is solaris 10 only) and linked the binaries
after that when i connecting with sqlplus i am getting following error
SQL*Plus: Release 10.2.0.5.0 - Production on Fri Oct 4 14:49:48 2013
Copyright (c) 1982, 2010, Oracle. All Rights Reserved.
Enter user-name: /as sysdba
ld.so.1: oracle: fatal: libskgxp10.so: open failed: No such file or directory
ERROR:
ORA-12547: TNS:lost contact
I would like to tell that i have also oracle 11gr2 running on the server
my oracle_base is same for both(10g 11g)
but ORACLE_HOME is different.
please help ??

You probably have some confusion between 32 and 64 bit versions of that file. Get a long listing of the file on each computer to see if they are the same. Sometimes people copy over the file to fix this, sometimes they fix it with links, sometimes it's just messed up in cloning as links become real. See Billy's response: ld.so.1: oracle: fatal: libskgxp10.so: open failed: No such file or directo

Tar backup

Similar Messages

Maybe you are looking for