mkfs -c /dev/hda3 results in Kernel panic during install to HD

mkfs -c /dev/hda3 results in Kernel panic during install to HD

Post by Hal R. Brand, LLnL, 510-422-63 » Thu, 20 Aug 1992 06:43:00




Organization: Lawrence Livermore National Laboratory
News-Software: VAX/VMS VNEWS 1.40    

Booting the Linux 0.97 bootimage gives:
        Serial port at 0x03f8 (irq 4) is a 16450
        Serial port at 0x02f8 (irq 3) is a 16450
        8 virtual consoles
        4 ptys
        lp_init: lp1 exists (0)
        lp_init: lp1 exists (0)
        Bus mouse detected and installed.
        Linux version 0.97-11 Aug 1 1992 13:33:18
        Floppy drive(s): fd0 is 1.2M, fd1 is 1.44M
        floppy: FDC version 0x90
        sock_init: initializing family 1 (AF_UNIX)
        scsi : 0 hosts
        scsi : detected 0 scsi disks 0 tapes total.
        hd0:
         part 1 start 32 size 450528 end 450559
         part 2 start 450560 size 204800 end 655359
         part 3 start 655360 size 122880 end 778239
         part 4 start 778240 size 122880 end 901119
Note: This a agrees with the what the NORTON utilities say. An YES, I know
 these 4 partitions don't fill the disk: 1 & 2 are for DOS, 3 and 4 are
 for Linux, but the (current) 64 Mbyte limit prevents using bigger partitions
 until later (soon?).
        Partition table ok
After feeding the floppy the 0.97.1 root disk:
        325 buffers = 332800 bytes buffer space
        Free mem: 15568896 bytes
        Welcome to the Linux V0.97.1 root disk
Now, logging in as root:
        # mkfs -c /dev/hda3 61440
        20480 inodes
        61440 blocks
        Firstdtazone = 653 (653)
        Zonesize = 1024
        Maxsize = 268966912
        HD: read_intr: status = 0x51
        HD: read_intr: error = 0x10
        HD: read_intr: status = 0x51
        HD: read_intr: error = 0x10
        HD: read_intr: status = 0x51
        HD: read_intr: error = 0x10
        HD-controller reset
        Kernel panic: Trying to write bad sector
        In swapper task - not syncing
At this point, there is not "#" prompt, but the keyboard is still active
in the sense that keystrokes are echoed and the "delete" key does the
right thing.

Anybody got any ideas, suggestions?

                                        Hal R. Brand
                                        LLNL

 
 
 

mkfs -c /dev/hda3 results in Kernel panic during install to HD

Post by Hal R. Brand, LLnL, 510-422-63 » Thu, 20 Aug 1992 06:43:00


Booting the Linux 0.97 bootimage gives:
        Serial port at 0x03f8 (irq 4) is a 16450
        Serial port at 0x02f8 (irq 3) is a 16450
        8 virtual consoles
        4 ptys
        lp_init: lp1 exists (0)
        lp_init: lp1 exists (0)
        Bus mouse detected and installed.
        Linux version 0.97-11 Aug 1 1992 13:33:18
        Floppy drive(s): fd0 is 1.2M, fd1 is 1.44M
        floppy: FDC version 0x90
        sock_init: initializing family 1 (AF_UNIX)
        scsi : 0 hosts
        scsi : detected 0 scsi disks 0 tapes total.
        hd0:
         part 1 start 32 size 450528 end 450559
         part 2 start 450560 size 204800 end 655359
         part 3 start 655360 size 122880 end 778239
         part 4 start 778240 size 122880 end 901119
Note: This a agrees with the what the NORTON utilities say. An YES, I know
 these 4 partitions don't fill the disk: 1 & 2 are for DOS, 3 and 4 are
 for Linux, but the (current) 64 Mbyte limit prevents using bigger partitions
 until later (soon?).
        Partition table ok
After feeding the floppy the 0.97.1 root disk:
        325 buffers = 332800 bytes buffer space
        Free mem: 15568896 bytes
        Welcome to the Linux V0.97.1 root disk
Now, logging in as root:
        # mkfs -c /dev/hda3 61440
        20480 inodes
        61440 blocks
        Firstdtazone = 653 (653)
        Zonesize = 1024
        Maxsize = 268966912
        HD: read_intr: status = 0x51
        HD: read_intr: error = 0x10
        HD: read_intr: status = 0x51
        HD: read_intr: error = 0x10
        HD: read_intr: status = 0x51
        HD: read_intr: error = 0x10
        HD-controller reset
        Kernel panic: Trying to write bad sector
        In swapper task - not syncing
At this point, there is not "#" prompt, but the keyboard is still active
in the sense that keystrokes are echoed and the "delete" key does the
right thing.

Anybody got any ideas, suggestions?

                                        Hal R. Brand
                                        LLNL


 
 
 

1. More info: mkfs -c /dev/hda3 results in Kernel panic during install to HD



Organization: Lawrence Livermore National Laboratory
News-Software: VAX/VMS VNEWS 1.40    

Somehow the following information got dropped from my original post so here
it is:

Machine is:
        ALR Power VEISA 486/33
        16 Mbyte RAM
        64 KByte cache
        Micropolis 1560A 660 Mbyte disk
        UltraStor EISA/ESDI 32 bit controller
        Pheonix BIOS V1.00.11A
        MS Bus mouse
        2 Serial, 2 Parallel ports
        1.2M and 1.44M floppies

Is there (possibly) something Linux doesn't like about the UltraStor
disk controller?

                                        Hal R. Brand
                                        LLNL

2. ^M problem in talk program...

3. Kernel panic: aha152x panic (during LILO install)

4. Looking for ISO 7498-2

5. accessing /dev/hda3 files from /dev/hda2 -- help!

6. using ipnat and dmz

7. /dev/hda1 = /dev/hda3?

8. Winmodems, the final word (I wish).

9. Mandrake install results in kernel panic

10. Linux on /dev/hda1 && Win95 on /dev/hda3

11. "Kernel panic: aic7xxx_isr..." during Install

12. panic after kernel config during install

13. Kernel panic during new install