Package: installation-reports

 

INSTALL REPORT

 

Debian-installer-version: netinst from a mirror, about two weeks ago (sorry, did not keep exact date L )

uname -a: Linux moof 2.6.8-2-32 #1 Tue Feb 8 00:15:05 EST 2005 parisc GNU/Linux

Date: 30/5/2005

Method: booting from CD, interacting using a serial terminal.

 

Machine: HPPA Visualize B132L+

Processor: PA7300LC (PCX-L2)

Memory: 192mb

Root Device: SCSI IBM Hard Drive attached to the SE SCSI chain, 4.3 gb

Root Size/partition table: 

   Device Boot      Start         End      Blocks   Id  System

/dev/sda1               1          61      489951   82  Linux swap / Solaris

/dev/sda2              62          65       32130   f0  Linux/PA-RISC boot

/dev/sda3              66          81      128520   83  Linux

/dev/sda4              82         527     3582495    5  Extended

/dev/sda5   *          82         505     3405748+  83  Linux

/dev/sda6             506         527      176683+  82  Linux swap / Solaris

 

Output of lspci and lspci -n:

0000:00:13.0 SCSI storage controller: LSI Logic / Symbios Logic 53c875 (rev 04)

0000:00:14.0 Ethernet controller: Digital Equipment Corporation DECchip 21142/43

 (rev 30)

 

0000:00:13.0 0100: 1000:000f (rev 04)

0000:00:14.0 0200: 1011:0019 (rev 30)

 

Base System Installation Checklist:

[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

 

Initial boot worked:    [E]

Configure network HW:   [O]

Config network:         [O]

Detect CD:              [O]

Load installer modules: [O]

Detect hard drives:     [O]

Partition hard drives:  [O]

Create file systems:    [O]

Mount partitions:       [O]

Install base system:    [O]

Install boot loader:    [O]

Reboot:                 [O]

 

Comments/Problems:

 

When trying to install, the following symptom would occur: after mounting the ramdisk, a few seconds afterwards an "attempt to write past end of device" error occurs. The image is unpacked incorrectly and the system enters a loop of failing to load a module.

This is worked around by changing the boot parameter to use a larger-sized ramdisk. The default ramdisk size is 16384k which is simply not enough. I used 65536 and it worked. I can check 32m if needed.

After making this change, the installation worked flawlessly.

I have no logs to attached from the failed installation, I'm afraid, as they've been overwritten by logs from the successful installation.

 

Gil Bahat,

System Administrator,

Imperva™ Ltd.

Reply via email to