Linux-Setup Digest #515, Volume #20 Sat, 27 Jan 01 09:13:10 EST
Contents:
Re: XCDROAST - "device on SCSI BUS has changed" error. ("Gene Heskett")
Re: XCDROAST - "device on SCSI BUS has changed" error. (Brian Goodyear)
Re: anyone having experience in setting up @Home (Neuromancer)
Re: Proliant 2500R + Red Hat 6.2 - RAID5 suddenly loses drives (The Archimage)
Re: Help with error msg's and cable modem prob (Neuromancer)
hangs on verifying dmi pool with hard drive ("Dave Thompson")
----------------------------------------------------------------------------
Date: 27 Jan 2001 8:28:47 -0500
From: "Gene Heskett" <[EMAIL PROTECTED]>
Subject: Re: XCDROAST - "device on SCSI BUS has changed" error.
Gene Heskett sends Greetings to Mike Holmes;
MH> I got my IDE CD-RW working great burning and all with one final
MH> flaw...
MH> everytime I open XCDROAST .96 I get the error message - "device
MH> on SCSI bus has changed - check config file to verify settings
MH> are ok..."
MH> I have to confirm the settings (which are OK) everytime, then I
MH> can use the program - What gives? Is this an error in XCDROAST
MH> 0.96 or do I need to tweak some more linux commands or kernel
MH> set-up?
MH> PS: The other CD-Player software I use with the burner doesn't
MH> give me any hassle about SCSI-stuffs at at all.
Generally speaking, this is/has been caused here by an external tape
drive that is sometimes turned on at boot time, and sometimes off.
The change in the bus device count caused this effect here. I finally
got enough tape drives that I could mount them internally which was the
end of *that* problem. I suppose it could be caused also by a slow to
get ready disk drive, but with boot times to that point being measured
in the 30 seconds plus area, I'd have troubleing thoughts about such a
drive, its probably on its way out.
Besides, its time to update your xcdroast to the current 0.98 test
version, lots of progress has been made. You might also look at
gnome-toaster, which is quite capable, but to me has a steeper learning
curve.
Cheers, Gene
--
Gene Heskett, CET, UHK |Amiga A2k Zeus040, Linux @ 600mhz
email gene underscore heskett at iolinc dot net
#Amiga based X10 home automation program EZHome, see at:#
# <http://www.thirdwave.net/~jimlucia/amigahomeauto> #
ISP's please take note: My spam control policy is explicit!
#Any Class C address# involved in spamming me is added to my killfile
never to be seen again. Message will be automaticly deleted without dl.
This messages reply content, but not any previously quoted material,
is � 2000 by Gene Heskett, all rights reserved.
--
------------------------------
From: Brian Goodyear <[EMAIL PROTECTED]>
Subject: Re: XCDROAST - "device on SCSI BUS has changed" error.
Date: Sat, 27 Jan 2001 08:48:34 -0500
Mike Holmes wrote:
> the program - What gives? Is this an error in XCDROAST 0.96
Seems to be a feature of the program.
------------------------------
Subject: Re: anyone having experience in setting up @Home
From: [EMAIL PROTECTED] (Neuromancer)
Date: Sat, 27 Jan 2001 13:51:31 GMT
I was never successful at getting my Linux dhcp working with @Home either.
Since my ip is static, I just manually configured everything and life is
good.
If you don't already have all the information, from Windoze, run
windows\winipcfg.exe. Click on "More Info>>" and write down everthing.
Plug all that into your Linux setup and you'll be off and running.
[EMAIL PROTECTED] wrote in <94sk43$9ki$[EMAIL PROTECTED]>:
>I am trying to set up my linux machine to access internet via cable
>modem
>Have tried linuxconf - enabled dhcp and put in a host name
>However, I keep on getting a message
>saying /etc/rc.d/rc3.d/S10network reload
>did not work
>essentially, it does not seem to be able to connect to a dhcp server
>
>any advice on this will be useful
>Thanks
>henna
>
>
>Sent via Deja.com
>http://www.deja.com/
>
------------------------------
From: The Archimage <[EMAIL PROTECTED]>
Crossposted-To:
comp.os.linux.hardware,alt.sys.pc-clone.compaq,alt.sys.pc-clone.compaq.servers,comp.os.linux.admin,comp.os.linux,comp.os.linux.misc,comp.os.linux.redhat
Subject: Re: Proliant 2500R + Red Hat 6.2 - RAID5 suddenly loses drives
Date: Sat, 27 Jan 2001 13:37:29 GMT
Logs below. They are long.
Jan 26 06:05:10 archimage kernel: SCSI disk error : host 0 channel 0 id
3 lun 0 return code = 2
Jan 26 06:05:10 archimage kernel: scsidisk I/O error: dev 08:31, sector
1747688
Jan 26 06:05:10 archimage kernel: raid5: Disk failure on sdd1, disabling
device. Operation continuing on 6 devices
Jan 26 06:05:10 archimage kernel: md: recovery thread got woken up ...
Jan 26 06:05:10 archimage kernel: md0: no spare disk to reconstruct
array! -- continuing in degraded mode
Jan 26 06:05:10 archimage kernel: md: recovery thread finished ...
Jan 26 06:05:10 archimage kernel: md: updating md0 RAID superblock on
device
Jan 26 06:05:10 archimage kernel: sdg1 [events: 00000006](write) sdg1's
sb offset: 8807296
Jan 26 06:05:10 archimage kernel: sdf1 [events: 00000006](write) sdf1's
sb offset: 8807296
Jan 26 06:05:10 archimage kernel: sde1 [events: 00000006](write) sde1's
sb offset: 8807296
Jan 26 06:05:10 archimage kernel: (skipping faulty sdd1 )
Jan 26 06:05:10 archimage kernel: sdc1 [events: 00000006](write) sdc1's
sb offset: 8807296
Jan 26 06:05:10 archimage kernel: sdb1 [events: 00000006](write) sdb1's
sb offset: 8807296
Jan 26 06:05:10 archimage kernel: sda5 [events: 00000006](write) sda5's
sb offset: 8811520
Jan 26 06:05:10 archimage kernel: .
Jan 26 06:05:10 archimage kernel: raid5: restarting stripe 4849728
Jan 26 06:05:10 archimage kernel: raid5: restarting stripe 4849736
Jan 26 06:05:10 archimage kernel: raid5: restarting stripe 4849744
Jan 26 06:05:10 archimage kernel: raid5: restarting stripe 4849752
Jan 26 06:05:10 archimage kernel: raid5: restarting stripe 4849768
Jan 26 06:05:10 archimage kernel: raid5: restarting stripe 4849776
Jan 26 06:05:10 archimage kernel: raid5: restarting stripe 4849784
Jan 26 06:05:10 archimage kernel: raid5: restarting stripe 830136
Jan 26 06:05:10 archimage kernel: raid5: restarting stripe 4500184
Jan 26 06:05:10 archimage kernel: raid5: restarting stripe 2140888
Jan 26 06:05:10 archimage kernel: raid5: restarting stripe 2271976
Jan 26 06:05:10 archimage kernel: raid5: restarting stripe 1747688
Jan 26 06:05:10 archimage kernel: raid5: restarting stripe 1747696
Jan 26 06:05:10 archimage kernel: raid5: restarting stripe 1747704
Jan 26 06:05:10 archimage kernel: raid5: restarting stripe 3648
Jan 26 06:05:10 archimage kernel: raid5: restarting stripe 3656
Jan 26 06:05:10 archimage kernel: raid5: restarting stripe 3664
Jan 26 06:05:10 archimage kernel: raid5: restarting stripe 4723088
Jan 26 06:05:10 archimage kernel: raid5: restarting stripe 4723096
Jan 26 06:05:10 archimage kernel: raid5: restarting stripe 7387792
Jan 26 06:05:10 archimage kernel: raid5: restarting stripe 7493680
Jan 26 06:05:10 archimage kernel: raid5: restarting stripe 7493688
Jan 26 06:05:10 archimage kernel: raid5: restarting stripe 7406000
Jan 26 06:05:10 archimage kernel: raid5: restarting stripe 7406008
Jan 26 06:05:10 archimage kernel: raid5: restarting stripe 6728400
Jan 26 06:05:10 archimage kernel: raid5: restarting stripe 13068280
Jan 26 06:05:10 archimage kernel: raid5: restarting stripe 14985976
Jan 26 21:58:55 archimage kernel: trying to remove sdd1 from md0 ...
Jan 26 21:58:55 archimage kernel: RAID5 conf printout:
Jan 26 21:58:55 archimage kernel: --- rd:7 wd:6 fd:1
Jan 26 21:58:55 archimage kernel: disk 0, s:0, o:1, n:0 rd:0 us:1
dev:sdb1
Jan 26 21:58:55 archimage kernel: disk 1, s:0, o:1, n:1 rd:1 us:1
dev:sdc1
Jan 26 21:58:55 archimage kernel: disk 2, s:0, o:0, n:2 rd:2 us:1
dev:sdd1
Jan 26 21:58:55 archimage kernel: disk 3, s:0, o:1, n:3 rd:3 us:1
dev:sde1
Jan 26 21:58:55 archimage kernel: disk 4, s:0, o:1, n:4 rd:4 us:1
dev:sdf1
Jan 26 21:58:55 archimage kernel: disk 5, s:0, o:1, n:5 rd:5 us:1
dev:sdg1
Jan 26 21:58:55 archimage kernel: disk 6, s:0, o:1, n:6 rd:6 us:1
dev:sda5
Jan 26 21:58:55 archimage kernel: disk 7, s:0, o:0, n:0 rd:0 us:0
dev:[dev 00:00]
Jan 26 21:58:55 archimage kernel: disk 8, s:0, o:0, n:0 rd:0 us:0
dev:[dev 00:00]
Jan 26 21:58:55 archimage kernel: disk 9, s:0, o:0, n:0 rd:0 us:0
dev:[dev 00:00]
Jan 26 21:58:55 archimage kernel: disk 10, s:0, o:0, n:0 rd:0 us:0
dev:[dev 00:00]
Jan 26 21:58:55 archimage kernel: disk 11, s:0, o:0, n:0 rd:0 us:0
dev:[dev 00:00]
Jan 26 21:58:55 archimage kernel: RAID5 conf printout:
Jan 26 21:58:55 archimage kernel: --- rd:7 wd:6 fd:1
Jan 26 21:58:55 archimage kernel: disk 0, s:0, o:1, n:0 rd:0 us:1
dev:sdb1
Jan 26 21:58:55 archimage kernel: disk 1, s:0, o:1, n:1 rd:1 us:1
dev:sdc1
Jan 26 21:58:55 archimage kernel: disk 2, s:0, o:0, n:2 rd:2 us:0
dev:[dev 00:00]
Jan 26 21:58:55 archimage kernel: disk 3, s:0, o:1, n:3 rd:3 us:1
dev:sde1
Jan 26 21:58:55 archimage kernel: disk 4, s:0, o:1, n:4 rd:4 us:1
dev:sdf1
Jan 26 21:58:55 archimage kernel: disk 5, s:0, o:1, n:5 rd:5 us:1
dev:sdg1
Jan 26 21:58:55 archimage kernel: disk 6, s:0, o:1, n:6 rd:6 us:1
dev:sda5
Jan 26 21:58:55 archimage kernel: disk 7, s:0, o:0, n:0 rd:0 us:0
dev:[dev 00:00]
Jan 26 21:58:55 archimage kernel: disk 8, s:0, o:0, n:0 rd:0 us:0
dev:[dev 00:00]
Jan 26 21:58:55 archimage kernel: disk 9, s:0, o:0, n:0 rd:0 us:0
dev:[dev 00:00]
Jan 26 21:58:55 archimage kernel: disk 10, s:0, o:0, n:0 rd:0 us:0
dev:[dev 00:00]
Jan 26 21:58:55 archimage kernel: disk 11, s:0, o:0, n:0 rd:0 us:0
dev:[dev 00:00]
Jan 26 21:58:55 archimage kernel: unbind<sdd1,6>
Jan 26 21:58:55 archimage kernel: export_rdev(sdd1)
Jan 26 21:58:55 archimage kernel: md: updating md0 RAID superblock on
device
Jan 26 21:58:55 archimage kernel: sdg1 [events: 00000007](write) sdg1's
sb offset: 8807296
Jan 26 21:58:55 archimage kernel: md: updating md0 RAID superblock on
device
Jan 26 21:58:55 archimage kernel: sdg1 [events: 00000008](write) sdg1's
sb offset: 8807296
Jan 26 21:58:55 archimage kernel: sdf1 [events: 00000008](write) sdf1's
sb offset: 8807296
Jan 26 21:58:55 archimage kernel: sdf1 [events: 00000008](write) sdf1's
sb offset: 8807296
Jan 26 21:58:55 archimage kernel: sde1 [events: 00000008](write) sde1's
sb offset: 8807296
Jan 26 21:58:55 archimage kernel: sde1 [events: 00000008](write) sde1's
sb offset: 8807296
Jan 26 21:58:55 archimage kernel: sdc1 [events: 00000008](write) sdc1's
sb offset: 8807296
Jan 26 21:58:55 archimage kernel: sdc1 [events: 00000008](write) sdc1's
sb offset: 8807296
Jan 26 21:58:55 archimage kernel: sdb1 [events: 00000008](write) sdb1's
sb offset: 8807296
Jan 26 21:58:55 archimage kernel: sdb1 [events: 00000008](write) sdb1's
sb offset: 8807296
Jan 26 21:58:55 archimage kernel: sda5 [events: 00000008](write) sda5's
sb offset: 8811520
Jan 26 21:58:55 archimage kernel: sda5 [events: 00000008](write) sda5's
sb offset: 8811520
Jan 26 21:58:55 archimage kernel: .
Jan 26 21:58:55 archimage kernel: .
Jan 26 21:59:04 archimage kernel: trying to hot-add sdd1 to md0 ...
Jan 26 21:59:04 archimage kernel: bind<sdd1,7>
Jan 26 21:59:04 archimage kernel: RAID5 conf printout:
Jan 26 21:59:04 archimage kernel: --- rd:7 wd:6 fd:1
Jan 26 21:59:04 archimage kernel: disk 0, s:0, o:1, n:0 rd:0 us:1
dev:sdb1
Jan 26 21:59:04 archimage kernel: disk 1, s:0, o:1, n:1 rd:1 us:1
dev:sdc1
Jan 26 21:59:04 archimage kernel: disk 2, s:0, o:0, n:2 rd:2 us:0
dev:[dev 00:00]
Jan 26 21:59:04 archimage kernel: disk 3, s:0, o:1, n:3 rd:3 us:1
dev:sde1
Jan 26 21:59:04 archimage kernel: disk 4, s:0, o:1, n:4 rd:4 us:1
dev:sdf1
Jan 26 21:59:04 archimage kernel: disk 5, s:0, o:1, n:5 rd:5 us:1
dev:sdg1
Jan 26 21:59:04 archimage kernel: disk 6, s:0, o:1, n:6 rd:6 us:1
dev:sda5
Jan 26 21:59:04 archimage kernel: disk 7, s:0, o:0, n:0 rd:0 us:0
dev:[dev 00:00]
Jan 26 21:59:05 archimage kernel: disk 8, s:0, o:0, n:0 rd:0 us:0
dev:[dev 00:00]
Jan 26 21:59:05 archimage kernel: disk 9, s:0, o:0, n:0 rd:0 us:0
dev:[dev 00:00]
Jan 26 21:59:05 archimage kernel: disk 10, s:0, o:0, n:0 rd:0 us:0
dev:[dev 00:00]
Jan 26 21:59:05 archimage kernel: disk 11, s:0, o:0, n:0 rd:0 us:0
dev:[dev 00:00]
Jan 26 21:59:05 archimage kernel: RAID5 conf printout:
Jan 26 21:59:05 archimage kernel: --- rd:7 wd:6 fd:1
Jan 26 21:59:05 archimage kernel: disk 0, s:0, o:1, n:0 rd:0 us:1
dev:sdb1
Jan 26 21:59:05 archimage kernel: disk 1, s:0, o:1, n:1 rd:1 us:1
dev:sdc1
Jan 26 21:59:05 archimage kernel: disk 2, s:0, o:0, n:2 rd:2 us:0
dev:[dev 00:00]
Jan 26 21:59:05 archimage kernel: disk 3, s:0, o:1, n:3 rd:3 us:1
dev:sde1
Jan 26 21:59:05 archimage kernel: disk 4, s:0, o:1, n:4 rd:4 us:1
dev:sdf1
Jan 26 21:59:05 archimage kernel: disk 5, s:0, o:1, n:5 rd:5 us:1
dev:sdg1
Jan 26 21:59:05 archimage kernel: disk 6, s:0, o:1, n:6 rd:6 us:1
dev:sda5
Jan 26 21:59:05 archimage kernel: disk 7, s:1, o:0, n:7 rd:7 us:1
dev:sdd1
Jan 26 21:59:05 archimage kernel: disk 8, s:0, o:0, n:0 rd:0 us:0
dev:[dev 00:00]
Jan 26 21:59:05 archimage kernel: disk 9, s:0, o:0, n:0 rd:0 us:0
dev:[dev 00:00]
Jan 26 21:59:05 archimage kernel: disk 10, s:0, o:0, n:0 rd:0 us:0
dev:[dev 00:00]
Jan 26 21:59:05 archimage kernel: disk 11, s:0, o:0, n:0 rd:0 us:0
dev:[dev 00:00]
Jan 26 21:59:05 archimage kernel: md: updating md0 RAID superblock on
device
Jan 26 21:59:05 archimage kernel: sdd1 [events: 00000009](write) sdd1's
sb offset: 8807296
Jan 26 21:59:05 archimage kernel: md: updating md0 RAID superblock on
device
Jan 26 21:59:05 archimage kernel: sdd1 [events: 0000000a](write) sdd1's
sb offset: 8807296
Jan 26 21:59:05 archimage kernel: sdg1 [events: 0000000a](write) sdg1's
sb offset: 8807296
Jan 26 21:59:05 archimage kernel: sdg1 [events: 0000000a](write) sdg1's
sb offset: 8807296
Jan 26 21:59:05 archimage kernel: sdf1 [events: 0000000a](write) sdf1's
sb offset: 8807296
Jan 26 21:59:05 archimage kernel: sdf1 [events: 0000000a](write) sdf1's
sb offset: 8807296
Jan 26 21:59:05 archimage kernel: sde1 [events: 0000000a](write) sde1's
sb offset: 8807296
Jan 26 21:59:05 archimage kernel: sde1 [events: 0000000a](write) sde1's
sb offset: 8807296
Jan 26 21:59:05 archimage kernel: sdc1 [events: 0000000a](write) sdc1's
sb offset: 8807296
Jan 26 21:59:05 archimage kernel: sdc1 [events: 0000000a](write) sdc1's
sb offset: 8807296
Jan 26 21:59:06 archimage kernel: sdb1 [events: 0000000a](write) sdb1's
sb offset: 8807296
Jan 26 21:59:06 archimage kernel: sdb1 [events: 0000000a](write) sdb1's
sb offset: 8807296
Jan 26 21:59:06 archimage kernel: sda5 [events: 0000000a](write) sda5's
sb offset: 8811520
Jan 26 21:59:06 archimage kernel: sda5 [events: 0000000a](write) sda5's
sb offset: 8811520
Jan 26 21:59:06 archimage kernel: .
Jan 26 21:59:06 archimage kernel: .
Jan 26 21:59:06 archimage kernel: md: recovery thread got woken up ...
Jan 26 21:59:06 archimage kernel: md0: resyncing spare disk sdd1 to
replace failed disk
Jan 26 21:59:06 archimage kernel: RAID5 conf printout:
Jan 26 21:59:06 archimage kernel: --- rd:7 wd:6 fd:1
Jan 26 21:59:06 archimage kernel: disk 0, s:0, o:1, n:0 rd:0 us:1
dev:sdb1
Jan 26 21:59:06 archimage kernel: disk 1, s:0, o:1, n:1 rd:1 us:1
dev:sdc1
Jan 26 21:59:06 archimage kernel: disk 2, s:0, o:0, n:2 rd:2 us:0
dev:[dev 00:00]
Jan 26 21:59:06 archimage kernel: disk 3, s:0, o:1, n:3 rd:3 us:1
dev:sde1
Jan 26 21:59:06 archimage kernel: disk 4, s:0, o:1, n:4 rd:4 us:1
dev:sdf1
Jan 26 21:59:06 archimage kernel: disk 5, s:0, o:1, n:5 rd:5 us:1
dev:sdg1
Jan 26 21:59:06 archimage kernel: disk 6, s:0, o:1, n:6 rd:6 us:1
dev:sda5
Jan 26 21:59:06 archimage kernel: disk 7, s:1, o:0, n:7 rd:7 us:1
dev:sdd1
Jan 26 21:59:06 archimage kernel: disk 8, s:0, o:0, n:0 rd:0 us:0
dev:[dev 00:00]
Jan 26 21:59:06 archimage kernel: disk 9, s:0, o:0, n:0 rd:0 us:0
dev:[dev 00:00]
Jan 26 21:59:06 archimage kernel: disk 10, s:0, o:0, n:0 rd:0 us:0
dev:[dev 00:00]
Jan 26 21:59:06 archimage kernel: disk 11, s:0, o:0, n:0 rd:0 us:0
dev:[dev 00:00]
Jan 26 21:59:06 archimage kernel: RAID5 conf printout:
Jan 26 21:59:06 archimage kernel: --- rd:7 wd:6 fd:1
Jan 26 21:59:06 archimage kernel: disk 0, s:0, o:1, n:0 rd:0 us:1
dev:sdb1
Jan 26 21:59:06 archimage kernel: disk 1, s:0, o:1, n:1 rd:1 us:1
dev:sdc1
Jan 26 21:59:06 archimage kernel: disk 2, s:0, o:0, n:2 rd:2 us:0
dev:[dev 00:00]
Jan 26 21:59:06 archimage kernel: disk 3, s:0, o:1, n:3 rd:3 us:1
dev:sde1
Jan 26 21:59:06 archimage kernel: disk 4, s:0, o:1, n:4 rd:4 us:1
dev:sdf1
Jan 26 21:59:06 archimage kernel: disk 5, s:0, o:1, n:5 rd:5 us:1
dev:sdg1
Jan 26 21:59:06 archimage kernel: disk 6, s:0, o:1, n:6 rd:6 us:1
dev:sda5
Jan 26 21:59:06 archimage kernel: disk 7, s:1, o:1, n:7 rd:7 us:1
dev:sdd1
Jan 26 21:59:06 archimage kernel: disk 8, s:0, o:0, n:0 rd:0 us:0
dev:[dev 00:00]
Jan 26 21:59:06 archimage kernel: disk 9, s:0, o:0, n:0 rd:0 us:0
dev:[dev 00:00]
Jan 26 21:59:06 archimage kernel: disk 10, s:0, o:0, n:0 rd:0 us:0
dev:[dev 00:00]
Jan 26 21:59:06 archimage kernel: disk 11, s:0, o:0, n:0 rd:0 us:0
dev:[dev 00:00]
Jan 26 21:59:06 archimage kernel: md: syncing RAID array md0
Jan 26 21:59:06 archimage kernel: md: minimum _guaranteed_
reconstruction speed: 100 KB/sec.
Jan 26 21:59:06 archimage kernel: md: using maximum available idle IO
bandwith for reconstruction.
Jan 26 21:59:06 archimage kernel: md: using 1536k window.
Jan 27 00:03:24 archimage kernel: md: md0: sync done.
Jan 27 00:03:24 archimage kernel: RAID5 conf printout:
Jan 27 00:03:24 archimage kernel: --- rd:7 wd:6 fd:1
Jan 27 00:03:24 archimage kernel: disk 0, s:0, o:1, n:0 rd:0 us:1
dev:sdb1
Jan 27 00:03:24 archimage kernel: disk 1, s:0, o:1, n:1 rd:1 us:1
dev:sdc1
Jan 27 00:03:24 archimage kernel: disk 2, s:0, o:0, n:2 rd:2 us:0
dev:[dev 00:00]
Jan 27 00:03:24 archimage kernel: disk 3, s:0, o:1, n:3 rd:3 us:1
dev:sde1
Jan 27 00:03:24 archimage kernel: disk 4, s:0, o:1, n:4 rd:4 us:1
dev:sdf1
Jan 27 00:03:24 archimage kernel: disk 5, s:0, o:1, n:5 rd:5 us:1
dev:sdg1
Jan 27 00:03:24 archimage kernel: disk 6, s:0, o:1, n:6 rd:6 us:1
dev:sda5
Jan 27 00:03:24 archimage kernel: disk 7, s:1, o:1, n:7 rd:7 us:1
dev:sdd1
Jan 27 00:03:24 archimage kernel: disk 8, s:0, o:0, n:0 rd:0 us:0
dev:[dev 00:00]
Jan 27 00:03:24 archimage kernel: disk 9, s:0, o:0, n:0 rd:0 us:0
dev:[dev 00:00]
Jan 27 00:03:24 archimage kernel: disk 10, s:0, o:0, n:0 rd:0 us:0
dev:[dev 00:00]
Jan 27 00:03:24 archimage kernel: disk 11, s:0, o:0, n:0 rd:0 us:0
dev:[dev 00:00]
Jan 27 00:03:24 archimage kernel: RAID5 conf printout:
Jan 27 00:03:24 archimage kernel: --- rd:7 wd:7 fd:0
Jan 27 00:03:24 archimage kernel: disk 0, s:0, o:1, n:0 rd:0 us:1
dev:sdb1
Jan 27 00:03:24 archimage kernel: disk 1, s:0, o:1, n:1 rd:1 us:1
dev:sdc1
Jan 27 00:03:24 archimage kernel: disk 2, s:0, o:1, n:2 rd:2 us:1
dev:sdd1
Jan 27 00:03:24 archimage kernel: disk 3, s:0, o:1, n:3 rd:3 us:1
dev:sde1
Jan 27 00:03:24 archimage kernel: disk 4, s:0, o:1, n:4 rd:4 us:1
dev:sdf1
Jan 27 00:03:24 archimage kernel: disk 5, s:0, o:1, n:5 rd:5 us:1
dev:sdg1
Jan 27 00:03:24 archimage kernel: disk 6, s:0, o:1, n:6 rd:6 us:1
dev:sda5
Jan 27 00:03:24 archimage kernel: disk 7, s:0, o:0, n:7 rd:7 us:0
dev:[dev 00:00]
Jan 27 00:03:24 archimage kernel: disk 8, s:0, o:0, n:0 rd:0 us:0
dev:[dev 00:00]
Jan 27 00:03:24 archimage kernel: disk 9, s:0, o:0, n:0 rd:0 us:0
dev:[dev 00:00]
Jan 27 00:03:24 archimage kernel: disk 10, s:0, o:0, n:0 rd:0 us:0
dev:[dev 00:00]
Jan 27 00:03:24 archimage kernel: disk 11, s:0, o:0, n:0 rd:0 us:0
dev:[dev 00:00]
Jan 27 00:03:24 archimage kernel: md: updating md0 RAID superblock on
device
Jan 27 00:03:24 archimage kernel: sdd1 [events: 0000000b](write) sdd1's
sb offset: 8807296
Jan 27 00:03:24 archimage kernel: md: updating md0 RAID superblock on
device
Jan 27 00:03:24 archimage kernel: sdd1 [events: 0000000c](write) sdd1's
sb offset: 8807296
Jan 27 00:03:24 archimage kernel: sdg1 [events: 0000000c](write) sdg1's
sb offset: 8807296
Jan 27 00:03:24 archimage kernel: sdg1 [events: 0000000c](write) sdg1's
sb offset: 8807296
Jan 27 00:03:24 archimage kernel: sdf1 [events: 0000000c](write) sdf1's
sb offset: 8807296
Jan 27 00:03:24 archimage kernel: sdf1 [events: 0000000c](write) sdf1's
sb offset: 8807296
Jan 27 00:03:25 archimage kernel: sde1 [events: 0000000c](write) sde1's
sb offset: 8807296
Jan 27 00:03:25 archimage kernel: sde1 [events: 0000000c](write) sde1's
sb offset: 8807296
Jan 27 00:03:25 archimage kernel: sdc1 [events: 0000000c](write) sdc1's
sb offset: 8807296
Jan 27 00:03:25 archimage kernel: sdc1 [events: 0000000c](write) sdc1's
sb offset: 8807296
Jan 27 00:03:25 archimage kernel: sdb1 [events: 0000000c](write) sdb1's
sb offset: 8807296
Jan 27 00:03:25 archimage kernel: sdb1 [events: 0000000c](write) sdb1's
sb offset: 8807296
Jan 27 00:03:25 archimage kernel: sda5 [events: 0000000c](write) sda5's
sb offset: 8811520
Jan 27 00:03:25 archimage kernel: .
Jan 27 00:03:25 archimage kernel: sda5 [events: 0000000c](write) sda5's
sb offset: 8811520
Jan 27 00:03:25 archimage kernel: .
Jan 27 00:03:25 archimage kernel: md: recovery thread finished ...
jwk wrote:
>
> On Sat, 27 Jan 2001 04:46:43 GMT, The Archimage
> <[EMAIL PROTECTED]> wrote:
> >OK, here's the scenario:
> >
> >I have a Compaq Proliant 2500R, dual PPro 200's, a gig of EDO ECC RAM,
> >and an external Compaq F1 Raid array with 9 identical Seagate 9.1 gig
> >SCSI drives. Several months ago (right when RH6.2 was released), I
> >installed RH6.2 in GUI mode, set up a 24 meg partition mounted on /boot,
> >and the rest of the array as /dev/md0, a RAID5 array, mounted on /.
> >
> >The server was at a remote site, and I have to admit I didn't watch the
> >logs as closely as I should have. I ssh'd in on January 16th, and
> >noticed in /var/log/messages that a "disk failure" had occured on one of
> >the disks, and the array was continuing on 6 disks. I used
> >raidhotremove to remove the drive from the stripe set, and then
> >raidhotadd to add it back in and regenerate the stripe set. The server
> >crashed, showing a second drive "failed." I lost all the data on the
> >array.
> >
> First of all, please trim down the list of newsgroups. Note the F'Up.
>
> Second, are there any log-messages that might indicate WHY some drives
> failed?
------------------------------
Subject: Re: Help with error msg's and cable modem prob
From: [EMAIL PROTECTED] (Neuromancer)
Date: Sat, 27 Jan 2001 14:02:11 GMT
As far as your hostname goes, you need to put in the FULL name such as
c123456-a.chmpgn1.il.home.com. (Just .home.com won't work.)
As for the dependency errors, it looks like some software wasn't
installed properly. What the system thinks it has and what you actually
have don't match, so it is upset. I don't really know how to fix this
one. Did you use RPM for the install?
[EMAIL PROTECTED] (NoClue) wrote in
<[EMAIL PROTECTED]>:
>newaliases: fatal: My hostname c123456-a is not a fully qualifiedname
>- set
>myhostname or mydomain in /etc/postfix/main.cf
>Jan 27 00:32:18 c123456-a postfix: postmap: fatal: My hostname
>c985883-a is
>not a fully qualified name
>
>
> modprobe: Note: /etc/conf.modules is more recent than
>/lib/modules/2.2.15-4mdk/modules.dep
> [...]
------------------------------
Reply-To: "Dave Thompson" <[EMAIL PROTECTED]>
From: "Dave Thompson" <[EMAIL PROTECTED]>
Subject: hangs on verifying dmi pool with hard drive
Date: Sat, 27 Jan 2001 14:02:45 GMT
I have a linux box that boots fine from a floppy-installed kernel but hangs
on verifying dmi pool if I try and boot from the hard disk. I've ignored it
for several months because I'm booting from floppy anyway, but now want to
change over and boot from the hard drive where /root is located and have
re-discovered this issue.
Any ideas / suggestions ?
Thanks.
Dave
------------------------------
** FOR YOUR REFERENCE **
The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:
Internet: [EMAIL PROTECTED]
You can send mail to the entire list by posting to comp.os.linux.setup.
Linux may be obtained via one of these FTP sites:
ftp.funet.fi pub/Linux
tsx-11.mit.edu pub/linux
sunsite.unc.edu pub/Linux
End of Linux-Setup Digest
******************************
