Hi. This moring after fatal "ATA Abnormal Status" machine freeze, and
after reboot it said on syslog:
Oct 30 12:35:15 prometeo kernel: DMA write timed out
Oct 30 12:35:16 prometeo kernel: parport0: BUSY timeout (1) in
compat_write_block_pio
what means this error?
--
Openclose.it - Idee per il s
Timo Railo wrote:
> Thanks Benedict,
>
> this is what happened (also tried just -d1).
>
> hdparm -d 1 -c 1 /dev/hda
>
> /dev/hda:
> setting 32-bit IO_support flag to 1
> setting using_dma to 1 (on)
> HDIO_SET_DMA failed: Operation not permitted
> IO_support = 1 (32-bit)
> using_dma
Hi Timo.
On Wednesday 18 February 2004 08:19, Timo Railo wrote:
> Thanks Benedict,
>
> this is what happened (also tried just -d1).
>
> hdparm -d 1 -c 1 /dev/hda
>
> /dev/hda:
> setting 32-bit IO_support flag to 1
> setting using_dma to 1 (on)
> HDIO_SET_DMA failed: Operation not permitted
>
Thanks Benedict,
this is what happened (also tried just -d1).
hdparm -d 1 -c 1 /dev/hda
/dev/hda:
setting 32-bit IO_support flag to 1
setting using_dma to 1 (on)
HDIO_SET_DMA failed: Operation not permitted
IO_support = 1 (32-bit)
using_dma= 0 (off)
Man this is tough...
Timo
Timo
Timo Railo wrote:
> Something is wacky. Any idea what could be causing such a poor
> performance. Quite new hardware, normal IDE, disks in separate BUSses.
>
> tmoby:~# hdparm -T /dev/md0
>
> hdparm -Tt /dev/hda /dev/hdc /dev/md0
>
> /dev/hda:
> Timing buffer-cache reads: 1828 MB in 2.00 secon
Something is wacky. Any idea what could be causing such a poor
performance. Quite new hardware, normal IDE, disks in separate BUSses.
tmoby:~# hdparm -T /dev/md0
hdparm -Tt /dev/hda /dev/hdc /dev/md0
/dev/hda:
Timing buffer-cache reads: 1828 MB in 2.00 seconds = 914.00 MB/sec
Timing buffe
[ Either me or my mail program is going nutty... I could have sworn
that I replied to the list, not you Justin. Sorry. ]
After much much headache (and almost buying new serial ata raid hw
setup etc.), I got it to work (almost). Solution: compiling my own
kernel. You should have warned me how
On Thursday 12 February 2004 07:05, you wrote:
[snip]
> >
> > You're going to have problems with that setup. You can't have a raid
> > using
> > part of a disk (hdc2) and the entire disk (hdc). You should be using
> > two
> > partitions, like this:
> > # cat /etc/raid/raidtab
> > raiddev /dev/md0
On Monday 09 February 2004 11:05, Timo Railo wrote:
[snip]
> > Your fstab file for your raid device is correct. What does your /etc/
> > raidtab and /etc/raid/raidtab look like? /etc/raidtab should be a link
> > to /etc/raid/raidtab. Post the contents of /etc/raid/raidtab, and we
> > may be more
I've tried putting it to /etc/fstab, but getting the error on boot
time. And since it's remote computer, it's a little inconvenient cause
it won't continue the bootup process without keyboard input. Here is
my
fstab setup:
You should use the option "noauto" instead of "defaults" while you're
debu
On Monday 09 February 2004 10:16, Timo Railo wrote:
> Hi David,
>
> thank you for your reply!
>
> I've tried putting it to /etc/fstab, but getting the error on boot
> time. And since it's remote computer, it's a little inconvenient cause
> it won't continue the bootup process without keyboard input
Hi David,
thank you for your reply!
I've tried putting it to /etc/fstab, but getting the error on boot
time. And since it's remote computer, it's a little inconvenient cause
it won't continue the bootup process without keyboard input. Here is my
fstab setup:
/dev/hda1 / ex
Timo Railo wrote:
> Hi!
>
> I'm having problems getting software raid to work with my IDE drives. I
> had Redhat9 installed previously on the same machine (with working
> software raid setup), but I'm now moving to Debian.
>
> My kernel is 2.4.18-bf2.4 and has support for RAID1, which I'm trying
On Sun, 2004-02-08 at 16:38, Timo Railo wrote:
> Hi!
>
> I'm having problems getting software raid to work with my IDE drives. I
> had Redhat9 installed previously on the same machine (with working
> software raid setup), but I'm now moving to Debian.
>
> My kernel is 2.4.18-bf2.4 and has sup
Hi!
I'm having problems getting software raid to work with my IDE drives. I
had Redhat9 installed previously on the same machine (with working
software raid setup), but I'm now moving to Debian.
My kernel is 2.4.18-bf2.4 and has support for RAID1, which I'm trying
to create. I'm following t
Solved the problem myself.
And found a alternative way to set up raid.
I have to identical disk hda, hdc.
1)
Install debian on hda.
hda1/boot
hda2/
hda3Swap
2)
config raidtab with hdc af failed.
md0 for boot
md1 for root
3)
config fstab and lilo.conf
md0 for boot
md1 for root
4)
I have a raid1 device for which fsck returns a error.
It says that the physical size of the device is 26000k but
that the superblock says that the size is 26066k.
if I run mkraid --upgrade it tells me that
the physical size is 26066k and that the superblock
starts at 26000k.
What should i do to m
>hello
>
>after a reboot (caused by a power fail) my raid was checked with ckraid and
>brought back into sync, but e2fsck sais, that the md-device-partition has
>zero length??
you have to restart md-device in /etc/init.d using mdutils
just a tip: use ckraid --fix
>the problem is, that my /usr /
hello
after a reboot (caused by a power fail) my raid was checked with ckraid and
brought back into sync, but e2fsck sais, that the md-device-partition has
zero length??
the problem is, that my /usr /home and /var on the md-device resist
any hints?
--
until next mail B-)
Peter
--
19 matches
Mail list logo
