invalidate: dirty buffer

[Natman]

"Jim Gifford" <giff...@linkline.com> wrote in message
news:ul428ch...@corp.supernews.com...
> I am a KT7A-Raid motherboard user. I have moved linux to use 100% of my
> RAID. When I did so I used the hpt3xx-opensource driver that high-point
> provides. I created my initrd and everything boots correctly. But going
> through the logs I noticed that there was a problem. Does anyone have any
> ideas how I can correct this problem. I also attached a more detailed
> version of the information below with the items before and after this
error.
>
<snip>

I get this message too when running a sofware RAID. I read somewhere that
it's caused by two parts of the kernel writing to the disk at once. I have
no problems with data loss because of it. I think it is safe to ignore it.

>
> Aug 7 00:33:56 server Trying to move old root to /initrd ... failed
> Aug 7 00:33:56 server Unmounting old root
> Aug 7 00:33:56 server Trying to free ramdisk memory ... invalidate: busy
> buffer
> Aug 7 00:33:56 server invalidate: dirty buffer
> Aug 7 00:33:56 server invalidate: dirty buffer
> Aug 7 00:33:56 server invalidate: dirty buffer
> Aug 7 00:33:56 server failed

I think that this 'failed' is talking about freeing ramdisk, the inval..'s
just got in the way.

Natman

[Jim Gifford]

I figured it out. It was an initrd problem. All you have to do is to add
/initrd to the root fs.

"Natman" <n...@where.com> wrote in message
news:Akl69.144826$f05.7...@news1.calgary.shaw.ca...

[Attombomb]

mkinitrd /boot/initrd-2.4.18.img 2.4.18

would it help to have the ram image.

"Jim Gifford" <giff...@linkline.com> wrote in message

news:ulnm8fk...@corp.supernews.com...