EXT3-fs error
Hy
I have a strange problem right now.
I set up a new Arch installation some days ago...
I went away, some hours, and as I came back, nothing worked.
At least, nothing that wasn't loaded in the memory.
So I have a shell now (bash), and cannot start anything.
Everytime I wan't to start something (like init, less, cat, etc.), I get this error message:
[cimnine@anti-1 ~]$ ls
EXT3-fs error (device sda3): ext3_find_entry: reading directory #16321 offset 0
EXT3-fs error (device sda3): ext3_find_entry: reading directory #595681 offset 0
-bash: ls: command not found
[cimnine@anti-1 ~]$ init 6
EXT3-fs error (device sda3): ext3_find_entry: reading directory #16321 offset 0
-bash: /sbin/init: No such file or directory
When I hardreset my PC, the device sda3 doesn't even get recogniced by the BIOS anymore. I have to connect the disk with another SATA-Port.
My PC:
Mainboard: Asus R.O.G. Striker II Formula // BIOS: 0902
CPU: Intel Core 2 Quad Q6600 GO
Harddisk: Samsung HD103UJ
I never came across a similar problem - I have absolutly no glue what I could do.
~Chris
Rehto wrote:
mcover wrote:I have an Asus Laptop and I used to have problems connecting a hard-disk to my eSATA port. It was problems with resources and IRQ allocation, but it somehow fixed itself with continuing upgrades (kernel?). Thou recently I had a problem where I was using my hard-disk and then randomly the system tells me that the disk does not exist anymore and after checking dmesg I saw that it was the same problem again (something about reseting the SATA port - sorry don't have log anymore).
I'm having a problem similar to yours when using an eSATA port to connect my external hdd. When moving files the transfer suddenly stops and I get these messages in dmesg and /var/log/messages
http://pastebin.ca/1340177
http://pastebin.ca/1340183
I'm using x86_64 updated to the latest stable...
Yup, thats exactly what I've been getting as well. However, as mentioned, I haven't had the problem for over a month now (regularly using eSATA).
Just to check my theory, could you look at your /proc/interrupts ? I suppose it is also some bug with ahci - not just the hardware its running on.
Similar Messages
-
EXT3-fs error (device sda6): in CONSOLE of CUCM 9.1
Hello my friends,
After several days of having my CUCM working properly, the CUCM show me EXT3-fs error (device sda6): xxxxxx , my TFTP service is down and never go UP again. I restart the server and the problem didnt go away.
Any idea whats going on????
Someone know what troubleshooting can i do?
I appreciate your help....
CUCM 9.1
ESXi 5.1
Attache the ERRORHello Jaime,
I do have the backup, but i didnt do the recovery, i reinstall all the server again, rigth now its good and all the services are UP. But what if it happens again. =(
Are you sure nothing happened to the server or wherever you have the vmdks???
The server does not show any kind of alerts.
Im goint to download some infomation from the console of the server just to check everything its fine with the vmdks.
Have you heard about a BUG in ESXi5.1 when you install CUCM 9.1 ??
Thanks for you answer -
(Read-only file system) ,EXT3-fs error (device sda6) in start_transaction, FOR MY MCS7825I3-K9-CMC1
I got this problem for my cucm version System version: 7.0.2.20000-5
Product Part Number: MCS7825I3-K9-CMC1
java.io.FileNotFoundException: /var/log/active/platform/log/cli.bin (Read-only file system)
log4j:ERROR No output stream or file set for the appender named [CLI_LOG].
EXT3-fs error (device sda6) in start_transaction: Journal has aborted SeverityMatch - Critical kernel: EXT3-fs error (device sda6) in start_transaction: Journal has aborted SeverityMatch - Critical kernel: EXT3-fs error (device sda6) in
Any Advice to solve this issue ?
Kind Regards
Mohammed khamis
java.io.FileNotFoundException: /var/log/active/platform/log/cli.bin (Read-only file system)
at java.io.RandomAccessFile.open(Native Method)
at java.io.RandomAccessFile.<init>(RandomAccessFile.java:212)
at com.cisco.iptplatform.fappend.ciscoRollingFileAppender.restoreIndex(c iscoRollingFileAppender.java:100)
at com.cisco.iptplatform.fappend.ciscoRollingFileAppender.setFile(ciscoR ollingFileAppender.java:43)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.log4j.config.PropertySetter.setProperty(PropertySetter.jav a:196)
at org.apache.log4j.config.PropertySetter.setProperty(PropertySetter.jav a:155)
at org.apache.log4j.xml.DOMConfigurator.setParameter(DOMConfigurator.jav a:530)
at org.apache.log4j.xml.DOMConfigurator.parseAppender(DOMConfigurator.ja va:182)
at org.apache.log4j.xml.DOMConfigurator.findAppenderByName(DOMConfigurat or.java:140)
at org.apache.log4j.xml.DOMConfigurator.findAppenderByReference(DOMConfi gurator.java:153)
at org.apache.log4j.xml.DOMConfigurator.parseChildrenOfLoggerElement(DOM Configurator.java:415)
at org.apache.log4j.xml.DOMConfigurator.parseRoot(DOMConfigurator.java:3 84)
at org.apache.log4j.xml.DOMConfigurator.parse(DOMConfigurator.java:783)
at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java :666)
at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java :616)
at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java :584)
at org.apache.log4j.xml.DOMConfigurator.configure(DOMConfigurator.java:6 87)
at sdMain.main(sdMain.java:511)
java.lang.NullPointerException
at com.cisco.iptplatform.fappend.ciscoRollingFileAppender.updateIndex(ci scoRollingFileAppender.java:117)
at com.cisco.iptplatform.fappend.ciscoRollingFileAppender.nextFileName(c iscoRollingFileAppender.java:92)
at com.cisco.iptplatform.fappend.ciscoRollingFileAppender.append(ciscoRo llingFileAppender.java:74)
at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:221)
at org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders (AppenderAttachableImpl.java:57)
at org.apache.log4j.Category.callAppenders(Category.java:187)
at org.apache.log4j.Category.forcedLog(Category.java:372)
at org.apache.log4j.Category.info(Category.java:674)
at sdMain.main(sdMain.java:525)
log4j:ERROR No output stream or file set for the appender named [CLI_LOG].
Welcome to the Platform Command Line Interface
admin:java.io.FileNotFoundException: /var/log/active/platform/log/cli.bin (Read-only f ile system):java.io.FileNotFoundException: /var/log/active/platform/log/cli.bin (Read-only f ile system)Hello
Thanks Manish .
I found many articles in cisco which says that this error is related to the bug which need firmware upgrade , but I don't have support from cisco because EOS.
https://supportforums.cisco.com/document/49511/updated-16-february-2011-ibm-7816-i4-782x-i4-filesystem-errors
Solution
The file-system going read-only issue which has recently been affecting server models MCS-7816-I4, MCS-7825-I4, and MCS-7828-I4 (or their IBM equivilants) in the field is addressed by CSCti52867 - "IBM 7816-I4 and 782x-I4 READONLY file system".
The fix for CSCti52867 is now available and requires the application of two patch files. Install both of these patch files in the order listed below.
1. First install ciscocm.ibm-diskex-1.0.cop.sgn
The Readme file ciscocm.ibm-diskex-1.0.cop.sgn includes installation instructions for this .cop.sgn.
Make sure to only install this utility when show hardware CLI output indicates the array is in a healthy state.
If your server has never had the filesystem go readonly then this step is optional.
2. Next install Cisco-HDD-FWUpdate-3.0.1-I.ISO .
The Readme file Cisco-HDD-FWUpdate-3.0.1-I.Readme.pdf includes installation instructions for this ISO.
This installer is completely independant of the OS installed on the server.
Note: Installing the FWUpdate v3.0(1) or later will get you firmware with the fix for this defect. It is always recommended that you apply the latest FWUCD available for your server.
Refer to the Release Note of CSCti52867 and the Readme file for each of the above mentioned patch files for more details.
Symptoms
The file system goes READONLY, then CUCM services may go down, the server may become "unresponsive" meaning that it is not possible to ssh into the server, login to the console, or web into the server although it may still respond to pings.
Traces from all services stop writing (including syslog)
You see the following error on the server console
EXT3-fs error (device sda6) in start_transaction: Jornal has aborted -
Hi,
This message is posted in "Workstation User" and "Kernel and HW issues" because I'm not sure what the problem is.
I'm having a problem with ext3 partition and I'm not sure if it's a bug o what. It has happened 3 times yesterday (Sunday), before I switched off the computer at night.
Situation
* A computer (no laptop) with 2 HD (hda and hdd) and a few partitions in each disk.
* Hdd has 1 ext3 and 2 xfs.
* Hda has 1 swap (hda1), 2 ext3 and 1 xfs. The two ext3 are "/" (hda5) and /home (hda6). The rests of directories /var /tmp and so are part of "/", on hda5.
* It's a coincidence (or not) but last weekend I made a "pacman –Sy; pacman –Su", and two of the packages updated were "filesystem" and "kernel". The pacman repositories I have configured are "current" and "extra".
The problem
After a few hours working the console shows the following messages:
journal_bmap: journal block not found at offset 25312 on hda5
Aborting journal on device hda5.
ext3_abort called.
EXT3-fs error (device hda5): ext3_journal_start_sb: Detected aborted journal
Remounting filesystem read-only
From that point, a lot of syslog-ng errors because of read-only filesystem, and also erros from other programs (xorg, kde, etc).
Obviously nothing works properly. In hda5 is mounted "/", including /var and /tmp and it's read-only.
The offset referred (25312) is different each time it happened.
First idea
Could it be the hw, physical error? It could, but when I've had problems with hw, there were lots of messages like "seek error", "read error sector ##", "seek complete error", etc.
But in this situation there aren't. And the error is always in hda5, never in hda6 (also ext3) not hda7 (xfs). So I doubt it's a hw problem.
Why not hda6? My opinion, hda5, root fs, is heavily used compared to hda6 (/home). The third time I got the error, I didn't log into any session. Only the OS and services.
Could it be a bug, related to ext3, after the last upgrade?Please don't cross-post:
http://bbs.archlinux.org/viewtopic.php?t=25392
Locking. -
Afternoon,
We have received this error on a switch which resulted in 5 ports being dropped.
2010 Apr 28 20:45:32 Switch144 %KERN-2-SYSTEM_MSG: mts_do_msg_input() failing since no space available in 22 (src_sap = 22, opc = 709)
2010 Apr 28 20:45:32 Switch144 %KERN-2-SYSTEM_MSG: node=1 sap=43 rq=0 lq=0 pq=0 nq=0 sq=0 buf_in_transit=3, bytes_in_transit=1872
2010 Apr 28 20:45:32 Switch144 %KERN-2-SYSTEM_MSG: node=1 sap=18 rq=5 lq=0 pq=1 nq=1 sq=0 buf_in_transit=100509, bytes_in_transit=10854972
2010 Apr 28 20:45:32 Switch144 %KERN-2-SYSTEM_MSG: node=1 sap=41 rq=0 lq=0 pq=1 nq=0 sq=0 buf_in_transit=3, bytes_in_transit=408
2010 Apr 28 20:45:32 Switch144 %KERN-2-SYSTEM_MSG: node=1 sap=19 rq=0 lq=0 pq=0 nq=0 sq=0 buf_in_transit=1, bytes_in_transit=92
2010 Apr 28 20:45:32 Switch144 %KERN-2-SYSTEM_MSG: node=1 sap=22 rq=100504 lq=0 pq=4307 nq=0 sq=0 buf_in_transit=7, bytes_in_transit=980
2010 Apr 28 20:45:32 Switch144 %KERN-2-SYSTEM_MSG: node=2 sap=906 rq=5 lq=0 pq=1 nq=1 sq=0 buf_in_transit=4305, bytes_in_transit=499376
Can anyone shed any light on what could have caused this?
show system health statistics
Test statistics for module 1
Test Name State Frequency Run Pass Fail CFail Errs
InBand Running 5s 2208530 2208530 0 0 0
Bootflash Running 10s 1104319 1104319 0 0 0
Management Port Running 5s 2208530 2208530 0 0 0
Loopback Running 5s 2208530 2208530 0 0 0Afternoon,We have received this error on a switch which resulted in 5 ports being dropped.2010 Apr 28 20:45:32 Switch144 %KERN-2-SYSTEM_MSG: mts_do_msg_input() failing since no space available in 22 (src_sap = 22, opc = 709)2010 Apr 28 20:45:32 Switch144 %KERN-2-SYSTEM_MSG: node=1 sap=43 rq=0 lq=0 pq=0 nq=0 sq=0 buf_in_transit=3, bytes_in_transit=18722010 Apr 28 20:45:32 Switch144 %KERN-2-SYSTEM_MSG: node=1 sap=18 rq=5 lq=0 pq=1 nq=1 sq=0 buf_in_transit=100509, bytes_in_transit=108549722010 Apr 28 20:45:32 Switch144 %KERN-2-SYSTEM_MSG: node=1 sap=41 rq=0 lq=0 pq=1 nq=0 sq=0 buf_in_transit=3, bytes_in_transit=4082010 Apr 28 20:45:32 Switch144 %KERN-2-SYSTEM_MSG: node=1 sap=19 rq=0 lq=0 pq=0 nq=0 sq=0 buf_in_transit=1, bytes_in_transit=922010 Apr 28 20:45:32 Switch144 %KERN-2-SYSTEM_MSG: node=1 sap=22 rq=100504 lq=0 pq=4307 nq=0 sq=0 buf_in_transit=7, bytes_in_transit=9802010 Apr 28 20:45:32 Switch144 %KERN-2-SYSTEM_MSG: node=2 sap=906 rq=5 lq=0 pq=1 nq=1 sq=0 buf_in_transit=4305, bytes_in_transit=499376 Can anyone shed any light on what could have caused this?
show system health statistics
Test statistics for module 1
Test Name State Frequency Run Pass Fail CFail Errs
InBand Running 5s 2208530 2208530 0 0 0
Bootflash Running 10s 1104319 1104319 0 0 0
Management Port Running 5s 2208530 2208530 0 0 0
Loopback Running 5s 2208530 2208530 0 0 0
Hi,
For the above errors check out the information from cisco interpertor
ERROR:%KERN-2-SYSTEM_MSG: EXT3-fs error (device ide1(22,4)): ext3_readdir: directory #2 contains a hole at offset 0
Explanation: Zoning changes or configuration cannot be saved. EXT3-fs filesystemis mounted in read-only mode. The above error message indicates a hole at offsetXX in filesystem. The above condition happens, system software issues a soft resetto the device. System health also issues a soft reset. Such multiple reset requestsconfuse the driver software completely, driver stops responding. This is possibly due to the known software bugs CSCeg75552, CSCse28623, CSCse36768.
Recommended Action: A system switchover in the case of dual supervisors or a reload of the supervisor should fix the problem.
Hope to Help !!
Ganesh.H
Remember to rate the helpful post -
Install Oracle 11gR2 Express Edition on Ubuntu Linux 11.04 (64-bit) Howto
h2. Install Oracle 11gR2 Express Edition on Ubuntu Linux 11.04 (64-bit) Howto
Version: B
Author: Dude, 24. May 2011
The following are step by step instructions how to install Oracle 11gR2 Express Edition (Beta) under Linux Ubuntu 11.04, 64-bit.
Access to the Internet is required.
The instructions cover the following additional topics:
- Converting Red Hat based Oracle XE installer to Ubuntu.
- Work-around for missing /sbin/chkconfig tool.
- Install Oracle XE into a different directory or disk volume.
- Relocate and configure the Oracle user and default login directory.
- Uninstall, reconfigure and perform first database backup.
- Notes and web links.
- Troubleshooting
h3. A) System Setup and Prerequisites
h4. A.1. System Access
You will need terminal command line, root and system console access to perform the setup tasks.
To open a Terminal at the system console:
Menu Applications > Accessories > TerminalThe following commands will enable remote ssh login with root access:
sudo apt-get install openssh-server
sudo passwd root
Verify:
ssh root@xe_server_host_nameh4. A.2. Software Prerequisites
The following is required in order to install Oracle 11gR2 XE:
sudo apt-get install alien libaio1 unixodbcThe following is not required, but it will fix backspace and arrow keys in case you prefer using the vi-editor:
sudo apt-get install vimh4. A.3. System Swap space
Minimum swap space required is 2 GB. You can increase swap space if necessary using a swap file:
To analyze current swap space and memory configuration:
sudo cat /proc/meminfo
To install a 1 GB swapfile named swapfile in /, for example:
sudo dd if=/dev/zero of=/swapfile bs=1024 count=1048576
(this may take a while)
sudo mkswap /swapfile
sudo swapon /swapfile
sudo cp /etc/fstab /etc/fstab.orig
sudo echo '/swapfile swap swap defaults 0 0' >> /etc/fstab
Verify:
sudo swapon -a
sudo swapon -sh4. A.4. Kernel Parameters
Oracle 11g XE requires the following additional kernel parameters:
sudo nano /etc/sysctl.d/60-oracle.conf
(Enter the following)
# Oracle 11g XE kernel parameters
fs.file-max=6815744
net.ipv4.ip_local_port_range=9000 65000
kernel.sem=250 32000 100 128
kernel.shmmax=536870912
(Save the file)
Note: kernel.shmmax = max possible value, e.g. size of physical RAM.
Verify: sudo cat /etc/sysctl.d/60-oracle.conf
Load new kernel parameters:
sudo service procps start
Verify:
sudo sysctl -q fs.file-max
-> fs.file-max = 6815744h4. A.5. Oracle Installation Directory
The current Oracle Installation Guide uses the same directory like in previous versions: /usr/lib/oracle/xe/app/oracle/product/11.2.0/server. However, the current Beta installation uses Oracle Flexible Architecture (OFA) and installs into /u01/app/oracle/product/11.2.0/xe. Due to size limitations of Oracle XE it may not be necessary to store the installation to a specific directory or separate volume, but it is possible:
Install Oracle XE to separate disk volume:
From the system console menu: System > Administration > Disk Utility
Select "ext3" filesystem for Oracle compatibility and specify a Volume label, e.g. Oracle.
Notice the device name e.g. /dev/sdb
Get the drive UUID:
sudo blkid
e.g. /dev/sdb: UUID="d19a2d8f-da43-4802-8bdb-0703c855e23a"
Modify /etc/fstab to automatically mount the volume at system startup:
sudo cp /etc/fstab /etc/fstab.original
sudo nano /etc/fstab
(Add the following, using determined UUID, for exmple)
UUID=d19a2d8f-da43-4802-8bdb-0703c855e23a /u01 ext3 defaults,errors=remount-ro 0 1
(Save the file)
Create the mount-point, mount the new volume and set ownership and privileges:
sudo mkdir /u01
sudo mount -a
sudo chown root:root /u01
sudo chmod 755 /u01
Verify:
df -h
or restart the systemYou can also install Oracle XE into a specific directory:
Create a symbolic link to store the installation into an existing directory, for instance:
sudo mkdir /home/oracle-xe
sudo ln -s /home/oracle-xe /u01h3. C) Oracle 11g XE Download and Installation
h4. C.1. Download and convert the Installer from Red Hat to Ubuntu
Please see section E.3. to download the Oracle 11gR2 XE installer.
Select the version listed for Linux x64.
sudo unzip linux.x64_11gR2_OracleXE.zip
sudo alien --to-deb --scripts oracle-xe-11.2.0-0.5.x86_64.rpm
(This may take a while)h4. C.2. Create a special chkconfig script
The Red Hat based installer of Oracle XE 11gR2 beta relies on +/sbin/chkconfig+, which is not used in Ubuntu. The chkconfig package available for the current version of Ubuntu produces errors and my not be safe to use. Below is a simple trick to get around the problem and install Oracle XE successfully:
Create /sbin/chconfig:
sudo nano /sbin/chkconfig
(Cut and paste the following)
#!/bin/bash
# Oracle 11gR2 XE installer chkconfig hack for Debian by Dude
file=/etc/init.d/oracle-xe
if [[ ! `tail -n1 $file | grep INIT` ]]; then
echo >> $file
echo '### BEGIN INIT INFO' >> $file
echo '# Provides: OracleXE' >> $file
echo '# Required-Start: $remote_fs $syslog' >> $file
echo '# Required-Stop: $remote_fs $syslog' >> $file
echo '# Default-Start: 2 3 4 5' >> $file
echo '# Default-Stop: 0 1 6' >> $file
echo '# Short-Description: Oracle 11g Express Edition' >> $file
echo '### END INIT INFO' >> $file
fi
update-rc.d oracle-xe defaults 80 01
(Save the file)
Set appropriate execute privileges:
chmod 755 /sbin/chkconfig
Note: You should remove the /sbin/chkconfig file after successful installation of Oracle XE.
h4. C.3. Install and configure Oracle XE
sudo dpkg --install ./oracle-xe_11.2.0-1.5_amd64.deb
/etc/init.d/oracle-xe configure
(This will take a while)
Remove the /sbin/chkconfig script, which is no longer needed.
sudo rm /sbin/chkconfigh4. C.4. Relocate and Configure the Oracle user login
The Oracle XE installer specifies /u01/app/oracle as the login directory for the Oracle user. Although not really necessary, the following will relocate the Oracle user $HOME to a standard location and create standard /etc/skel login files:
Exit all Oracle user sessions:
sudo /etc/init.d/oracle-xe stop
sudo kill -9 `ps -ef | grep oracle | grep -v grep | awk '{print $2}'`
sudo userdel oracle
sudo useradd -s /bin/bash -G dba -g dba -m oracle
sudo passwd oracle
Verify:
sudo id oracle
-> uid=1001(oracle) gid=1001(dba) groups=1001(dba)h4. C.5. Setup Oracle environment variables
In order to use sqlplus and other tools, the Oracle account requires certain environment variables. The following will set these variables automatically at every interactive Oracle login:
sudo echo '. /u01/app/oracle/product/11.2.0/xe/bin/oracle_env.sh' >> /home/oracle/.bashrch4. C.6. Oracle sudo root access
It is not essential to allow the Oracle user to use sudo, but it is convenient:
usermod -G admin oracle
Verify:
id oracle
-> uid=1001(oracle) gid=1001(dba) groups=1001(dba),120(admin)
sudo su -
-> Enter Oracle account passwordh4. C.7. Oracle 11g XE Post-installation
After you install Oracle Database XE, its graphical user interface is only available from the local server, but not remotely.
The following will correct the problem if necessary:
Login as user Oracle or use:
su - oracle
sqlplus / as sysdba
At the SQL prompt, enter the following command:
EXEC DBMS_XDB.SETLISTENERLOCALACCESS(FALSE);
exith3. D) Unintstall, Reconfigure and Troubleshooting
h4. D.1. Uninstall Oracle 11g XE
The following will completely uninstall and remove Oracle 11g XE:
Login as user root:
sudo su -
/etc/init.d/oracle-xe stop
dpkg --purge oracle-xe
rm -r /u01/app
rm /etc/default/oracle-xe
update-rc.d -f oracle-xe removeh4. D.2. Reconfigure Oracle 11g XE
Type the following in a terminal window:
/etc/init.d/oracle-xe stop
sudo rm /etc/default/oracle-xe
/etc/init.d/oracle-xe configureh4. D.3. Enable Archivelog mode and perform a database backup
Login as user Oracle:
su - oracle
sqlplus / as sysdba
At the SQL prompt, enter the following commands:
shutdown immediate
startup mount
alter database archivelog;
alter database open;
exit
Login to system console of the Oracle user account:
Select Applications > Oracle Database 11g Express Edition > Backup Databaseh3. E) Notes
h4. E.1. Oracle 11g XE limitiations overview
- It will consume, at most, processing resources equivalent to one CPU.
- Only one installation of Oracle Database XE can be performed on a single computer.
- The maximum amount of user data in an Oracle Database XE database cannot exceed 11 GB.
- The maximum amount of RAM that Oracle XE uses cannot exceed 1 GB, even if more is available.
- HTTPS is not supported natively with the HTTP listener built into Oracle Database XE.
h4. E.2. Documentation and Links
Official documentation for Oracle 11gR2 XE can be found at:
http://www.oracle.com/pls/xe112/homepage
h4. E.3. Oracle 11g XE downloads
The Installer is available from the Oracle Technology Network at:
http://www.oracle.com/technology/products/database/xe
http://www.oracle.com/technetwork/database/express-edition/downloads/index.html
h4. E.4 APEX links and archives
The APEX archives can be found at:
http://www.oracle.com/technetwork/developer-tools/apex/application-express/all-archives-099381.html
The APEX download site is:
http://www.oracle.com/technetwork/developer-tools/apex/downloads/index.html
h3. F) Troubleshooting
... in progress
Regards and best of luck!
Edited by: Dude on May 25, Version B: various corrections. chkconfig package (A.2.) not required.even though I am admin user.Admin user is a MS Windows term, that does not apply to Linux or Unix in the same fashion.
The configuration script tells you "You must be root user to run the configure script. Login as root user and
then run the configure script."
This is most likely correct because your account is not root and does not have UID 0. What you can do is to login as root e.g. sudo su -, as the message suggest, or use "sudo /etc/init.d/oracle-xe configure", provided your account is defined in the /etc/sudoers file to perform root/admin actions.
Btw, do not modify /etc/passwd and /etc/group to give you admin privileges or try to create a another root account under a different name. That's not the way it works and usually leads to nasty problems. -
How to gain access to second Linux partition
Hi,
Before I start, I'd just like to say how impressed I am with Arch! I've only been using it for a week now, a bit less in fact, but it's already wowing me enough to make me think about changing my loyalties from Debian to Arch - something I thought would be impossible even a few weeks back!
Anyway, my problem is, should be a simple one this, how to access my Arch partition from Debian and vice versa. In Debian, I can see the Arch partition in Dolphin, but when I click on it I get a permission denied message. When I try to mount this device (in Dolphin not with the command line) I get the same message. Now, in the bad old days when I shared my Linux computer with Windows, I was able to access my FAT32 partition by simply going into /media, finding the partition (let's say hda2) and chmod-ing it, ie chmod 0777 /media/hda2. I wanted to see if this would work with my Arch partition, but I don't even see it in /media/ Instead I went into /dev and tried changing permission there, but to no avail. I've tried tinkering around with the fstab file, but I'm very much an amateur at this, and now I don't know what to try. Here is the result of fdisk -l (hda1 is Debian):
Disk /dev/hda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hda1 * 1 7047 56604996 83 Linux
/dev/hda2 9447 9729 2273197+ 5 Extended
/dev/hda3 7048 9446 19269967+ 83 Linux
/dev/hda5 9447 9729 2273166 82 Linux swap / Solaris
And here is the fstab file (I have myself entered the line for hda3):
debian:/home/james# cat /etc/fstab
# /etc/fstab: static file system information.
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
/dev/hda1 / ext3 defaults,errors=remount-ro 0 1
/dev/hda3 / ext3 defaults, errors=remount-ro 0 0 2
/dev/hda5 none swap sw 0 0
/dev/hdc /media/cdrom0 udf,iso9660 user,noauto 0 0
/dev/hdd /media/cdrom1 udf,iso9660 user,noauto 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto 0 0
/dev/sdb1 /media/usb0 vfat rw,user,users,noauto,noatime,noauto 1 2
Can anyone help me with this?
Thanks a lot in advance.Thanks for your reply toliman. I've tried doing what you suggested but it still doesn't work. Here is my new fstab file:
# /etc/fstab: static file system information.
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
/dev/hda1 / ext3 defaults,errors=remount-ro 0 1
/dev/hda3 /media/arch ext3 defaults, errors=remount-ro 0 0 2
/dev/hda5 none swap sw 0 0
/dev/hdc /media/cdrom0 udf,iso9660 user,noauto 0 0
/dev/hdd /media/cdrom1 udf,iso9660 user,noauto 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto 0 0
/dev/sdb1 /media/usb0 vfat rw,user,users,noauto,noatime,noauto 1 2
And here is the result of ls -l /media:
drwxr-xr-x 2 root root 4096 2008-05-14 16:43 arch
lrwxrwxrwx 1 root root 6 2007-06-07 17:13 cdrom -> cdrom0
drwxr-xr-x 2 root root 4096 2007-06-07 17:13 cdrom0
drwxr-xr-x 2 root root 4096 2007-06-07 17:13 cdrom1
lrwxrwxrwx 1 root root 7 2007-06-07 17:13 floppy -> floppy0
drwxr-xr-x 2 root root 4096 2007-06-07 17:13 floppy0
drwxr-xr-x 2 root root 4096 2008-04-03 14:17 IOMEGA_HDD
drwxr-xr-x 2 root root 4096 2008-01-10 14:56 sda1
drwxrwxrwx 2 root cdrom 4096 2007-12-15 20:44 usb0
Still the same issues: pemissions denied when I try to open or mount hda/3 with dolphin. When I try to mount as root using the command line I get:
debian:/home/james# mount /dev/hda3
[mntent]: line 6 in /etc/fstab is bad
mount: can't find /dev/hda3 in /etc/fstab or /etc/mtab
Thanks once again. -
Hard disk failing -- how to safely backup data / remove bad sectors?
I'm sorry if this is posted in the wrong forums, I wasn't sure where to go.
It appears that I have a bad block on my hard drive. During normal boot-up, arch ran its regular scan of my / partition, and failed giving an error that looked something like:
Error reading block 13303898 (something here about a short read) while getting next inode from scan.
It then let me login as root for maintenance and mounted / as read only. By doing some work with du, I was able to narrow the problem to a bunch of files in a single folder. Attempting to access them with du gave the error
Ext3-fs error (device sda4): ext3_get_inode_loc: unable to read inode block - inode=3328795, block=13303898
The block was the same for all of the bad files, although the inode changed.
First question (probably the most important): Is it safe to mount my hard drive in read-write mode to try to backup my data? If I do so, what is the best way to proceed?
Second question (hopeful here, but not optimistic): The folder with the bad block is not critical at all. I've had the harddrive for less than a year, so I'm hoping it just got bumped and isn't completely dying. I'd like to think I can back up my data, use some software to ignore the bad block, and go on my merry way using the rest of my hard drive. Is this feasible or even possible? If so, how would I go about fixing this?
(Sigh) all of this the week before my final exams too, with critical data on the hard drive. Oh well, when it rains it pours I guess...I would backup all the data I could to another HD, then I would zero de drive with dd and try to read it back with dd and see if it complains.
It may be a transient problem due to a failed write and not a physical problem.
Something similar happened to me before. But either way if dd solves your problem I would still keep a close eye on that disk. -
Hello
Does anybody experience some weird issue related with external hard drive enlosures?
In my case I have experienced this problem 2nd time.
First was enclosure for single 5.25" SATA Samsung, then IcyBox for 2x 5.25" SATA drives (USB interfaces)
In both examples after a while something strange is happening. During normal operation suddenly Samsung hard drive is disconnecting together with noise of slowing drive. I had to remount the drive. I replaced the enclosure, because I was suspecting SATA controller failure.
In new IcyBox enclosure hard drive was operating without issues for 4-5 months. Now is happening the same, but more frequent (few times a day) for Samsung drive.
I replaced Samsung for Hitachi to test the situation. Same thing happened!
I'm really confused about this all crap enclosures. IcyBox cost me ~55 pounds, but later I faced not small drawbacks related to SATA controller (different manufacturer). Second drawer in this enclosure does not detect any hard drive.
Is it some kind of USB module drawbacks that cause these hard drive restarts? I can't use eSATA, because my laptop does not have it.
Please share your experience about enclosures and suggest some good brands, because I want to deal with it once and for all. I know "Think before you buy". In our times there is a lot of failing or half-products on the market.
Thank you
P.S.
I'll try to find something interesting in my logs.
Last edited by Kardell (2010-06-09 22:37:06).:B:. wrote:Do your enclosures get enough power? Sometimes the power one USB connector can give is not enough and you need either a second one (some manufacturers have special cables for that) or an external power source. I have some Icy Box enclosures too, and they frequently exhibit this behaviour. Really depends on the system they're connected to it seems, but as soon as they get a second power source the problem's gone.
Yes. Both enclosures have external power supplies plugged to the wall outlet.
The thing is that these enclosures are connected to my laptop via 2x3m USB cables.
But I don't think so that such distance can cause these issues. I know that USB repeater is required after about 5m of a cable.
But who knows, maybe in these circumstances something bad is happening too.
kernel.log
Jun 9 21:00:01 skywalker kernel: EXT3-fs error (device sde5): ext3_find_entry: reading directory #2 offset 0
Jun 9 21:00:01 skywalker kernel: EXT3-fs error (device sde6): ext3_find_entry: reading directory #2 offset 0
Jun 9 21:00:01 skywalker kernel: EXT3-fs error (device sde6): ext3_find_entry: reading directory #2 offset 0
Jun 9 21:00:01 skywalker kernel: EXT3-fs error (device sde8): ext3_find_entry: reading directory #2 offset 0
Jun 9 21:03:26 skywalker kernel: usb 2-1: USB disconnect, address 8
Jun 9 21:50:43 skywalker kernel: usb 2-2: USB disconnect, address 4
Jun 9 21:50:43 skywalker kernel: EXT3-fs error (device sde5): ext3_find_entry: reading directory #2 offset 0
Jun 9 21:50:43 skywalker kernel: EXT3-fs error (device sde5): ext3_find_entry: reading directory #2 offset 0
Jun 9 21:50:43 skywalker kernel: EXT3-fs error (device sde6): ext3_find_entry: reading directory #2 offset 0
Jun 9 21:50:43 skywalker kernel: EXT3-fs error (device sde6): ext3_find_entry: reading directory #2 offset 0
Jun 9 21:50:43 skywalker kernel: EXT3-fs error (device sde8): ext3_find_entry: reading directory #2 offset 0
Jun 9 21:50:43 skywalker kernel: EXT3-fs error (device sdd2): ext3_find_entry: reading directory #2 offset 0
Jun 9 21:50:43 skywalker kernel: EXT3-fs error (device sdd1): ext3_find_entry: reading directory #2 offset 0
Jun 9 23:48:23 skywalker kernel: EXT3-fs error (device sdd1): ext3_find_entry: reading directory #2 offset 0
Jun 9 23:48:23 skywalker kernel: EXT3-fs error (device sde5): ext3_find_entry: reading directory #2 offset 0
Jun 9 23:48:23 skywalker kernel: EXT3-fs error (device sde5): ext3_find_entry: reading directory #2 offset 0
Jun 9 23:48:23 skywalker kernel: EXT3-fs error (device sde6): ext3_find_entry: reading directory #2 offset 0
Jun 9 23:48:23 skywalker kernel: EXT3-fs error (device sde6): ext3_find_entry: reading directory #2 offset 0
Jun 9 23:48:23 skywalker kernel: EXT3-fs error (device sde8): ext3_find_entry: reading directory #2 offset 0
Jun 9 23:48:23 skywalker kernel: EXT3-fs error (device sdd2): ext3_find_entry: reading directory #2 offset 0
Jun 9 23:51:06 skywalker kernel: EXT3-fs error (device sdd1): ext3_find_entry: reading directory #2 offset 0
Jun 9 23:54:18 skywalker kernel: usbcore: deregistering interface driver oss_usb
Jun 9 21:00:01 skywalker kernel: EXT3-fs error (device sde5): ext3_find_entry: reading directory #2 offset 0
Jun 9 21:00:01 skywalker kernel: EXT3-fs error (device sde6): ext3_find_entry: reading directory #2 offset 0
Jun 9 21:00:01 skywalker kernel: EXT3-fs error (device sde6): ext3_find_entry: reading directory #2 offset 0
Jun 9 21:00:01 skywalker kernel: EXT3-fs error (device sde8): ext3_find_entry: reading directory #2 offset 0
Jun 9 21:03:26 skywalker kernel: usb 2-1: USB disconnect, address 8
Jun 9 21:50:43 skywalker kernel: usb 2-2: USB disconnect, address 4
Jun 9 21:50:43 skywalker kernel: EXT3-fs error (device sde5): ext3_find_entry: reading directory #2 offset 0
Jun 9 21:50:43 skywalker kernel: EXT3-fs error (device sde5): ext3_find_entry: reading directory #2 offset 0
Jun 9 21:50:43 skywalker kernel: EXT3-fs error (device sde6): ext3_find_entry: reading directory #2 offset 0
Jun 9 21:50:43 skywalker kernel: EXT3-fs error (device sde6): ext3_find_entry: reading directory #2 offset 0
Jun 9 21:50:43 skywalker kernel: EXT3-fs error (device sde8): ext3_find_entry: reading directory #2 offset 0
Jun 9 21:50:43 skywalker kernel: EXT3-fs error (device sdd2): ext3_find_entry: reading directory #2 offset 0
Jun 9 21:50:43 skywalker kernel: EXT3-fs error (device sdd1): ext3_find_entry: reading directory #2 offset 0
Jun 9 23:48:23 skywalker kernel: EXT3-fs error (device sdd1): ext3_find_entry: reading directory #2 offset 0
Jun 9 23:48:23 skywalker kernel: EXT3-fs error (device sde5): ext3_find_entry: reading directory #2 offset 0
Jun 9 23:48:23 skywalker kernel: EXT3-fs error (device sde5): ext3_find_entry: reading directory #2 offset 0
Jun 9 23:48:23 skywalker kernel: EXT3-fs error (device sde6): ext3_find_entry: reading directory #2 offset 0
Jun 9 23:48:23 skywalker kernel: EXT3-fs error (device sde6): ext3_find_entry: reading directory #2 offset 0
Jun 9 23:48:23 skywalker kernel: EXT3-fs error (device sde8): ext3_find_entry: reading directory #2 offset 0
Jun 9 23:48:23 skywalker kernel: EXT3-fs error (device sdd2): ext3_find_entry: reading directory #2 offset 0
Jun 9 23:51:06 skywalker kernel: EXT3-fs error (device sdd1): ext3_find_entry: reading directory #2 offset 0
Jun 9 23:54:18 skywalker kernel: usbcore: deregistering interface driver oss_usb
Last edited by Kardell (2010-06-10 17:54:37) -
[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) -
INode problem in SUSE 11 SP1 for SAP
Dear Experts,
We are now preparing server for our new BW Productive instance, with the following specs:
- server x3850
- storage V7000
- SUSE 11 SP 1 (2.6.32.49-0.3-default #1 SMP 2011-12-02 11:28:04 +0100 x86_64 x86_64 x86_64 GNU/Linux)
We use EXT3 for the fs type with just only allocating one VG, size 5,5TB. The problem is:
every time we copy file from mounted folder to the file system, let say DB2, it ended with the following result:
-????????? ? ? ? ? ? home.bd1adm.tar
the file is corrupt after copying and restarting the system
the messages log contains:
Jan 16 15:36:25 tdsbwdev xinetd[11067]: Started working: 2 available services
Jan 16 15:36:25 tdsbwdev kernel: [ 57.746711] pci 0000:03:00.0: Invalid ROM contents
Jan 16 15:36:25 tdsbwdev kernel: [ 57.746892] pci 0000:03:00.0: Invalid ROM contents
Jan 16 15:36:25 tdsbwdev kernel: [ 57.747067] pci 0000:03:00.0: Invalid ROM contents
Jan 16 15:36:25 tdsbwdev kernel: [ 57.747241] pci 0000:03:00.0: Invalid ROM contents
Jan 16 15:36:25 tdsbwdev kernel: [ 57.747415] pci 0000:03:00.0: Invalid ROM contents
Jan 16 15:36:25 tdsbwdev kernel: [ 57.747588] pci 0000:03:00.0: Invalid ROM contents
Jan 16 15:36:25 tdsbwdev kernel: [ 57.747762] pci 0000:03:00.0: Invalid ROM contents
Jan 16 15:36:25 tdsbwdev kernel: [ 57.747936] pci 0000:03:00.0: Invalid ROM contents
Jan 16 15:36:25 tdsbwdev kernel: [ 57.748152] pci 0000:03:00.0: Invalid ROM contents
Jan 16 15:36:30 tdsbwdev gdm-simple-greeter[11245]: GLib-GObject-CRITICAL: g_param_spec_flags: assertion `G_TYPE_IS_FLAGS (flags_type)' failed
Jan 16 15:36:30 tdsbwdev gdm-simple-greeter[11245]: GLib-GObject-CRITICAL: g_object_class_install_property: assertion `G_IS_PARAM_SPEC (pspec)' failed
Jan 16 15:36:30 tdsbwdev pulseaudio[11252]: module.c: module-hal-detect is deprecated: Please use module-udev-detect instead of module-hal-detect!
Jan 16 15:36:32 tdsbwdev kernel: [ 64.352048] eth2: no IPv6 routers present
Jan 16 15:36:35 tdsbwdev gdm-session-worker[11247]: WARNING: gdm_session_settings_load: lang = (null)
Jan 16 15:36:38 tdsbwdev checkproc: checkproc: can not get session id for process 10862!
Jan 16 15:36:42 tdsbwdev pulseaudio[11442]: pid.c: Stale PID file, overwriting.
Jan 16 15:36:42 tdsbwdev pulseaudio[11442]: module.c: module-hal-detect is deprecated: Please use module-udev-detect instead of module-hal-detect!
Jan 16 15:37:11 tdsbwdev kernel: [ 103.074143] EXT3-fs error (device dm-18): ext3_lookup: deleted inode referenced: 12
Jan 16 15:37:46 tdsbwdev kernel: [ 138.207724] ide-cd driver 5.00
Jan 16 15:37:46 tdsbwdev kernel: [ 138.232491] st: Version 20081215, fixed bufsize 32768, s/g segs 256
Jan 16 15:37:46 tdsbwdev kernel: [ 138.323747] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Jan 16 15:37:46 tdsbwdev kernel: [ 138.323751] EDD information not available.
Jan 16 15:40:00 tdsbwdev multipathd: dm-22: add map (uevent 4232)
Jan 16 15:40:02 tdsbwdev sshd[12550]: Accepted keyboard-interactive/pam for root from 10.63.61.90 port 4162 ssh2
Jan 16 15:40:07 tdsbwdev kernel: [ 279.247416] EXT3-fs error (device dm-18): ext3_lookup: deleted inode referenced: 12
Jan 16 15:40:18 tdsbwdev kernel: [ 290.801925] kjournald starting. Commit interval 15 seconds
Jan 16 15:40:18 tdsbwdev kernel: [ 290.802250] EXT3 FS on dm-22, internal journal
Jan 16 15:40:18 tdsbwdev kernel: [ 290.802258] EXT3-fs: mounted filesystem with ordered data mode.
Jan 16 15:40:28 tdsbwdev kernel: [ 300.938467] EXT3-fs error (device dm-18): ext3_lookup: deleted inode referenced: 12
Jan 16 15:40:34 tdsbwdev kernel: [ 306.912355] EXT3-fs error (device dm-18): ext3_lookup: deleted inode referenced: 12
Jan 16 15:40:54 tdsbwdev kernel: [ 326.758056] EXT3-fs error (device dm-18): ext3_lookup: deleted inode referenced: 12
Jan 16 15:41:13 tdsbwdev kernel: [ 345.147993] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Jan 16 15:41:13 tdsbwdev kernel: [ 345.147996] EDD information not available.
Jan 16 15:41:27 tdsbwdev kernel: [ 359.123438] EXT3-fs error (device dm-18): ext3_lookup: deleted inode referenced: 12
Jan 16 15:42:08 tdsbwdev kernel: [ 400.822663] EXT3-fs error (device dm-18): ext3_lookup: deleted inode referenced: 12
Jan 16 15:42:43 tdsbwdev rpc.statd[13824]: Version 1.2.1 Starting
Jan 16 15:42:43 tdsbwdev rpc.statd[13824]: Flags:
Jan 16 15:42:43 tdsbwdev rpc.statd[13824]: statd running as root. chown /var/lib/nfs/sm to choose different user
Jan 16 15:42:43 tdsbwdev kernel: [ 435.807748] ip_tables: (C) 2000-2006 Netfilter Core Team
Jan 16 15:42:43 tdsbwdev kernel: [ 435.879502] RPC: Registered udp transport module.
Jan 16 15:42:43 tdsbwdev kernel: [ 435.879505] RPC: Registered tcp transport module.
Jan 16 15:42:43 tdsbwdev kernel: [ 435.879506] RPC: Registered tcp NFSv4.1 backchannel transport module.
Jan 16 15:42:43 tdsbwdev kernel: [ 435.896769] Slow work thread pool: Starting up
Jan 16 15:42:43 tdsbwdev kernel: [ 435.896904] Slow work thread pool: Ready
Jan 16 15:42:43 tdsbwdev kernel: [ 435.897571] FS-Cache: Loaded
Jan 16 15:42:43 tdsbwdev kernel: [ 435.915961] FS-Cache: Netfs 'nfs' registered for caching
Jan 16 15:44:32 tdsbwdev polkit-grant-helper[14116]: granted authorization for org.freedesktop.consolekit.system.restart to pid 11275 [uid=0] [auth=root]
Jan 16 15:44:33 tdsbwdev console-kit-daemon[9170]: GLib-GObject-WARNING: IA__g_object_get_valist: value location for `gchararray' passed as NULL
Jan 16 15:44:33 tdsbwdev shutdown[14125]: shutting down for system reboot
Jan 16 15:44:34 tdsbwdev kernel: [ 546.139405] pci 0000:03:00.0: Invalid ROM contents
Jan 16 15:44:34 tdsbwdev kernel: [ 546.139583] pci 0000:03:00.0: Invalid ROM contents
Jan 16 15:44:34 tdsbwdev kernel: [ 546.139757] pci 0000:03:00.0: Invalid ROM contents
Jan 16 15:44:34 tdsbwdev kernel: [ 546.139953] pci 0000:03:00.0: Invalid ROM contents
Jan 16 15:44:34 tdsbwdev kernel: [ 546.140172] pci 0000:03:00.0: Invalid ROM contents
Jan 16 15:44:34 tdsbwdev kernel: [ 546.140348] pci 0000:03:00.0: Invalid ROM contents
Jan 16 15:44:34 tdsbwdev kernel: [ 546.140522] pci 0000:03:00.0: Invalid ROM contents
Jan 16 15:44:34 tdsbwdev kernel: [ 546.140697] pci 0000:03:00.0: Invalid ROM contents
Jan 16 15:44:34 tdsbwdev kernel: [ 546.140870] pci 0000:03:00.0: Invalid ROM contents
Jan 16 15:44:34 tdsbwdev init: Switching to runlevel: 6
Jan 16 15:44:35 tdsbwdev pulseaudio[14222]: module.c: module-hal-detect is deprecated: Please use module-udev-detect instead of module-hal-detect!
Jan 16 15:44:35 tdsbwdev gdm-simple-greeter[14203]: GLib-GObject-CRITICAL: g_param_spec_flags: assertion `G_TYPE_IS_FLAGS (flags_type)' failed
Jan 16 15:44:35 tdsbwdev gdm-simple-greeter[14203]: GLib-GObject-CRITICAL: g_object_class_install_property: assertion `G_IS_PARAM_SPEC (pspec)' failed
Jan 16 15:44:36 tdsbwdev kernel: [ 547.943213] bootsplash: status on console 0 changed to on
Jan 16 15:44:36 tdsbwdev auditd[10010]: The audit daemon is exiting.
Jan 16 15:44:36 tdsbwdev multipathd: mpathc: stop event checker thread (140491298486032)
Jan 16 15:44:36 tdsbwdev multipathd: mpathb: stop event checker thread (140491298334480)
Jan 16 15:44:36 tdsbwdev multipathd: mpathd: stop event checker thread (140491298301712)
Jan 16 15:44:36 tdsbwdev multipathd: mpathe: stop event checker thread (140491298268944)
Jan 16 15:44:36 tdsbwdev multipathd: mpathf: stop event checker thread (140491298236176)
Jan 16 15:44:36 tdsbwdev multipathd: mpathg: stop event checker thread (140491298203408)
Jan 16 15:44:36 tdsbwdev multipathd: mpathi: stop event checker thread (140491298170640)
Jan 16 15:44:36 tdsbwdev multipathd: mpathj: stop event checker thread (140491298137872)
Jan 16 15:44:36 tdsbwdev multipathd: mpathk: stop event checker thread (140491298105104)
Jan 16 15:44:36 tdsbwdev multipathd: mpathh: stop event checker thread (140491298072336)
Jan 16 15:44:36 tdsbwdev multipathd: -
shut down-------
Jan 16 15:44:37 tdsbwdev sshd[10835]: Received signal 15; terminating.
Jan 16 15:44:38 tdsbwdev xinetd[11067]: Exiting...
Jan 16 15:44:40 tdsbwdev rpc.statd[13824]: Caught signal 15, un-registering and exiting.
Jan 16 15:44:40 tdsbwdev rpcbind: rpcbind terminating on signal. Restart with "rpcbind -w"
Jan 16 15:44:40 tdsbwdev kernel: Kernel logging (proc) stopped.
Jan 16 15:44:40 tdsbwdev kernel: Kernel log daemon terminating.
Jan 16 15:44:40 tdsbwdev syslog-ng[8182]: Termination requested via signal, terminating;
Jan 16 15:44:40 tdsbwdev syslog-ng[8182]: syslog-ng shutting down; version='2.0.9'
Jan 16 15:48:53 tdsbwdev syslog-ng[7872]: syslog-ng starting up; version='2.0.9'
Jan 16 15:48:53 tdsbwdev firmware.sh[7899]: Cannot find firmware file 'intel-ucode/06-2f-02'
Jan 16 15:48:53 tdsbwdev firmware.sh[7904]: Cannot find firmware file 'intel-ucode/06-2f-02'
Jan 16 15:48:53 tdsbwdev firmware.sh[7911]: Cannot find firmware file 'intel-ucode/06-2f-02'
Jan 16 15:48:53 tdsbwdev firmware.sh[7918]: Cannot find firmware file 'intel-ucode/06-2f-02'
Jan 16 15:48:53 tdsbwdev firmware.sh[7925]: Cannot find firmware file 'intel-ucode/06-2f-02'
Jan 16 15:48:53 tdsbwdev firmware.sh[7932]: Cannot find firmware file 'intel-ucode/06-2f-02'
Jan 16 15:48:56 tdsbwdev ifup: No configuration found for eth0
Jan 16 15:48:56 tdsbwdev ifup: eth1 device: ServerEngines Corp. Emulex OneConnect 10Gb NIC (be3) (rev 02)
Jan 16 15:48:56 tdsbwdev ifup: No configuration found for eth1
Jan 16 15:48:56 tdsbwdev ifup: eth2 device: Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet (rev 20)
Jan 16 15:48:56 tdsbwdev ifup: eth2
Jan 16 15:48:56 tdsbwdev ifup: IP address: 10.66.2.30/24
Jan 16 15:48:56 tdsbwdev ifup:
Jan 16 15:48:56 tdsbwdev SuSEfirewall2: SuSEfirewall2 not active
Jan 16 15:48:56 tdsbwdev ifup: eth3 device: Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet (rev 20)
Jan 16 15:48:56 tdsbwdev ifup: No configuration found for eth3
Jan 16 15:48:56 tdsbwdev ifup: usb0
Jan 16 15:48:56 tdsbwdev ifup: No configuration found for usb0
Jan 16 15:48:57 tdsbwdev auditd[9684]: Started dispatcher: /sbin/audispd pid: 9686
Jan 16 15:48:57 tdsbwdev audispd: priority_boost_parser called with: 4
Jan 16 15:48:57 tdsbwdev audispd: af_unix plugin initialized
Jan 16 15:48:57 tdsbwdev audispd: audispd initialized with q_depth=80 and 1 active plugins
Jan 16 15:48:57 tdsbwdev auditd[9684]: Init complete, auditd 1.7.7 listening for events (startup state disable)
Jan 16 15:48:58 tdsbwdev multipathd: mpathb: load table [0 1258291200 multipath 1 queue_if_no_path 0 2 1 round-robin 0 2 1 8:16 1000 65:80 1000 round-robin 0
2 1 8:
Jan 16 15:48:58 tdsbwdev multipathd: mpathc: load table [0 1258291200 multipath 1 queue_if_no_path 0 2 1 round-robin 0 2 1 8:192 1000 66:0 1000 round-robin 0
2 1 8:
Jan 16 15:48:58 tdsbwdev multipathd: mpathd: load table [0 1258291200 multipath 1 queue_if_no_path 0 2 1 round-robin 0 2 1 8:48 1000 65:112 1000 round-robin
0 2 1 8
Jan 16 15:48:58 tdsbwdev kernel: klogd 1.4.1, log source = /proc/kmsg started.
Jan 16 15:48:58 tdsbwdev kernel: [ 61.694904] type=1505 audit(1326703731.692:2): operation="profile_load" pid=7621 name=/bin/ping
Jan 16 15:48:58 tdsbwdev kernel: [ 61.716682] type=1505 audit(1326703731.712:3): operation="profile_load" pid=7622 name=/sbin/klogd
Jan 16 15:48:58 tdsbwdev kernel: [ 61.757378] type=1505 audit(1326703731.756:4): operation="profile_load" pid=7623 name=/sbin/syslog-ng
Jan 16 15:48:58 tdsbwdev kernel: [ 61.798886] type=1505 audit(1326703731.796:5): operation="profile_load" pid=7624 name=/sbin/syslogd
Jan 16 15:48:58 tdsbwdev kernel: [ 61.843387] type=1505 audit(1326703731.840:6): operation="profile_load" pid=7625 name=/usr/sbin/avahi-daemon
Jan 16 15:48:58 tdsbwdev kernel: [ 61.880550] type=1505 audit(1326703731.880:7): operation="profile_load" pid=7626 name=/usr/sbin/identd
Jan 16 15:48:58 tdsbwdev kernel: [ 61.927302] type=1505 audit(1326703731.924:8): operation="profile_load" pid=7627 name=/usr/sbin/mdnsd
Jan 16 15:48:58 tdsbwdev kernel: [ 61.973857] type=1505 audit(1326703731.972:9): operation="profile_load" pid=7628 name=/usr/sbin/nscd
Jan 16 15:48:58 tdsbwdev kernel: [ 62.039439] type=1505 audit(1326703732.036:10): operation="profile_load" pid=7629 name=/usr/sbin/ntpd
Jan 16 15:48:58 tdsbwdev kernel: [ 62.076126] type=1505 audit(1326703732.072:11): operation="profile_load" pid=7630 name=/usr/sbin/traceroute
Jan 16 15:48:58 tdsbwdev kernel: [ 63.937151] microcode: CPU0 sig=0x206f2, pf=0x4, revision=0x32
Jan 16 15:48:58 tdsbwdev kernel: [ 63.953337] microcode: CPU1 sig=0x206f2, pf=0x4, revision=0x32
Jan 16 15:48:58 tdsbwdev kernel: [ 63.956652] microcode: CPU2 sig=0x206f2, pf=0x4, revision=0x32
Jan 16 15:48:58 tdsbwdev kernel: [ 63.960023] microcode: CPU3 sig=0x206f2, pf=0x4, revision=0x32
Jan 16 15:48:58 tdsbwdev kernel: [ 63.963288] microcode: CPU4 sig=0x206f2, pf=0x4, revision=0x32
Jan 16 15:48:58 tdsbwdev kernel: [ 63.966488] microcode: CPU5 sig=0x206f2, pf=0x4, revision=0x32
Jan 16 15:48:58 tdsbwdev kernel: [ 63.969769] microcode: CPU6 sig=0x206f2, pf=0x4, revision=0x32
Jan 16 15:48:58 tdsbwdev kernel: [ 63.972980] microcode: CPU7 sig=0x206f2, pf=0x4, revision=0x32
Jan 16 15:48:58 tdsbwdev kernel: [ 67.613672] device-mapper: multipath: Cannot access device path 8:0: -16
Jan 16 15:48:58 tdsbwdev kernel: [ 67.613702] device-mapper: table: 253:23: multipath: error getting device
Jan 16 15:48:58 tdsbwdev kernel: [ 67.613708] device-mapper: ioctl: error adding target to table
Jan 16 15:48:58 tdsbwdev kernel: [ 68.047055] device-mapper: multipath: Cannot access device path 8:0: -16
Jan 16 15:48:58 tdsbwdev kernel: [ 68.047082] device-mapper: table: 253:23: multipath: error getting device
Jan 16 15:48:58 tdsbwdev kernel: [ 68.047088] device-mapper: ioctl: error adding target to table
Jan 16 15:48:58 tdsbwdev kernel: [ 68.455663] bnx2: eth2 NIC Copper Link is Up, 100 Mbps half duplex
Please advise.
Thank you in advance.
Regards,
RudiDear all,
the inode issue occurs when copying files to /usr/sap folder from any directory.
/usr folder is mounted in the internal disk (rootvg) which contains OS files as /usr/sap folder is mounted in the V7000 storage (datavg). The problem is: every time we copy file from any directory to /usr/sap, that file is corrupted with i/o error message, then we just only remove it from the folder by running fsck, since it can not be removed manually.
Is it bug from SLES 11 SP1? I tried to configure SAP by joining /sap and /usr/sap using rootvg (internal disk), and it run successfully.
This is the version of LVM:
LVM2 tools 2.02.39-18.31.2
Device mapper tools 1.02.27-8.17.20
Device mapper tools -32bit 1.02.27-8.17.20
SUSE 11 SP01 2.6.32.49-0.3-default #1 SMP 2011-12-02 11:28:04 +0100 x86_64 x86_64 x86_64 GNU/Linux.
Please advise.
Regards,
Rudi -
Copy a compiled DBXML from one Linux machine to another Linux machine?
Hello
I am currently preparing two Linux machines for a DBXML application. One machine is for testing and the other for production. They are almost identical:
Test machine:
>
root@jumasiri:~# uname -a
Linux jumasiri 2.6.29.6 #2 Mon Aug 17 01:31:42 CDT 2009 i686 AMD Athlon(tm) AuthenticAMD GNU/Linux
root@jumasiri:~# gcc --version
gcc (GCC) 4.3.3
root@jumasiri:/etc# mount
/dev/root on / type ext2 (rw,errors=continue)
... (some lines left out for clarity)
>
Production machine
>
root@jumasiri:/etc/udev/rules.d# uname -a
Linux jumasiri 2.6.29.6-smp #2 SMP Mon Aug 17 00:52:54 CDT 2009 i686 AMD Athlon(tm) XP 2800+ AuthenticAMD GNU/Linux
root@jumasiri:/etc/udev/rules.d# gcc --version
gcc (GCC) 4.3.3
root@jumasiri:/etc# mount
/dev/root on / type ext3 (rw,errors=continue,data=ordered)
... (some lines left out for clarity)
/dev/hda3 on /usr/local type ext3 (rw)
/dev/hda4 on /home type ext3 (rw)
>
As you can see the test machine has everything mounted on 1 partition only, whereas the production uses several. The test machine has a ext2 filesystem and the production machine ext3 filesystems. The dbxml binaries and libraries are installed in /usr/local/dbxml on both machines. The databases are installed somewhere in /home/koen/.
I've compiled dbxml succssfully on both machines, but ran into severe compilation problems on the production machine when compiling Xerces. Instead of digging and solving into the problem I have simply copied the successful compilation of the test machine to the production machine. Everything seems to work.
My question is very simple. Can one do that, copying one compilation to another machine with the same OS but with a different filesystem?
Thank you
KoenHello
Thank you. One can never be sure enough, isn't it? For your information, the copy is running fine. My question was more related to the file system. As we don't know the inner workings of dbxml, we can never tell if the knowledge of type of file system is used internally.
Bye
Koen -
Critical Alarm for Nexus 7010 device
Hi Team,
We are getting Critical Alarm for the Data center device Nexus 7010 continuously from 28-Oct.
error (device hde1) in start_transaction: Journal has aborted - kernel
2012 Oct 29 10:00:18.227 DC-Core-Switch2 29 10:00:18 %KERN-2-SYSTEM_MSG: EXT3-fs
error (device hde1) in start_transaction: Journal has aborted - kernel
2012 Oct 29 10:28:37.497 DC-Core-Switch2 29 10:28:37 %KERN-2-SYSTEM_MSG: EXT3-fs
error (device hde1) in start_transaction: Journal has aborted - kernel
2012 Oct 29 10:28:42.398 DC-Core-Switch2 29 10:28:42 %KERN-2-SYSTEM_MSG: EXT3-fs
Also attaching the complete logs collected for this device and suggest if there is any Hardware related issue or some Software related issue.
Regards,
AshutoshHello
hde1 is the logflash device. Looks like there were IO errors and the kernel mounted the fs read-only. You can try to reload the device and if logflash will come back up fine after the reload, its a transient issue; if the issue comes back, the logflash device most likely is damaged bad and needs to be replaced. You will need to open a service request with TAC to get it replaced.
HTH,
Alex -
Hi all,
I installed oralce10.2.0 in Centos5.5.
During Normal Working Suddenly DB Crashed and Linux-x86_64's file system became Read-only file system.
The error in log file is like that.
Errors in file /u01/app/oracle/admin/WELS103/bdump/wels103_dbw0_5710.trc:
ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
ORA-01114: IO error writing block to file 16 (block # 17877)
ORA-01110: data file 16: '/data/WSMT_ETL_HIS201106_001.dbf'
ORA-27072: File I/O error
Linux-x86_64 Error: 5: Input/output error
Additional information: 4
Additional information: 17877
Additional information: -1
DBW0: terminating instance due to error 1242
Instance terminated by DBW0, pid = 5710
I used dbv to check datafile. The datafiles are normal.
I reboot linux and the file system became normal.
SQL>startup nomount
SQL>alter database mount
SQL>RECOVER DATAFILE '/data/WSMT_ETL_HIS201106_001.dbf'
SQL>recover tablespace system;
SQL>RECOVER DATABASE;
SQL>ALTER DATABASE OPEN;
And db is normal.But the same thing unexpected happened after a few days
Can anyone tell me what is the reason of this happening.
#df -lh
Filesystem Size Used Avail Use% Mounted on
/dev/cciss/c0d0p3 523G 115G 381G 24% /data
Any help would be greatly appreciated.Thanks.
The error in log file(/var/log/messages ) is like that.
Nov 17 17:28:57 DB-103 kernel: cciss 0000:03:00.0: cciss: c ffff810037e00000 has CHECK CONDITION sense key = 0x3
Nov 17 17:28:57 DB-103 kernel: Buffer I/O error on device cciss/c0d0p3, logical block 12117854
Nov 17 17:28:57 DB-103 kernel: lost page write due to I/O error on cciss/c0d0p3
Nov 17 17:28:57 DB-103 kernel: Buffer I/O error on device cciss/c0d0p3, logical block 12117855
Nov 17 17:28:57 DB-103 kernel: lost page write due to I/O error on cciss/c0d0p3
Nov 17 17:28:57 DB-103 kernel: Aborting journal on device cciss/c0d0p3.
Nov 17 17:28:57 DB-103 kernel: ext3_abort called.
Nov 17 17:28:57 DB-103 kernel: EXT3-fs error (device cciss/c0d0p3): ext3_journal_start_sb: Detected aborted journal
Nov 17 17:28:57 DB-103 kernel: Remounting filesystem read-only -
Hey guys.
Yesterday i decided to install Arch, on my second HD
It seems to me, that everything went fine, i just skipped the install of grub, because i already have grub on ubuntu. So i just went there and add a line to boot Arch as well.
I reboot the system, and choose Arch, the boot began, and when i was already celebrating, the boot started to "freeze"
It stopped for long times, on ata1, ata2, sd 0, and then after a really long wait he stop on "CD-Rom driver revision: 3.20"
Can someone plz tell me if i did anything wrong? Is it a problem with my HD's? I have no clue o.o
============================
on sda i have ubuntu hardy installed
sdb1 it's where i installed Arch, sdb2 its swap, and sdb3 /home.
sdc it's my third hd for files, musics, movies...
============================
If you guys need anything else about the computer or the installation, just say
Thks for the help.Disco /dev/sda: 20.0 GB, 20060135424 bytes
255 heads, 63 sectors/track, 2438 cylinders
Units = cilindros of 16065 * 512 = 8225280 bytes
Disk identifier: 0xc5f0c5f0
Dispositivo Boot Início Fim Blocos Id Sistema
/dev/sda1 * 1 2331 18723726 83 Linux
/dev/sda2 2332 2438 859477+ 5 Estendida
/dev/sda5 2332 2438 859446 82 Linux swap / Solaris
Disco /dev/sdb: 20.0 GB, 20020396032 bytes
255 heads, 63 sectors/track, 2434 cylinders
Units = cilindros of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00054c65
Dispositivo Boot Início Fim Blocos Id Sistema
/dev/sdb1 1 2434 19551073+ 83 Linux
Disco /dev/sdc: 10.1 GB, 10110320640 bytes
255 heads, 63 sectors/track, 1229 cylinders
Units = cilindros of 16065 * 512 = 8225280 bytes
Disk identifier: 0x73f973f9
Dispositivo Boot Início Fim Blocos Id Sistema
/dev/sdc1 * 1 6 48194+ 83 Linux
/dev/sdc2 7 72 530145 82 Linux swap / Solaris
/dev/sdc3 73 646 4610655 83 Linux
/dev/sdc4 647 1229 4682947+ 83 Linux
Hehe i find out that i need the root permission to use this one ^^
There it is, the last HD is the one with ARCH.
Sdc3 is /
Sdc4 is /home
I've edited the grub to that
root=/dev/sdc3 ro vga=773
But it always say that it can't find the root device.
(sorry for my bad english)
I was looking in the /dev folder, and i find out that IT'S EMPTY!! Well nearly empty, it only have these files:
-console
-null
-zero
Ohhh man, i dont get o.o
What have i did wrong x.x
Ohh here is my fstab, in case it helps.
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
none /dev/pts devpts defaults 0 0
none /dev/shm tmpfs defaults 0 0
/dev/cdrom /mnt/cd iso9660 ro,user,noauto,unhide 0 0
/dev/dvd /mnt/dvd udf ro,user,noauto,unhide 0 0
#/dev/fd0 /mnt/fl vfat user,noauto 0 0
#swap
UUID=1554de60-50c0-437c-8c3d-f94a3159c60e none swap sw 0 0
#HD's
#/dev/sdc3
UUID=2b48e50d-dd5c-496c-b214-fbdee73e3b39 / ext3 relatime,errors=remount-ro 0 1
#/dev/sdc4
UUID=2556ca41-461d-43ad-8eb5-1a7dacddf77e /home ext3 user,errors=remount-ro 0 2
Last edited by Razien (2008-05-25 14:51:46)
Maybe you are looking for
-
I restored my PC using Windows 7 64-bit and tried to download and reinstall iTunes. I can download the file titled "iTunes64Setup.exe" and when I run it the bar that pops up does not fill up and then I receive the massage that says "Windows Installer
-
How to eliminate an instance of "entering a sequence call" from the teststand report
I am using TestStand 4.2 and I am using a long sequence with several sub-sequences. In these subsequences I am getting test results that I would like to place in the TestStand report. Currently, in order to do this I have to check the "Record Resul
-
Error in Output--please ignore, not urgent
Hi friends, I wrote a bdc to update the value in an outbound delivery thru VL02N transaction. Everything is going fine n unexpectedly at some point i'm getting an error in output. Error is coming only sometimes not every time we execute the program.
-
I'm trying to clean up a Parallels installation, I got tired of it locking up my system when shutting down the VM, any way it added a host of Windows Applications to the Open With Menu in Finder. I've tried following a few older suggestions such as d
-
IPod will not update or restore
Whenever I try to update my iPod I get a pop-up that says it can't be updated because the filmware file could not be found, and when I try to restore it all it does is delete my files but it still won't update it. Could it be because I'm not using th