Jonathan Dill
2006-12-15 15:01:21 UTC
Maybe this is a shot in the dark, I have already asked on the Linux
PowerEdge mailing list, just hoping that someone has had a very similar
problem and can help narrow down all of the possibilities.
I have a PowerEdge 1900 with Ubuntu Dapper 6.06.1 LTS x86_64 with dual
Xeon 5110 processors, PERC 5/i with 2 SATA drives in RAID1, 3 more
drives on motherboard SATA with LVM for the backup data. The server is
stable as long as I don't run BackupPC. I called Dell and they
recommended taking out the Intel add-in gigabit card and try the onboard
Broadcom, tried that and it still crashed with the same error, so it's
not the network card. I have run a regular rsync of about 200 GB from
the server to another computer, and that worked fine, and that was more
CPU and I/O intensive than BackupPC. I really need to get some more
time to do more hardware diagnostics, but I'm having to do it off hours
and get someone there to "escort" me so it's been hard to schedule downtime.
I disabled all but one host then ran "BackupPC_dump -v -f host" from the
console and also a tail of /var/log/messages, there were no errors in
the system log, the dump was just a ways into the stream of dumping
files, create / pool, toward then end there are a few "Can't link X to"
errors. I started the dump around 11pm and it crashed at 4:13am, this
was only supposed to be about 18 GB so it seems like it should have been
quicker than that.
There are a lot of hardware things that it could be, CPU, memory, riser
board, PERC controller, motherboard. The disks that it is dumping to
are on the motherboard SATA controller and not on the PERC. Any ideas
that could help me to pinpoint this problem?
Thanks,
Jonathan
PowerEdge mailing list, just hoping that someone has had a very similar
problem and can help narrow down all of the possibilities.
I have a PowerEdge 1900 with Ubuntu Dapper 6.06.1 LTS x86_64 with dual
Xeon 5110 processors, PERC 5/i with 2 SATA drives in RAID1, 3 more
drives on motherboard SATA with LVM for the backup data. The server is
stable as long as I don't run BackupPC. I called Dell and they
recommended taking out the Intel add-in gigabit card and try the onboard
Broadcom, tried that and it still crashed with the same error, so it's
not the network card. I have run a regular rsync of about 200 GB from
the server to another computer, and that worked fine, and that was more
CPU and I/O intensive than BackupPC. I really need to get some more
time to do more hardware diagnostics, but I'm having to do it off hours
and get someone there to "escort" me so it's been hard to schedule downtime.
I disabled all but one host then ran "BackupPC_dump -v -f host" from the
console and also a tail of /var/log/messages, there were no errors in
the system log, the dump was just a ways into the stream of dumping
files, create / pool, toward then end there are a few "Can't link X to"
errors. I started the dump around 11pm and it crashed at 4:13am, this
was only supposed to be about 18 GB so it seems like it should have been
quicker than that.
There are a lot of hardware things that it could be, CPU, memory, riser
board, PERC controller, motherboard. The disks that it is dumping to
are on the motherboard SATA controller and not on the PERC. Any ideas
that could help me to pinpoint this problem?
Thanks,
Jonathan