It looks like the work around has been successful. The machine boots fine
with the # in the fstab and the two commands in the rc.local file. I know
this is not ideal but at least the machine can be used now. I will look
into the problem in a bit more detail next week but currently i need to
crack on with other issues now. Thanks for all your help it has been much
appreciated.
P.s FYI - The e2fsck did not help with regards the machine coming back up
with out the fstab /dev/md0 hashed out.
Regards
[IMAGE]
|+-----------------------------+------------------------------------------|
|| <Krishnaprasad_K@xxxxxxxx>| |
|| Sent by: | |
|| redhat-list-bounces@redhat| To: <redhat-list@xxxxxxxxxx> |
|| .com | cc: |
|| | Subject: RE: Machine not|
|| 16/05/2007 14:58 | Booting - Continued |
|| Please respond to General | |
|| Red Hat Linux discussion | |
|| list | |
|| | |
|+-----------------------------+------------------------------------------|
That could be ok. After fixing bad blocks, have u tried to use the mount
during startup?
Note : You should not attempt to execute bad block fixing when partition
is mounted. It may damage ur partition / data
Regards,
Krishnaprasad
-----Original Message-----
From: redhat-list-bounces@xxxxxxxxxx
[mailto:redhat-list-bounces@xxxxxxxxxx] On Behalf Of
Andrew.Bridgeman@xxxxxxxxxxxxxx
Sent: Wednesday, May 16, 2007 6:40 PM
To: General Red Hat Linux discussion list
Subject: RE: Machine not Booting - Continued
I did put the commands in rc.local. The entry in the fstab is now hashed
out and the machine has rebooted OK, it seems to Skip on the "Starting up
Raid devices" on boot up. The machine is now up and running and i have just
done the e2fsck command like you mentioned, the output I got is below. It
looks like it has fixed something, do I still need to find the correct
command to fix bad blocks like you suggested or has this done it already.
Just to clarify the config's are all the same on these machines i.e fstabs
etc .
Let me know what you think.
e2fsck -y /dev/md0
e2fsck 1.32 (09-Nov-2002)
/dev/md0 is mounted.
WARNING!!! Running e2fsck on a mounted filesystem may cause
SEVERE filesystem damage.
Do you really want to continue (y/n)? yes
/dev/md0: recovering journal
/dev/md0 was not cleanly unmounted, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Inode 2 ref count is 3, should be 4. Fix? yes
Pass 5: Checking group summary information
/dev/md0: ***** FILE SYSTEM WAS MODIFIED *****
/dev/md0: 12/8011776 files (0.0% non-contiguous), 259619/16022156 blocks
Regards
Andrew Bridgeman
|+-----------------------------+------------------------------------------|
|| <Krishnaprasad_K@xxxxxxxx>| |
|| Sent by: | |
|| redhat-list-bounces@redhat| To: <redhat-list@xxxxxxxxxx> |
|| .com | cc: |
|| | Subject: RE: Machine not|
|| 16/05/2007 12:36 | Booting - Continued |
|| Please respond to General | |
|| Red Hat Linux discussion | |
|| list | |
|| | |
|+-----------------------------+------------------------------------------|
You put the mount command in /etc/rc.local right?
The error seems like its able to mount the partition but is not able to
perform bad block check ( using e2fsck ) .So can you perform bad block
check on your Software raid partition? ( I think its e2fsck -y
/dev/<partition name> , just see the man page for getting options of bad
block fixing )
I am still confused because you are able to do it after system boot up. So
I think we may be missing a step before trying to mount.
One more doubt.. Is the system configuration is different from other
machines where mount is working properly thro fstab?
Regards,
Krishnaprasad
-----Original Message-----
From: redhat-list-bounces@xxxxxxxxxx
[mailto:redhat-list-bounces@xxxxxxxxxx] On Behalf Of
Andrew.Bridgeman@xxxxxxxxxxxxxx
Sent: Wednesday, May 16, 2007 4:30 PM
To: General Red Hat Linux discussion list
Subject: RE: Machine not Booting - Continued
Thanks for the reply. No I do not have the raiddev utility so i put the
mkraid command and the mount command in the script as you suggested ( in no
particular place). It came up with the same error as i was
originally getting with the addition of the line below.
checking filesystems
/dev/md0 is mounted - e2fsck cannot continue aborting
Does this mean that i need to put the two commands in a specific place on
the /etc/rc.sysinit file?
P.s Once i have put the root passwd in, to go into maintenance mode the
/dev/md0 is mounted.
Thanks for your help so far. Please let me know what you think i should do
next.
Regards
Andrew
|+-----------------------------+------------------------------------------|
|| <Krishnaprasad_K@xxxxxxxx>| |
|| Sent by: | |
|| redhat-list-bounces@redhat| To: <redhat-list@xxxxxxxxxx> |
|| .com | cc: |
|| | Subject: RE: Machine not|
|| 16/05/2007 10:49 | Booting - Continued |
|| Please respond to General | |
|| Red Hat Linux discussion | |
|| list | |
|| | |
|+-----------------------------+------------------------------------------|
If you see /etc/rc.sysinit you can see some sections for managing raid
partitions. As per that section it uses raiddev utility. Can you check if
you have that utility installed in your system.
Otherwise specify the same mkraid and mount command in /etc/rc.local. still
its not a preffered way :(
Just for a cross check we can try that option.
Regards,
Krishnaprasad
-----Original Message-----
From: redhat-list-bounces@xxxxxxxxxx
[mailto:redhat-list-bounces@xxxxxxxxxx] On Behalf Of
Andrew.Bridgeman@xxxxxxxxxxxxxx
Sent: Wednesday, May 16, 2007 2:20 PM
To: redhat-list@xxxxxxxxxx
Subject: RE: Machine not Booting - Continued
The fstab is not to blame for this issue as i have just run mkraid /dev/md0
and then a mount -a and the area mounted straight away. It is as if the
mkraid command is not recognised when the machine is rebooted.
Any ideas on what i can check next would be much appreciated.
Regards
Andrew Bridgeman
----- Forwarded by Andrew Bridgeman/UK/Corus on 16/05/2007 09:47 -----
|+------+--------------------------------------------------|
|| And| To: General Red Hat Linux |
|| rew| discussion list <redhat-list@xxxxxxxxxx> |
|| Bri| cc: |
|| dge| Subject: RE: Machine not Booting|
|| man| - UpdateLink |
|| | |
|| 16/| |
|| 05/| |
|| 200| |
|| 7 | |
|| 08:| |
|| 09 | |
|| | |
|+------+--------------------------------------------------|
Hello,
Thanks for the reply. I am gradually narrowing the issue down
thanks to the replies.
I have just run the following commands with the system up ( with the line
hashed out on the /etc/fstab ) and the mount looks fine and it completed
with no errors so the problem only seems to be when i reboot the system
with the line back in the /etc/fstab.
mkraid /dev/md0
mkfs.ext3 /dev/md0
mount /dev/md0 /local_scratch
Any ideas on what i can check now because the entries in the fstab appear
to be identical to all my other machines?
Regards
Andrew Bridgeman
|+-----------------------------+------------------------------------------|
|| <Krishnaprasad_K@xxxxxxxx>| |
|| Sent by: | |
|| redhat-list-bounces@redhat| To: <redhat-list@xxxxxxxxxx> |
|| .com | cc: |
|| | Subject: RE: Machine not|
|| 16/05/2007 05:32 | Booting - Update |
|| Please respond to General | |
|| Red Hat Linux discussion | |
|| list | |
|| | |
|+-----------------------------+------------------------------------------|
Hi,
Have you tried mounting the software RAID partition manually? It seems like
it has no proper file system to mount. Try to create ext3 file system again
manually.
Regards,
Krishnaprasad
-----Original Message-----
From: redhat-list-bounces@xxxxxxxxxx
[mailto:redhat-list-bounces@xxxxxxxxxx] On Behalf Of
Andrew.Bridgeman@xxxxxxxxxxxxxx
Sent: Tuesday, May 15, 2007 8:28 PM
To: redhat-list@xxxxxxxxxx
Subject: Machine not Booting - Update
Problem continued.
If I hash the /dev/md0 line out of the /etc/fstab the machine boots fine.
When i try a mount -a when the machine has come up i get the error below. I
have double checked the fstab and it is identical to the other 40 odd
machines so it is not a problem with a typo etc. Does anyone know something
else i can look at to resolve this issue.
mount: wrong fs type, bad option, bad superblock on /dev/md0,
or too many mounted file systems
(could this be the IDE device where you in fact use
ide-scsi so that sr0 or sda or so is needed?)
I know the fs type is OK , the options are right in the fstab and i only
have around 10 files systems mounted so the only thing left is the bad
Superblock - does anyone know what this is referring too?
Regards
Andrew Bridgeman
----- Forwarded by Andrew Bridgeman/UK/Corus on 15/05/2007 15:44 -----
|+-----------+----------------------------------------------|
|| Andrew | |
|| Bridgema| To: redhat-list@xxxxxxxxxx |
|| n | cc: |
|| | Subject: Machine not Booting|
|| 15/05/20| |
|| 07 10:40| |
|| | |
|+-----------+----------------------------------------------|
I am currently having problems with a Redhat machine not booting after a DD
image of another machine has been put on to it. We have 40 odd machines
with all exactly the same spec and OS config and DD is used to image one
machine incase of a disk failure. This image is kept on a network drive and
then deployed when needed. I have checked to make sure the Raid settings on
the machine are correct and they seem fine showing 2 x 36gig disks
individually using raid 0.
The error i get when i reboot the machine after the image has been deployed
to it is below, it then prompt me for the root password to enter
maintenance mode. Has anyone seen this error before or do you have any
ideas where i can start to diagnose the problem.
" Invalid Argument when trying to open /dev/md0"
P.s The /dev/md0 device is used for our /local_scratch area which is
around 60 gig in size.
Any help would be much appreciated.
Regards
Andrew Bridgeman
**********************************************************************
This transmission is confidential and must not be used or disclosed by
anyone other than the intended recipient. Neither Corus Group Plc nor
any of its subsidiaries can accept any responsibility for any use or
misuse of the transmission by anyone.
For address and company registration details of certain entities
within the Corus group of companies, please visit
http://www.corusgroup.com/entities
**********************************************************************
--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
**********************************************************************
This transmission is confidential and must not be used or disclosed by
anyone other than the intended recipient. Neither Corus Group Plc nor
any of its subsidiaries can accept any responsibility for any use or
misuse of the transmission by anyone.
For address and company registration details of certain entities
within the Corus group of companies, please visit
http://www.corusgroup.com/entities
**********************************************************************
--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
**********************************************************************
This transmission is confidential and must not be used or disclosed by
anyone other than the intended recipient. Neither Corus Group Plc nor
any of its subsidiaries can accept any responsibility for any use or
misuse of the transmission by anyone.
For address and company registration details of certain entities
within the Corus group of companies, please visit
http://www.corusgroup.com/entities
**********************************************************************
--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
**********************************************************************
This transmission is confidential and must not be used or disclosed by
anyone other than the intended recipient. Neither Corus Group Plc nor
any of its subsidiaries can accept any responsibility for any use or
misuse of the transmission by anyone.
For address and company registration details of certain entities
within the Corus group of companies, please visit
http://www.corusgroup.com/entities
**********************************************************************
--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
(Embedded image moved to file: pic01023.jpg)
**********************************************************************
This transmission is confidential and must not be used or disclosed by
anyone other than the intended recipient. Neither Corus Group Plc nor
any of its subsidiaries can accept any responsibility for any use or
misuse of the transmission by anyone.
For address and company registration details of certain entities
within the Corus group of companies, please visit
http://www.corusgroup.com/entities
**********************************************************************
--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
