Re: [parisc-linux] Call for Testing
Hello Kyle + all,
I try to hack a bit more this pb but a very weird pb:
> >
> > On Tue, Mar 29, 2005 at 12:45:17PM +0200, Joel Soete wrote:
> > > Any idae?
> > >
> >
> > Hi Joel,
> >
> > Thanks again for helping me with this. I think the problem is that
> > you don't have "discover1" or "hotplug" installed. I think this is
> > at least the problem with lasi ethernet not getting loaded and may
> > be a contributing factor for this as well.
> >
> ah...
> # dpkg -l discover\*
> Desired=Unknown/Install/Remove/Purge/Hold
>
>
> | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
>
> |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
>
> ||/ Name Version Description
> +++-==============-==============-============================================
> ii discover
2.0.7-2
> hardware identification system
>
> ii discover-data 2.2005.02.13-1 Data lists for Discover hardware detection
> s
> un discover1 <none> (no description available)
>
> un discover1-data <none> (no description available)
>
>
> Better to remove 'discover' to reinstall 'discover1' ?
>
I install hotplug: no help :-(
Well, (even thought that discover seems more recent) I purge the discover
pkg and install discover1 in place: no help :_(
I log more the boot the b180 and this looks like:
sym0:8: FAST-20 WIDE SCSI 40.0 MB/s ST (50.0 ns, offset 15)
scsi(0:0:8:0): Domain Validation skipping write tests
scsi(0:0:8:0): Ending Domain Validation
Attached scsi generic sg0 at scsi0, channel 0, id 5, lun 0, type 0
Attached scsi generic sg1 at scsi0, channel 0, id 6, lun 0, type 0
Attached scsi generic sg2 at scsi0, channel 0, id 8, lun 0, type 0
SCSI device sda: 17773524 512-byte hdwr sectors (9100 MB)
SCSI device sda: drive cache: write through
/dev/scsi/host0/bus0/target5/lun0: p1 p2 p3 p4 < p5 p6 p7 p8 p9 p10 p11
>
Attached scsi disk sda at scsi0, channel 0, id 5, lun 0
SCSI device sdb: 17773524 512-byte hdwr sectors (9100 MB)
SCSI device sdb: drive cache: write back
/dev/scsi/host0/bus0/target6/lun0: p1 p2 p3 p4 < p5 p6 p7 p8 p9 p10 p11
>
Attached scsi disk sdb at scsi0, channel 0, id 6, lun 0
SCSI device sdc: 17783112 512-byte hdwr sectors (9105 MB)
SCSI device sdc: drive cache: write back
/dev/scsi/host0/bus0/target8/lun0: p1 p2 p3 p4 < p5 p6 p7 p8 p9 p10 >
Attached scsi disk sdc at scsi0, channel 0, id 8, lun 0
md: md1 stopped.
md: bind<sdb3>
md: bind<sda3>
raid1: raid set md1 active with 2 out of 2 mirrors
mdadm: /devfs/mdmd: md2 stopped.
/1 has been started with 2 drives.
md: bind<sdb5>
md: bind<sda5>
raid1: raid set md2 active with 2 out of 2 mirrors
mdadm: /devfs/md/2 has been started with 2 drives.
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
INIT: version 2.86 booting
Activating swap.
Adding 127928k swap on /dev/md1. Priority:-1 extents:1
Checking root file system...
fsck 1.37 (21-Mar-2005)
/dev/md2: clean, 64824/215936 files, 293120/431840 blocks
EXT3 FS on md2, internal journal
System time was Wed Mar 30 08:46:42 UTC 2005.
Setting the System Clock using the Hardware Clock as reference...
System Clock set. System local time is now Wed Mar 30 08:46:44 UTC 2005.
Cleaning up ifupdown...done.
Calculating module dependencies... done.
Loading modules...
All modules loaded.
device-mapper: 4.1.0-ioctl (2003-12-10) initialised: dm@uk.sistina.com
Creating device-mapper devices...done.
Creating device-mapper devices...done.
Starting raid devices:
md: md0 stopped.
md: bind<sdb2>
md: bind<sda2>
raid1: raid set md0 active with 2 out of 2 mirrors
mdadm: /dev/md0 has been started with 2 drives.
md: md3 stopped.
md: bind<sdb6>
md: bind<sda6>
raid1: raid set md3 active with 2 out of 2 mirrors
mdadm: /dev/md3 has been started with 2 drives.
md: md4 stopped.
md: bind<sdb7>
md: bind<sda7>
raid1: raid set md4 active with 2 out of 2 mirrors
mdadm: /dev/md4 has been started with 2 drives.
md: md5 stopped.
md: bind<sdb8>
md: bind<sda8>
raid1: raid set md5 active with 2 out of 2 mirrors
mdadm: /dev/md5 has been started with 2 drives.
md: md6 stopped.
md: bind<sdb9>
md: bind<sda9>
raid1: raid set md6 active with 2 out of 2 mirrors
mdadm: /dev/md6 has been started with 2 drives.
md: md7 stopped.
md: bind<sdb10>
md: bind<sda10>
raid1: raid set md7 active with 2 out of 2 mirrors
mdadm: /dev/md7 has been started with 2 drives.
md: md8 stopped.
md: bind<sdb11>
md: bind<sda11>
raid1: raid set md8 active with 2 out of 2 mirrors
mdadm: /dev/md8 has been started with 2 drives.
done.
Setting up LVM Volume Groups...
Reading all physical volumes. This may take a while...
No volume groups found
No volume groups found
No volume groups found
Checking all file systems...
fsck 1.37 (21-Mar-2005)
/dev/md0: clean, 72/32000 files, 110376/127936 blocks
/dev/md3: clean, 4521/64000 files, 151291/255872 blocks
/dev/md4: clean, 14/32000 files, 8179/127872 blocks (check in 3 mounts)
/dev/md5: clean, 252/32000 files, 47687/127872 blocks
/dev/md6 has been mounted 39 times without being checked, check forced.
/dev/md6: |========================================================| 100.0%
/dev/md6: 88233/256000 files (1.3% non-contiguous), 421807/511968 blocks
/dev/md7: clean, 2919/256000 files, 325572/511968 blocks
/dev/md8: clean, 68414/256000 files, 376166/511968 blocks
/dev/sdc5: clean, 66950/256512 files, 314297/512252 blocks
/dev/sdc2: clean, 36/32000 files, 64653/128000 blocks
/dev/sdc6: clean, 3593/64000 files, 216578/255984 blocks
/dev/sdc7: clean, 14/32000 files, 8185/127984 blocks (check after next mount)
/dev/sdc8: clean, 168/32000 files, 13193/127984 blocks
/dev/sdc9: clean, 90909/256512 files, 311338/512252 blocks
/dev/sdc10: clean, 2767/250368 files, 307695/499964 blocks
Setting kernel variables ...
...
boot ok :-)
but for what is very weird on the b2k (just set -x in mdadm-raid):
Activating swap.
Adding 255928k swap on /dev/md1. Priority:-1 extents:1
Checking root file system...
fsck 1.37 (21-Mar-2005)
/dev/md2: clean, 76063/200096 files, 346742/3998EXT3 FS on md2, 40 blocks
(checkinternal journal
in 5 mounts)
System time was Wed Mar 30 09:51:19 UTC 2005.
Setting the System Clock using the Hardware Clock as reference...
System Clock set. System local time is now Wed Mar 30 09:51:21 UTC 2005.
Cleaning up ifupdown...done.
Calculating module dependencies... done.
Loading modules...
All modules loaded.
+ MDADM=/sbin/mdadm
+ MDRUN=/sbin/mdrun
+ CONFIG=/etc/mdadm/mdadm.conf
+ DEBIANCONFIG=/etc/default/mdadm
+ test -x /sbin/mdadm
+ AUTOSTART=true
+ test -f /etc/default/mdadm
+ . /etc/default/mdadm
++ START_DAEMON=true
++ MAIL_TO=root
++ AUTOSTART=true
+ case "$1" in
+ '[' xtrue = xtrue ']'
+ '[' '!' -f /proc/mdstat ']'
+ test -f /proc/mdstat
+ echo 'Starting raid devices: '
Starting raid devices:
+ '[' -f /etc/mdadm/mdadm.conf ']'
+ '[' -x /sbin/mdrun ']'
+ /sbin/mdrun
+ echo done.
done.
+ exit 0
Checking all file systems...
fsck 1.37 (21-Mar-2005)
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:
...
What I don't understand is why /sbin/mdrun didn't discover the other md[0..3-8]?
I compare also the results of description of md structure (mdadm -d /dev/md[0-8])
of each system and excepted some size or uuid there aren't imho any relevant
diff
and list of modules:
(none):~ # lsmod
Module Size Used by
ext3 158800 1
jbd 77304 1 ext3
sd_mod 24352 6
sg 49952 0
sym53c8xx 102508 4
scsi_transport_spi 17056 1 sym53c8xx
raid1 21728 2
md 61864 3 raid1
unix 32912 0
and also some more disk info:
...
sym0: SCSI BUS has been reset.
scsi0 : sym-2.2.0
Vendor: QUANTUM Model: ATLAS5-9LVD Rev: HP04
Type: Direct-Access ANSI SCSI revision: 03
target0:0:5: tagged command queuing enabled, command queue depth 16.
target0:0:5: Beginning Domain Validation
target0:0:5: asynchronous.
target0:0:5: wide asynchronous.
target0:0:5: FAST-40 WIDE SCSI 80.0 MB/s ST (25 ns, offset 31)
target0:0:5: Ending Domain Validation
Vendor: SEAGATE Model: ST336704LC Rev: HP03
Type: Direct-Access ANSI SCSI revision: 03
target0:0:6: tagged command queuing enabled, command queue depth 16.
target0:0:6: Beginning Domain Validation
target0:0:6: asynchronous.
target0:0:6: wide asynchronous.
target0:0:6: FAST-40 WIDE SCSI 80.0 MB/s ST (25 ns, offset 31)
target0:0:6: Ending Domain Validation
...
I also try to populate a /etc/mdadm/mdadm.conf with mdadm -D -scan >/etc/mdadm/mdadm.conf
in this case I got some errors like:
...
All modules loaded.
Starting raid devices:
md: md3 stopped.
mdadm: no devicemd: md4 stopped.
s found for /devmd: md5 stopped.
/md3
mdadm: no md: md6 stopped.
devices found fomd: md7 stopped.
r /dev/md4
mdadmd: md8 stopped.
m: no devices fomd: md0 stopped.
und for /dev/md5
mdadm: no devices found for /dev/md6
mdadm: no devices found for /dev/md7
mdadm: no devices found for /dev/md8
mdadm: no devices found for /dev/md0
done.
...
even thought:
cfdisk 2.12p
Disk Drive: /dev/sdb
Size: 36420075520 bytes, 36.4 GB
Heads: 64 Sectors per Track: 32 Cylinders: 34732
Name Flags Part Type FS Type [Label] Size
(MB)
------------------------------------------------------------------------------
sdb1 Primary Linux/PA-RISC boot
66.07
sdb2 Primary Linux raid autodetect
131.08
sdb3 Primary Linux raid autodetect
262.15
sdb5 Logical Linux raid autodetect 1637.88
sdb6 Logical Linux raid autodetect
262.15
sdb7 Logical Linux raid autodetect
131.08
sdb8 Logical Linux raid autodetect
131.08
sdb9 Logical Linux raid autodetect 2097.16
sdb10 Logical Linux raid autodetect 2097.16
sdb11 Logical Linux raid autodetect 2097.16
and the same for the other disk
Welcome to any other idea :-)
Thanks,
Joel
Reply to: