Mailing List Archive

On Sun, 16 Jul 2006 18:04:03 -0400 (EDT)
"Ronald Vincent Vazquez" <rvazquez@ctcministries.org> wrote:

> I have an E4500 with 4 processors and 2 gig of RAM. I installed
> Gentoo with 2.4.32-r6 kernel onto 3 mirrored drives. I would like to
> know if anybody can help me verifying my config so I may be able to
> boot this "Sparquie" from /dev/md0. Below are some of my configs:

/boot needs to either be by itself or on a raid0 setup or SILO will be
unable to read the information it needs to from the /boot partition at
boot time.

--
Jason Wever
Gentoo/Sparc Team Co-Lead

Jason Wever wrote:
>
> /boot needs to either be by itself or on a raid0 setup or SILO will be
> unable to read the information it needs to from the /boot partition at
> boot time.
>
>

Hello again:

Yes, it has been a while. I was forced to set this project aside and
just last night I had time to revisit it again. Well, you all know how
it is...

Ok, here is what I have in my fstab now:

###############################################################
/dev/sda1 /boot ext2 noatime
0 2
/dev/sdb1 /boot2 ext2
noatime 0 2
/dev/sdc1 /boot3 ext2
noatime 0 2
/dev/md0 / ext3
noatime 0 1
/dev/sda4 none swap sw
0 0
/dev/sdb4 none swap
sw 0 0
/dev/sdc4 none swap
sw 0 0
none /proc proc
defaults 0 0
shm /dev/shm tmpfs nodev,nosuid,noexec 0 0
###############################################################



Now, the machine attempts to boot but I get the following:


###############################################################
md: linear personality registered as nr 1
md: raid0 personality registered as nr 2
md: raid1 personality registered as nr 3
md: raid5 personality registered as nr 4
raid5: measuring checksumming speed
VIS : 162.400 MB/sec
raid5: using function: VIS (162.400 MB/sec)
md: multipath personality registered as nr 7
md: Autodetecting RAID arrays.
[events: 00000010]
[events: 00000010]
[events: 00000010]
md: autorun ...
md: considering scsi/host0/bus0/target2/lun0/part2 ...
md: adding scsi/host0/bus0/target2/lun0/part2 ...
md: adding scsi/host0/bus0/target1/lun0/part2 ...
md: adding scsi/host0/bus0/target0/lun0/part2 ...
md: created md0
md: bind<scsi/host0/bus0/target0/lun0/part2,1>
md: bind<scsi/host0/bus0/target1/lun0/part2,2>
md: bind<scsi/host0/bus0/target2/lun0/part2,3>
md: running:
<scsi/host0/bus0/target2/lun0/part2><scsi/host0/bus0/target1/lun0/part2><scsi/host0/bus0/tar>
md: scsi/host0/bus0/target2/lun0/part2's event counter: 00000010
md: scsi/host0/bus0/target1/lun0/part2's event counter: 00000010
md: scsi/host0/bus0/target0/lun0/part2's event counter: 00000010
md0: max total readahead window set to 248k
md0: 1 data-disks, max readahead per data-disk: 248k
raid1: device scsi/host0/bus0/target2/lun0/part2 operational as mirror 2
raid1: device scsi/host0/bus0/target1/lun0/part2 operational as mirror 1
raid1: device scsi/host0/bus0/target0/lun0/part2 operational as mirror 0
raid1: raid set md0 active with 3 out of 3 mirrors
md: updating md0 RAID superblock on device
md: scsi/host0/bus0/target2/lun0/part2 [events: 00000011]<6>(write)
scsi/host0/bus0/target2/lun0/part2's 6
md: scsi/host0/bus0/target1/lun0/part2 [events: 00000011]<6>(write)
scsi/host0/bus0/target1/lun0/part2's 6
md: scsi/host0/bus0/target0/lun0/part2 [events: 00000011]<6>(write)
scsi/host0/bus0/target0/lun0/part2's 6
md: ... autorun DONE.
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
LVM version 1.0.8(17/11/2003)
Initializing Cryptographic API
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 16384 buckets, 256Kbytes
TCP: Hash tables configured (established 262144 bind 65536)
Linux IP multicast router 0.06 plus PIM-SM
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
kjournald starting. Commit interval 5 seconds
*EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.*
Mounted devfs on /dev
INIT: version 2.86 booting

Gentoo Linux; http://www.gentoo.org/
Copyright 1999-2006 Gentoo Foundation; Distributed under the GPLv2

Press I to enter interactive boot mode

* Mounting proc at /proc
... [ ok ]
* Kernel automatically mounted devfs at /dev
... [ ok ]
* Starting devfsd ...Started device management daemon v1.3.25 for /dev
[ ok ]
* Starting up RAID devices (mdadm) ...mdadm: No arrays found in config file
[ !! ]
* Checking root filesystem ...fsck.ext3: Invalid argument while trying
to open /dev/md0
/dev/md0:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>


* Filesystem couldn't be fixed :(

[ !! ]
Give root password for maintenance
(or type Control-D to continue):

###############################################################


The thing is that as you can see on the fstab, the file system type on
/dev/md0 is ext3 and not ext2. Would any one be so kind to give me an
indication of what is going on here?


Thanks,

--

/////////////////////////////////////
Ronald Vincent Vazquez
Vice President of Technology Group
Senior Unix Systems Administrator
Senior Network Manager
Christ Tabernacle Church Ministries
http://www.ctcministries.org/
(301) 540-9394 Home
(240) 401-9192 Cell



--
gentoo-sparc@gentoo.org mailing list

On Wednesday 23 August 2006 21:53, Ronald Vazquez wrote:
> The thing is that as you can see on the fstab, the file system type on
> /dev/md0 is ext3 and not ext2.  Would any one be so kind to give me an
> indication of what is going on here?
>
>
> Thanks,

1. Give the password for root maintenance like it says, verify that /dev/md0
exists. Does devfs use the same name or does devfsd need to make the symlink?
It is quite some time since I used devfs(d) so I don't remember the
nomenclature for md devices off the top of my head. Or perhaps some other
devfs related problem?
2. Are the md partitions marked "autoraid" as partition type in the partition
table ? If yes then the kernel can initialise the array, if not then you need
to use the mdadm tools to initialise the array at boot, that might be why the
mdadm init script is failing, because the config file is empty or invalid.
3. the failure of the mdadm script is causing the root fsck to fail for some
reason?

You might have checked some of these, I don't know that from reading your post
and I haven't read your original post just voicing the concerns I saw from
your most recent post.

hamish

--
gentoo-sparc@gentoo.org mailing list

On Wednesday 23 August 2006 21:53, Ronald Vazquez wrote:
> Checking root filesystem ...fsck.ext3: Invalid argument while trying
> to open /dev/md0
> /dev/md0:
> The superblock could not be read or does not describe a correct ext2
> filesystem.  If the device is valid and it really contains an ext2
> filesystem (and not swap or ufs or something else), then the superblock
> is corrupt, and you might try running e2fsck with an alternate superblock:
>     e2fsck -b 8193 <device>
>
>
>  * Filesystem couldn't be fixed :(

apologies for multiple posting, I didn't actually address your primary
concern, just skipped over it and went to what caused the problem. ext3 is an
addition to ext2. ext3 is backwards compatible with ext2, you can overlook
what fsck says, don't take it literally, it is just saying it can't find an
ext* filesystem at all regardless of which version of ext* it tries.

Hamish

--
gentoo-sparc@gentoo.org mailing list

Hamish wrote:
> 1. Give the password for root maintenance like it says, verify that
> /dev/md0
> exists. Does devfs use the same name or does devfsd need to make the
> symlink?
> It is quite some time since I used devfs(d) so I don't remember the
> nomenclature for md devices off the top of my head. Or perhaps some other
> devfs related problem?
> 2. Are the md partitions marked "autoraid" as partition type in the
> partition
> table ? If yes then the kernel can initialise the array, if not then you
> need
> to use the mdadm tools to initialise the array at boot, that might be why
> the
> mdadm init script is failing, because the config file is empty or invalid.
> 3. the failure of the mdadm script is causing the root fsck to fail for
> some
> reason?
>
> You might have checked some of these, I don't know that from reading your
> post
> and I haven't read your original post just voicing the concerns I saw from
> your most recent post.
>
> hamish
>
> --
> gentoo-sparc@gentoo.org mailing list
>
Hello Hamish:

I tracked it down to the script checkroot. The command fsck returns 8
(Operational error) while checking the file system (/dev/md0). I did an
ugly hack just to boot the machine. I hard coded (retval=0) just to start
the machine and it does. Now, how do I fix this issue of (fsck /dev/md0)
returning 8 as supposed to 0?

Thanks again,

/////////////////////////////////////////////////
Ronald Vincent Vazquez
Senior Unix Systems Administrator
Senior Network Manager
Christ Tabernacle Church Ministries
http://www.ctcministries.org
(301) 540-9394 Home
(240) 401-9192 Cell

For web hosting solutions, please visit:
http://www.spherenix.com/

--
gentoo-sparc@gentoo.org mailing list