Re: devel install woes (was FC6 T3 install woes)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sun, 2006-09-17 at 21:46 -0500, Jay Cliburn wrote:
> listman wrote:
> [snip]
> > <6>ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> > <6>ata1.00: ATA-7, max UDMA/133, 488397168 sectors: LBA48 NCQ (depth 0/32)
> > <6>ata1.00: ata1: dev 0 multi count 16
> > <6>ata1.00: configured for UDMA/133
> > <6>scsi1 : sata_nv
> > <7>PM: Adding info for No Bus:host1
> > <6>ata2: SATA link down (SStatus 0 SControl 300)
> > <7>PM: Adding info for No Bus:target0:0:0
> > <5>  Vendor: ATA       Model: ST3250620AS       Rev: 3.AA
> > <5>  Type:   Direct-Access                      ANSI SCSI revision: 05
> > <7>PM: Adding info for scsi:0:0:0:0
> > <5>SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB)
> > <5>sda: Write Protect is off
> > <7>sda: Mode Sense: 00 3a 00 00
> > <5>SCSI device sda: drive cache: write back
> > <5>SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB)
> > <5>sda: Write Protect is off
> > <7>sda: Mode Sense: 00 3a 00 00
> > <5>SCSI device sda: drive cache: write back
> > <6> sda: sda1 sda2 < sda5 sda6 sda7 sda8 >
> > <5>sd 0:0:0:0: Attached scsi disk sda
> [snip]
> > <6>md: raid0 personality registered for level 0
> > <6>md: raid1 personality registered for level 1
> > <6>raid5: automatically using best checksumming function: generic_sse
> > <4>   generic_sse:  7070.000 MB/sec
> > <4>raid5: using function: generic_sse (7070.000 MB/sec)
> > <4>raid6: int64x1   1592 MB/s
> > <4>raid6: int64x2   2180 MB/s
> > <4>raid6: int64x4   1751 MB/s
> > <4>raid6: int64x8   1979 MB/s
> > <4>raid6: sse2x1    2566 MB/s
> > <4>raid6: sse2x2    3583 MB/s
> > <4>raid6: sse2x4    3932 MB/s
> > <4>raid6: using algorithm sse2x4 (3932 MB/s)
> > <6>md: raid6 personality registered for level 6
> > <6>md: raid5 personality registered for level 5
> > <6>md: raid4 personality registered for level 4
> > <4>GFS2 (built Sep  6 2006 16:09:57) installed
> > <6>Lock_Nolock (built Sep  6 2006 16:10:14) installed
> > <6>JFS: nTxBlock = 8192, nTxLock = 65536
> > <6>SGI XFS with ACLs, security attributes, large block/inode numbers, no debug enabled
> > <6>SGI XFS Quota Management subsystem
> > <6>device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: dm-devel@xxxxxxxxxx
> > <6>device-mapper: multipath: version 1.0.4 loaded
> > <6>device-mapper: multipath round-robin: version 1.0.0 loaded
> > <6>device-mapper: multipath emc: version 0.0.3 loaded
> > <5>audit(1158518905.881:3): audit_pid=788 old=0 by auid=4294967295 subj=system_u:system_r:anaconda_t:s0
> > <5>ReiserFS: sda7: found reiserfs format "3.6" with standard journal
> > <5>ReiserFS: sda7: using ordered data mode
> > <5>ReiserFS: sda7: journal params: device sda7, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
> > <5>ReiserFS: sda7: checking transaction log (sda7)
> > <5>ReiserFS: sda7: Using r5 hash to sort names
> > <6>SELinux: initialized (dev sda7, type reiserfs), uses genfs_contexts
> 
> I'm curious: What was installed on this drive before you began the FC6T3 
> installation?

I was curious on that as well.  I had heard there was a reiserfs bug
when doing an install, er well upgrade in this case.

Maybe if he tried a clean install (or one on a sep partition) just to
see if it works on a clean system?

Might tell you more possibly?

-- 
Mike Chambers
Madisonville, KY

"Sex is like air, it's not important unless your not getting any!"

-- 
fedora-test-list mailing list
fedora-test-list@xxxxxxxxxx
To unsubscribe: 
https://www.redhat.com/mailman/listinfo/fedora-test-list

[Index of Archives]     [Fedora Desktop]     [Fedora SELinux]     [Photo Sharing]     [Yosemite Forum]     [KDE Users]