1 |
Jason Wever wrote: |
2 |
> |
3 |
> /boot needs to either be by itself or on a raid0 setup or SILO will be |
4 |
> unable to read the information it needs to from the /boot partition at |
5 |
> boot time. |
6 |
> |
7 |
> |
8 |
|
9 |
Hello again: |
10 |
|
11 |
Yes, it has been a while. I was forced to set this project aside and |
12 |
just last night I had time to revisit it again. Well, you all know how |
13 |
it is... |
14 |
|
15 |
Ok, here is what I have in my fstab now: |
16 |
|
17 |
############################################################### |
18 |
/dev/sda1 /boot ext2 noatime |
19 |
0 2 |
20 |
/dev/sdb1 /boot2 ext2 |
21 |
noatime 0 2 |
22 |
/dev/sdc1 /boot3 ext2 |
23 |
noatime 0 2 |
24 |
/dev/md0 / ext3 |
25 |
noatime 0 1 |
26 |
/dev/sda4 none swap sw |
27 |
0 0 |
28 |
/dev/sdb4 none swap |
29 |
sw 0 0 |
30 |
/dev/sdc4 none swap |
31 |
sw 0 0 |
32 |
none /proc proc |
33 |
defaults 0 0 |
34 |
shm /dev/shm tmpfs nodev,nosuid,noexec 0 0 |
35 |
############################################################### |
36 |
|
37 |
|
38 |
|
39 |
Now, the machine attempts to boot but I get the following: |
40 |
|
41 |
|
42 |
############################################################### |
43 |
md: linear personality registered as nr 1 |
44 |
md: raid0 personality registered as nr 2 |
45 |
md: raid1 personality registered as nr 3 |
46 |
md: raid5 personality registered as nr 4 |
47 |
raid5: measuring checksumming speed |
48 |
VIS : 162.400 MB/sec |
49 |
raid5: using function: VIS (162.400 MB/sec) |
50 |
md: multipath personality registered as nr 7 |
51 |
md: Autodetecting RAID arrays. |
52 |
[events: 00000010] |
53 |
[events: 00000010] |
54 |
[events: 00000010] |
55 |
md: autorun ... |
56 |
md: considering scsi/host0/bus0/target2/lun0/part2 ... |
57 |
md: adding scsi/host0/bus0/target2/lun0/part2 ... |
58 |
md: adding scsi/host0/bus0/target1/lun0/part2 ... |
59 |
md: adding scsi/host0/bus0/target0/lun0/part2 ... |
60 |
md: created md0 |
61 |
md: bind<scsi/host0/bus0/target0/lun0/part2,1> |
62 |
md: bind<scsi/host0/bus0/target1/lun0/part2,2> |
63 |
md: bind<scsi/host0/bus0/target2/lun0/part2,3> |
64 |
md: running: |
65 |
<scsi/host0/bus0/target2/lun0/part2><scsi/host0/bus0/target1/lun0/part2><scsi/host0/bus0/tar> |
66 |
md: scsi/host0/bus0/target2/lun0/part2's event counter: 00000010 |
67 |
md: scsi/host0/bus0/target1/lun0/part2's event counter: 00000010 |
68 |
md: scsi/host0/bus0/target0/lun0/part2's event counter: 00000010 |
69 |
md0: max total readahead window set to 248k |
70 |
md0: 1 data-disks, max readahead per data-disk: 248k |
71 |
raid1: device scsi/host0/bus0/target2/lun0/part2 operational as mirror 2 |
72 |
raid1: device scsi/host0/bus0/target1/lun0/part2 operational as mirror 1 |
73 |
raid1: device scsi/host0/bus0/target0/lun0/part2 operational as mirror 0 |
74 |
raid1: raid set md0 active with 3 out of 3 mirrors |
75 |
md: updating md0 RAID superblock on device |
76 |
md: scsi/host0/bus0/target2/lun0/part2 [events: 00000011]<6>(write) |
77 |
scsi/host0/bus0/target2/lun0/part2's 6 |
78 |
md: scsi/host0/bus0/target1/lun0/part2 [events: 00000011]<6>(write) |
79 |
scsi/host0/bus0/target1/lun0/part2's 6 |
80 |
md: scsi/host0/bus0/target0/lun0/part2 [events: 00000011]<6>(write) |
81 |
scsi/host0/bus0/target0/lun0/part2's 6 |
82 |
md: ... autorun DONE. |
83 |
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27 |
84 |
LVM version 1.0.8(17/11/2003) |
85 |
Initializing Cryptographic API |
86 |
NET4: Linux TCP/IP 1.0 for NET4.0 |
87 |
IP Protocols: ICMP, UDP, TCP, IGMP |
88 |
IP: routing cache hash table of 16384 buckets, 256Kbytes |
89 |
TCP: Hash tables configured (established 262144 bind 65536) |
90 |
Linux IP multicast router 0.06 plus PIM-SM |
91 |
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. |
92 |
kjournald starting. Commit interval 5 seconds |
93 |
*EXT3-fs: mounted filesystem with ordered data mode. |
94 |
VFS: Mounted root (ext3 filesystem) readonly.* |
95 |
Mounted devfs on /dev |
96 |
INIT: version 2.86 booting |
97 |
|
98 |
Gentoo Linux; http://www.gentoo.org/ |
99 |
Copyright 1999-2006 Gentoo Foundation; Distributed under the GPLv2 |
100 |
|
101 |
Press I to enter interactive boot mode |
102 |
|
103 |
* Mounting proc at /proc |
104 |
... [ ok ] |
105 |
* Kernel automatically mounted devfs at /dev |
106 |
... [ ok ] |
107 |
* Starting devfsd ...Started device management daemon v1.3.25 for /dev |
108 |
[ ok ] |
109 |
* Starting up RAID devices (mdadm) ...mdadm: No arrays found in config file |
110 |
[ !! ] |
111 |
* Checking root filesystem ...fsck.ext3: Invalid argument while trying |
112 |
to open /dev/md0 |
113 |
/dev/md0: |
114 |
The superblock could not be read or does not describe a correct ext2 |
115 |
filesystem. If the device is valid and it really contains an ext2 |
116 |
filesystem (and not swap or ufs or something else), then the superblock |
117 |
is corrupt, and you might try running e2fsck with an alternate superblock: |
118 |
e2fsck -b 8193 <device> |
119 |
|
120 |
|
121 |
* Filesystem couldn't be fixed :( |
122 |
|
123 |
[ !! ] |
124 |
Give root password for maintenance |
125 |
(or type Control-D to continue): |
126 |
|
127 |
############################################################### |
128 |
|
129 |
|
130 |
The thing is that as you can see on the fstab, the file system type on |
131 |
/dev/md0 is ext3 and not ext2. Would any one be so kind to give me an |
132 |
indication of what is going on here? |
133 |
|
134 |
|
135 |
Thanks, |
136 |
|
137 |
-- |
138 |
|
139 |
///////////////////////////////////// |
140 |
Ronald Vincent Vazquez |
141 |
Vice President of Technology Group |
142 |
Senior Unix Systems Administrator |
143 |
Senior Network Manager |
144 |
Christ Tabernacle Church Ministries |
145 |
http://www.ctcministries.org/ |
146 |
(301) 540-9394 Home |
147 |
(240) 401-9192 Cell |
148 |
|
149 |
|
150 |
|
151 |
-- |
152 |
gentoo-sparc@g.o mailing list |