Board index Freebsd

Help me please! FreeBSD 3.4 & HDD 13Gb

Help me please! FreeBSD 3.4 & HDD 13Gb

Post by z.. » Sat, 30 Sep 2000 04:00:00



Hello!



I have the problem. The version of FreeBSD is 3.4-RELEASE. The problem
the
following: i get the error messages to console of the HDD IDE <FUJITSU
MPE3136AH> (~13 Gb). I have the two equality HDD on secondary IDE
controller
and a FreeBSD 3.4 curses to both HDDes. I have attached below the dmesg
message of FreeBSD and error logs. The problen occurs when i try run a
bad144 utility (bad144 -v /dev/rwd2c for example) or i run
/stand/sysinstall
and try to execute a fdisk (to mark a bad block scan bit of slice and
write
command /W/). Please help me what is problem?

Sep 29 21:24:04 ping /kernel: Timecounter "i8254"  frequency 1193182 Hz
Sep 29 21:24:04 ping /kernel: CPU: AMD Athlon(tm) Processor (700.03-MHz
686-class CPU)
Sep 29 21:24:04 ping /kernel: Origin = "AuthenticAMD"  Id = 0x622
Stepping
= 2
Sep 29 21:24:04 ping /kernel:
Features=0x183f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,C
MOV,
PAT,PSE36,MMX,FXSR>
Sep 29 21:24:04 ping /kernel: AMD Features=0xc0400000<<b22>,<b30>,3DNow!
Sep 29 21:24:04 ping /kernel: real memory  = 268435456 (262144K bytes)
Sep 29 21:24:04 ping /kernel: avail memory = 258707456 (252644K bytes)
Sep 29 21:24:04 ping /kernel: Preloaded elf kernel "kernel" at
0xc0255000.
Sep 29 21:24:04 ping /kernel: Pentium Pro MTRR support enabled
Sep 29 21:24:04 ping /kernel: Probing for devices on PCI bus 0:
Sep 29 21:24:04 ping /kernel: chip0: <Host to PCI bridge (vendor=1106
device=0691)> rev 0x02 on pci0.0.0
Sep 29 21:24:04 ping /kernel: chip1: <VIA 82C598MVP (Apollo MVP3) PCI-
PCI
bridge> rev 0x00 on pci0.1.0
Sep 29 21:24:04 ping /kernel: chip2: <PCI to ISA bridge (vendor=1106
device=0686)> rev 0x21 on pci0.4.0
Sep 29 21:24:04 ping /kernel: ide_pci0: <VIA 82C586x (Apollo) Bus-
master IDE
controller> rev 0x10 on pci0.4.1
Sep 29 21:24:04 ping /kernel: chip3: <Host to PCI bridge (vendor=1106
device=3057)> rev 0x30 on pci0.4.4
Sep 29 21:24:04 ping /kernel: vga0: <Alliance model 643d VGA-compatible
display device> rev 0x02 on pci0.11.0
Sep 29 21:24:04 ping /kernel: Probing for devices on PCI bus 1:
Sep 29 21:24:04 ping /kernel: Probing for PnP devices:
Sep 29 21:24:04 ping /kernel: Probing for devices on the ISA bus:
Sep 29 21:24:04 ping /kernel: sc0 on isa
Sep 29 21:24:04 ping /kernel: sc0: VGA color <16 virtual consoles,
flags=0x0>
Sep 29 21:24:04 ping /kernel: atkbdc0 at 0x60-0x6f on motherboard
Sep 29 21:24:04 ping /kernel: atkbd0 irq 1 on isa
Sep 29 21:24:04 ping /kernel: psm0 irq 12 on isa
Sep 29 21:24:04 ping /kernel: psm0: model NetMouse, device ID 0
Sep 29 21:24:04 ping /kernel: sio0: configured irq 4 not in bitmap of
probed
irqs 0
Sep 29 21:24:04 ping /kernel: sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on
isa
Sep 29 21:24:04 ping /kernel: sio0: type 8250
Sep 29 21:24:04 ping /kernel: sio1: configured irq 3 not in bitmap of
probed
irqs 0
Sep 29 21:24:04 ping /kernel: sio1 not found at 0x2f8
Sep 29 21:24:04 ping /kernel: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa
Sep 29 21:24:04 ping /kernel: fdc0: FIFO enabled, 8 bytes threshold
Sep 29 21:24:04 ping /kernel: fd0: 1.44MB 3.5in
Sep 29 21:24:04 ping /kernel: wdc0 at 0x1f0-0x1f7 irq 14 on isa
Sep 29 21:24:04 ping /kernel: wdc0: unit 0 (wd0): <ST38410A>
Sep 29 21:24:04 ping /kernel: wd0: 8223MB (16841664 sectors), 16708
cyls, 16
heads, 63 S/T, 512 B/S
Sep 29 21:24:04 ping /kernel: wdc0: unit 1 (wd1): <ST38410A>
Sep 29 21:24:04 ping /kernel: wd1: 8223MB (16841664 sectors), 16708
cyls, 16
heads, 63 S/T, 512 B/S
Sep 29 21:24:04 ping /kernel: wdc1 at 0x170-0x177 irq 15 on isa
Sep 29 21:24:04 ping /kernel: wdc1: unit 0 (wd2): <FUJITSU MPE3136AH>
Sep 29 21:24:04 ping /kernel: wd2: 13027MB (26679688 sectors), 26467
cyls,
16 heads, 63 S/T, 512 B/S
Sep 29 21:24:04 ping /kernel: wdc1: unit 1 (wd3): <FUJITSU MPE3136AH>
Sep 29 21:24:04 ping /kernel: wd3: 13027MB (26679688 sectors), 26467
cyls,
16 heads, 63 S/T, 512 B/S
Sep 29 21:24:04 ping /kernel: ppc0 not found
Sep 29 21:24:04 ping /kernel: vga0 at 0x3b0-0x3df maddr 0xa0000 msize
131072
on isa
Sep 29 21:24:04 ping /kernel: npx0 on motherboard
Sep 29 21:24:04 ping /kernel: npx0: INT 16 interface
Sep 29 21:24:04 ping /kernel: changing root device to wd0s1a
--------------------------------

I have run the bad144 -v /dev/rwd2c and have gotten the following
errors:

Sep 29 21:31:35 ping /kernel: wd2s1h: hard error writing fsbn 16644487
(wd2s1 bn 26679687; cn 20273 tn 59 sn 6) (status 51<rdy,seekdone,err>
error
10<no_id>)
Sep 29 21:33:55 ping /kernel: wd2c: hard error reading fsbn 26679681
(wd2 bn
26679681; cn 20273 tn 59 sn 0) (status 59<rdy,seekdone,drq,err> error
10<no_id>)
Sep 29 21:33:55 ping /kernel: wd2c: hard error reading fsbn 26679683
(wd2 bn
26679683; cn 20273 tn 59 sn 2) (status 59<rdy,seekdone,drq,err> error
10<no_id>)
Sep 29 21:33:55 ping /kernel: wd2c: hard error reading fsbn 26679685
(wd2 bn
26679685; cn 20273 tn 59 sn 4) (status 59<rdy,seekdone,drq,err> error
10<no_id>)
Sep 29 21:33:55 ping /kernel: wd2c: hard error reading fsbn 26679687
(wd2 bn
26679687; cn 20273 tn 59 sn 6) (status 59<rdy,seekdone,drq,err> error
10<no_id>)
Sep 29 21:34:50 ping /kernel: wd2c: hard error reading fsbn 26679681
(wd2 bn
26679681; cn 20273 tn 59 sn 0) (status 59<rdy,seekdone,drq,err> error
10<no_id>)
Sep 29 21:34:50 ping /kernel: wd2c: hard error reading fsbn 26679683
(wd2 bn
26679683; cn 20273 tn 59 sn 2) (status 59<rdy,seekdone,drq,err> error
10<no_id>)
Sep 29 21:34:50 ping /kernel: wd2c: hard error reading fsbn 26679685
(wd2 bn
26679685; cn 20273 tn 59 sn 4) (status 59<rdy,seekdone,drq,err> error
10<no_id>)
Sep 29 21:34:51 ping /kernel: wd2c: hard error reading fsbn 26679687
(wd2 bn
26679687; cn 20273 tn 59 sn 6) (status 59<rdy,seekdone,drq,err> error
10<no_id>)

I have run the bad144 -v /dev/rwd3c and have gotten the following
errors:

Sep 29 21:35:03 ping /kernel: wd3c: hard error reading fsbn 26679625
(wd3 bn
26679625; cn 1660 tn 186 sn 7) (status 59<rdy,seekdone,drq,err> error
10<no_id>)
Sep 29 21:35:03 ping /kernel: wd3c: hard error reading fsbn 26679627
(wd3 bn
26679627; cn 1660 tn 186 sn 9) (status 59<rdy,seekdone,drq,err> error
10<no_id>)
Sep 29 21:35:03 ping /kernel: wd3c: hard error reading fsbn 26679629
(wd3 bn
26679629; cn 1660 tn 186 sn 11) (status 59<rdy,seekdone,drq,err> error
10<no_id>)
Sep 29 21:35:04 ping /kernel: wd3c: hard error reading fsbn 26679631
(wd3 bn
26679631; cn 1660 tn 186 sn 13) (status 59<rdy,seekdone,drq,err> error
10<no_id>)
Sep 29 21:35:04 ping /kernel: wd3c: hard error reading fsbn 26679633
(wd3 bn
26679633; cn 1660 tn 186 sn 15) (status 59<rdy,seekdone,drq,err> error
10<no_id>)
Sep 29 21:38:17 ping /kernel: wd3c: hard error reading fsbn 26679625
(wd3 bn
26679625; cn 1660 tn 186 sn 7) (status 59<rdy,seekdone,drq,err> error
10<no_id>)
Sep 29 21:38:17 ping /kernel: wd3c: hard error reading fsbn 26679627
(wd3 bn
26679627; cn 1660 tn 186 sn 9) (status 59<rdy,seekdone,drq,err> error
10<no_id>)

---
Best regards,

Sent via Deja.com http://www.deja.com/
Before you buy.

 
 
 
Top

1. Help with mail on FreeBSD 3.4, please...

I'm really buried trying to get my FreeBSD 3.4 system working
as I had 2.1.5 before it so I'm way behind in news.  Thus, I'll

e-mail if you don't think it's of general interest.  Reply-to: is
set properly.

I'm finally updating my FreeBSD box at home from 2.1.5 to 3.4.

I find that on 3.4, if I send mail to a local user, it causes ppp
to dial out; that didn't happen on 2.1.5.  Unfortunately, I don't
remember if 2.1.5 was that way by default or if I changed something
to fix it.

I use /usr/bin/mail and am running sendmail as I had done on 2.1.5.
Naturally, its a newer version of sendmail on 3.4.

I simply copied /usr/src/etc/sendmail/freebsd.mc to quail.mc in
that same directory, added four lines (see diffs below), and
created quail.cf from that and copied quail.cf to /etc/sendmail.cf
after checking the original into RCS.

PC% cd /usr/src/etc/sendmail
PC% diff freebsd.mc quail.mc
37c37
< #  This is a generic configuration file for 4.4 BSD-based
systems.
---
system.
64a65,68
PC%

That's essentially what I did with 2.1.5, as I recall although
there is certainly the possibility that I changed something in
sendmail.cf directly as a result of suggestions from this news
group.

I assume that the problem is that mail or sendmail is trying to do
a DNS lookup but why?  If I try to "mail crs" that's obviously
local.  Why try a DNS lookup?  What am I overlooking?

Thanks for any help with this and for taking the trouble to Cc: a

--
Best regards,

Charlie "Older than dirt" Sorsby     Edgewood,  NM     "I'm the NRA!"

2. Q: Applixware

3. Help please -- FreeBSD 3.4 supported SCSI controllers ???

4. AIX3.2 & AFS

5. Installing FreeBSD 3.4 ... Please advise

6. gnuplot3d - how to get it to work

7. FreeBSD 3.4-RELEASE & DD-UP

8. Applix to Linux users: please bend over...

9. Freebsd 3.4 & licq 0.81 port

10. FreeBSD 3.4 with AT&T worldnet

11. Thinkpad 600 & FreeBSD 3.4/4.0 battle

12. Oracle & FreeBSD 3.4

13. Netscape 4.7 for FreeBSD 2.2x does not run on FreeBSD 3.4


All times are UTC
Board index