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

Bug#367402: marked as done (Tyan S2865)



Your message dated Wed, 08 Sep 2010 03:58:13 +0000
with message-id <E1OtBnZ-0005AT-AM@ravel.debian.org>
and subject line Closing old installation report #367402
has caused the Debian Bug report #367402,
regarding Tyan S2865
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
367402: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=367402
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports

Boot method: <CD>
Image version: <debian-testing-amd64-netinst.iso>
Date: <Sun May 14 18:05:17 CDT 2006>

Machine: <Tyan S2865G2NR)>
Processor: AMD Opteron(tm) Processor 144
Memory: MemTotal:      1024068 kB
Partitions: <Filesystem    Type   1K-blocks      Used Available Use% Mounted on
/dev/md1       jfs    70570440    817892  69752548   2% /
tmpfs        tmpfs      512032         0    512032   0% /dev/shm
tmpfs        tmpfs       10240       684      9556   7% /dev

Disk /dev/sda: 82.3 GB, 82348277760 bytes
255 heads, 63 sectors/track, 10011 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1        8790    70605643+  fd  Linux raid autodetect
/dev/sda2            8791       10011     9807682+  fd  Linux raid autodetect

# cat /proc/mdstat
Personalities : [raid0] [raid1] [raid5]
md1 : active raid1 sda1[0] sdb1[1]
      70605568 blocks [2/2] [UU]

md0 : active raid1 sda2[0] sdb2[1]
      9807616 blocks [2/2] [UU]

unused devices: <none>

# cat /etc/fstab
# /etc/fstab: static file system information.
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    defaults        0       0
/dev/md1        /               jfs     defaults,errors=remount-ro 0       1
/dev/md0        none            swap    sw              0       0
/dev/hdb        /media/cdrom0   udf,iso9660 user,noauto     0       0



>

Output of lspci and lspci -n:

# lspci
0000:00:00.0 Memory controller: nVidia Corporation: Unknown device 005e (rev a3)
0000:00:01.0 ISA bridge: nVidia Corporation: Unknown device 0050 (rev a3)
0000:00:01.1 SMBus: nVidia Corporation: Unknown device 0052 (rev a2)
0000:00:02.0 USB Controller: nVidia Corporation: Unknown device 005a (rev a2)
0000:00:02.1 USB Controller: nVidia Corporation: Unknown device 005b (rev a3)
0000:00:06.0 IDE interface: nVidia Corporation: Unknown device 0053 (rev f2)
0000:00:07.0 IDE interface: nVidia Corporation: Unknown device 0054 (rev f3)
0000:00:08.0 IDE interface: nVidia Corporation: Unknown device 0055 (rev f3)
0000:00:09.0 PCI bridge: nVidia Corporation: Unknown device 005c (rev a2)
0000:00:0a.0 Bridge: nVidia Corporation: Unknown device 0057 (rev a3)
0000:00:0b.0 PCI bridge: nVidia Corporation: Unknown device 005d (rev a3)
0000:00:0c.0 PCI bridge: nVidia Corporation: Unknown device 005d (rev a3)
0000:00:0d.0 PCI bridge: nVidia Corporation: Unknown device 005d (rev a3)
0000:00:0e.0 PCI bridge: nVidia Corporation: Unknown device 005d (rev a3)
0000:00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge
0000:00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge
0000:00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge
0000:00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge
0000:01:05.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27)
0000:04:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5721 Gigabit Ethernet PCI Express (rev 11)

# lspci -n
0000:00:00.0 0580: 10de:005e (rev a3)
0000:00:01.0 0601: 10de:0050 (rev a3)
0000:00:01.1 0c05: 10de:0052 (rev a2)
0000:00:02.0 0c03: 10de:005a (rev a2)
0000:00:02.1 0c03: 10de:005b (rev a3)
0000:00:06.0 0101: 10de:0053 (rev f2)
0000:00:07.0 0101: 10de:0054 (rev f3)
0000:00:08.0 0101: 10de:0055 (rev f3)
0000:00:09.0 0604: 10de:005c (rev a2)
0000:00:0a.0 0680: 10de:0057 (rev a3)
0000:00:0b.0 0604: 10de:005d (rev a3)
0000:00:0c.0 0604: 10de:005d (rev a3)
0000:00:0d.0 0604: 10de:005d (rev a3)
0000:00:0e.0 0604: 10de:005d (rev a3)
0000:00:18.0 0600: 1022:1100
0000:00:18.1 0600: 1022:1101
0000:00:18.2 0600: 1022:1102
0000:00:18.3 0600: 1022:1103
0000:01:05.0 0300: 1002:4752 (rev 27)
0000:04:00.0 0200: 14e4:1659 (rev 11)



Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot worked:    [E]
Configure network HW:   [E]
Config network:         [E]
Detect CD:              [E]
Load installer modules: [E]
Detect hard drives:     [E]
Partition hard drives:  [E]
Create file systems:    [E]
Mount partitions:       [E]
Install base system:    [E]
Install boot loader:    [E]
Reboot:                 [E]

Comments/Problems:

<I did a sarge install on jfs on software RAID1. This had not worked on earlier versions of the installer. The version I used had file dates May-13-06 (this date should be part of the iso file name!!) There was a problem with the RAID - it came out with the partitions mis mated - Might have been my error??

After running and installing a few packages the file system became corrupted and was not rebootable.

Will run memtest and try to zero the supper blocks and start over.

 >

----------------------------------------------------------------
Karl Schmidt                         EMail Karl@xtronics.com
Transtronics, Inc.    		       WEB http://xtronics.com
3209 West 9th Street                    Ph (785) 841-3089
Lawrence, KS 66049                     FAX (785) 841-0434


 There's many a bestseller that could have been prevented by a good teacher.
--Flannery O'Connor
----------------------------------------------------------------


--- End Message ---
--- Begin Message ---
We are closing this installation report for one of the following
reasons:
- it was reported with a pre-lenny version of Debian
  Installer.
- indications in the installation report give the feeling that
  the reported problem waslying in another software, unrelated to
  D-I, which we can't easily identify.
- indications in the installation report suggest that it may have been
  fixed in a more recent version of a D-I component
- it was successful and we forgot closing it..:-)
- it has no information we consider useful


The D-I team is currently in the process of cleaning out the old spool
of installation reports that haven't bene processed yet. 

In case you think that the problem you reported has chances to be
still present, please reiterate your installation test with
a more recent image of D-I, if you're in position of doing this.

You'll find daily builds at
http://www.debian.org/devel/debian-installer. We recommend you choose
the netboot image, in the "daily builds section", then choose to
install "squeeze" when prompted.

If some problems are found, please report them with a new bug sent
against installation-reports.

Many thanks for your understanding and your help improving Debian,
past and present.



--- End Message ---

Reply to: