I actually have this running at @expert but only had
one response... pretty dead over there...
let me clarify things a bit...
I had two boxes previously running 7.2 with ext2
box-x (broken box in question) and box-lt (laptop)
after upgrading to 8.1, I decided to also upgrade to
ext3. After
That maybe the case...but I upgraded two systems from
7.2 to 8.1 but only had problems with one of them... I
was able to resolve it with the old kernel by mkinitrd
and placing read-only in the global section at the
beginning of lilo.conf. That does not seem to work
with the new kernel.
---
let me amend this abit. I was speaking of the initial
8.1 kernel, not 2.4.8-34.1mdk. I only updated the
problem machine to 2.4.8-34.1mdk as I am waiting for
win4lin to release the latest kernel before I do the
other one.
--- SI Reasoning [EMAIL PROTECTED] wrote:
That maybe the case...but I
On Thu Nov 29, 2001 at 09:13:04AM -0800, SI Reasoning wrote:
(Let's move this over to expert@ where it belongs)
That maybe the case...but I upgraded two systems from
7.2 to 8.1 but only had problems with one of them... I
was able to resolve it with the old kernel by mkinitrd
and placing
I had the usb hangup happen at least once on shutdown
of the Tyan Trinity AT100 (the system with the fsck
problem).
--- Randy Welch [EMAIL PROTECTED] wrote:
George Mitchell wrote:
I know that this is not an answer to your problem,
but I am running 8.1
(with 2.4.8-34.1) with all but
Juan Quintela [EMAIL PROTECTED] writes:
Let me guess:
- 7.2 uses as kernel 2.2.
- there is a way to generate a kernel in 2.2 2.4 making the fs
incompatible with 2.2 (I think that it is the sparse super
capability).
FWIW I'm using a 2.2 kernel with a partition created
guillaume == Guillaume Cottenceau [EMAIL PROTECTED] writes:
guillaume Juan Quintela [EMAIL PROTECTED] writes:
Let me guess:
- 7.2 uses as kernel 2.2.
- there is a way to generate a kernel in 2.2 2.4 making the fs
incompatible with 2.2 (I think that it is the sparse super
capability).
George Mitchell wrote:
I know that this is not an answer to your problem, but I am running 8.1
(with 2.4.8-34.1) with all but my home partition formatted ext3. I am
constantly crashing this system due to some usb problem jamming up the
shutdown. Thus I am continually recovering those
potential uniqueness:
- 2 disk system with /boot on hda2 and / on hdb2
- upgraded mdk7.2 to 8.1
- migrated from ext2 to ext3 (previous kernel)
- k6-2 400 cpu (in case it is an amd chipset issue)
--- George Mitchell [EMAIL PROTECTED] wrote:
I know that this is not an answer to your problem,
but
SI Reasoning wrote:
potential uniqueness:
- 2 disk system with /boot on hda2 and / on hdb2
- upgraded mdk7.2 to 8.1
- migrated from ext2 to ext3 (previous kernel)
- k6-2 400 cpu (in case it is an amd chipset issue)
I am using k6-2 450 so you can eliminate that factor, but I find the
fact that
george == George Mitchell [EMAIL PROTECTED] writes:
george SI Reasoning wrote:
potential uniqueness:
- 2 disk system with /boot on hda2 and / on hdb2
- upgraded mdk7.2 to 8.1
- migrated from ext2 to ext3 (previous kernel)
- k6-2 400 cpu (in case it is an amd chipset issue)
george I am
[root@mom root]# tune2fs -l /dev/hdb2
tune2fs 1.24a (02-Sep-2001)'mom,10.0.0.77' (RSA1) to
the list of known hosts.
Filesystem volume name: none
Last mounted on: not available
Filesystem UUID:
ca78be02-e630-11d4-938c-ff1614a77075
Filesystem magic number: 0xEF53
Filesystem
I know that this is not an answer to your problem, but I am running 8.1
(with 2.4.8-34.1) with all but my home partition formatted ext3. I am
constantly crashing this system due to some usb problem jamming up the
shutdown. Thus I am continually recovering those partitions from the
journals
13 matches
Mail list logo
