Announcement

Collapse

Forum Rules and Etiquette

Our mission ...

This forum is part of our mission to promote the preservation of vintage computers through education and outreach. (In real life we also run events and have a museum.) We encourage you to join us, participate, share your knowledge, and enjoy.

This forum has been around in this format for over 15 years. These rules and guidelines help us maintain a healthy and active community, and we moderate the forum to keep things on track. Please familiarize yourself with these rules and guidelines.


Rule 1: Remain civil and respectful

There are several hundred people who actively participate here. People come from all different backgrounds and will have different ways of seeing things. You will not agree with everything you read here. Back-and-forth discussions are fine but do not cross the line into rude or disrespectful behavior.

Conduct yourself as you would at any other place where people come together in person to discuss their hobby. If you wouldn't say something to somebody in person, then you probably should not be writing it here.

This should be obvious but, just in case: profanity, threats, slurs against any group (sexual, racial, gender, etc.) will not be tolerated.


Rule 2: Stay close to the original topic being discussed
  • If you are starting a new thread choose a reasonable sub-forum to start your thread. (If you choose incorrectly don't worry, we can fix that.)
  • If you are responding to a thread, stay on topic - the original poster was trying to achieve something. You can always start a new thread instead of potentially "hijacking" an existing thread.



Rule 3: Contribute something meaningful

To put things in engineering terms, we value a high signal to noise ratio. Coming here should not be a waste of time.
  • This is not a chat room. If you are taking less than 30 seconds to make a post then you are probably doing something wrong. A post should be on topic, clear, and contribute something meaningful to the discussion. If people read your posts and feel that their time as been wasted, they will stop reading your posts. Worse yet, they will stop visiting and we'll lose their experience and contributions.
  • Do not bump threads.
  • Do not "necro-post" unless you are following up to a specific person on a specific thread. And even then, that person may have moved on. Just start a new thread for your related topic.
  • Use the Private Message system for posts that are targeted at a specific person.


Rule 4: "PM Sent!" messages (or, how to use the Private Message system)

This forum has a private message feature that we want people to use for messages that are not of general interest to other members.

In short, if you are going to reply to a thread and that reply is targeted to a specific individual and not of interest to anybody else (either now or in the future) then send a private message instead.

Here are some obvious examples of when you should not reply to a thread and use the PM system instead:
  • "PM Sent!": Do not tell the rest of us that you sent a PM ... the forum software will tell the other person that they have a PM waiting.
  • "How much is shipping to ....": This is a very specific and directed question that is not of interest to anybody else.


Why do we have this policy? Sending a "PM Sent!" type message basically wastes everybody else's time by making them having to scroll past a post in a thread that looks to be updated, when the update is not meaningful. And the person you are sending the PM to will be notified by the forum software that they have a message waiting for them. Look up at the top near the right edge where it says 'Notifications' ... if you have a PM waiting, it will tell you there.

Rule 5: Copyright and other legal issues

We are here to discuss vintage computing, so discussing software, books, and other intellectual property that is on-topic is fine. We don't want people using these forums to discuss or enable copyright violations or other things that are against the law; whether you agree with the law or not is irrelevant. Do not use our resources for something that is legally or morally questionable.

Our discussions here generally fall under "fair use." Telling people how to pirate a software title is an example of something that is not allowable here.


Reporting problematic posts

If you see spam, a wildly off-topic post, or something abusive or illegal please report the thread by clicking on the "Report Post" icon. (It looks like an exclamation point in a triangle and it is available under every post.) This send a notification to all of the moderators, so somebody will see it and deal with it.

If you are unsure you may consider sending a private message to a moderator instead.


New user moderation

New users are directly moderated so that we can weed spammers out early. This means that for your first 10 posts you will have some delay before they are seen. We understand this can be disruptive to the flow of conversation and we try to keep up with our new user moderation duties to avoid undue inconvenience. Please do not make duplicate posts, extra posts to bump your post count, or ask the moderators to expedite this process; 10 moderated posts will go by quickly.

New users also have a smaller personal message inbox limit and are rate limited when sending PMs to other users.


Other suggestions
  • Use Google, books, or other definitive sources. There is a lot of information out there.
  • Don't make people guess at what you are trying to say; we are not mind readers. Be clear and concise.
  • Spelling and grammar are not rated, but they do make a post easier to read.
See more
See less

Cobalt Qube3, a bit lost

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Cobalt Qube3, a bit lost

    First off, a bit of background on the unit: http://www.kevinomura.com/microservers/cobalt/qube3/

    Granted its not vintage, (K6-2 cpu) but every other place I seem to look for information I either get stone silence or a rash of people saying; "lol throw that old p.o.s. away". My goal is it use this little box to isolate my older computers from the new ones. It would also be an Appleserve point for my macs and be a file server for them.

    I want to not use the 40gb hard drives that came with the unit. They are hot, noisy, and draw a lot of power. I have a friend who owes me a favor or two, so I have access to several 500gb sata laptop drives. These drives use <500ma @5v while the original drives are rated 750/1000 @ 5v/12. not to mention VASTLY larger in space. However, the onboard bios is limited to 137gb. Nor do ide>sata adapters work. (at least the ones I have) I thought I came across a solution of using CF cards to boot and have the laptop drives dedicated for storage. However when I try to install the special linux on the cards, the installation fails. i'm not fluent in Linux enough to know how to fix it. So I'm asking here, hopefully someone know these 2000 era linux kernels and can tell me how to proceed. I CAN just install some other ide drives, in fact I have 2 spare 250gb drives, but the power/noise savings is practically nil.

    Code:
    
    
    
    
             Sun Cobalt - Smaller, Bluer, Better, and Free
                   Firmware version 2.10.3-ext3
    
    
    Current date: Jan 07 23:55:08 UTC 2014
    ROM build info: Thu Mar 11 08:51:36 MST 2004 .
    System serial number: Uninitialized
    System type: 3000 series system, Version 2 board
    Silicon serial number: b8000008bcc84d01
    Monitor: 153536 bytes
    Memory: 512 MB
    CPU: 1 processor(s) detected
      CPU 0: AuthenticAMD 448MHz (4.5 x 100MHz host bus) [BSP]
    Initializing flash: done
      Flash Bank 0: AMD AM29F080B 1024KB (01:d5)
      Flash Bank 1: not installed.
    Mounting ROM fs: done
    Initializing PCI: done
      Host Bus: 0 (device 1b:07) [33MHz]
        Device: 00:00 10b9:1541 Acer Labs M1541 Aladdin V Host Bridge
        Device: 01:00 10b9:5243 Acer Labs M5243 AGP Controller
        Device: 02:00 10b9:5237 Acer Labs M5237 USB Controller (IRQ 6)
        Device: 03:00 10b9:7101 Acer Labs M7101 PMU
        Device: 07:00 10b9:1533 Acer Labs M1543 Aladdin V PCI-ISA Bridge
        Device: 0e:00 1000:000f Symbios Logic SYM53C875 SCSI Controller (IRQ 12)
        Device: 0f:00 10b9:5229 Acer Labs M5229 TXpro IDE Controller (IRQ 14)
        Device: 10:00 100b:0020 National DP83815 MacPhyter Ethernet (IRQ 11)
        Device: 12:00 100b:0020 National DP83815 MacPhyter Ethernet (IRQ 10)
      Bridged Bus: 1 (bridge: 00:01:00)
    Initializing ethernet: 2 controller(s) found
      National Semiconductor DP83815 Found at port 0xfc00, MAC: 00:10:e0:03:ce:a0
      National Semiconductor DP83815 Found at port 0xfb00, MAC: 00:10:e0:03:c5:6c
    Initializing IDE: found ALI M5229 at 00:78
      spinning up second channel: done
      scanning ide0: master slave
      scanning ide1:
    IDE: stabilizing spinup: 100%
    Checking Memory: done
    
    
    Press spacebar to enter ROM mode
    
    
    Cobalt:Main Menu> bfn
    Enabling L2 cache: on-chip L2 is 128K -done
    First stage kernel (Linux): Decompressing - done
    ERROR: cannot relocate with filesize 0
    command line: 'console=ttyS0,115200 debug ip=on root=/dev/nfs nfsroot=/nfsroot-x86,rsize=8192 '
    booting kernel...
    Linux version 2.4.25-ROM (duncan@atherton) (gcc version 3.3.3 (Debian 20040306)) #1 Thu Mar 11 08:47:53 MST 2004
    BIOS-provided physical RAM map:
     BIOS-e801: 0000000000000000 - 000000000009f000 (usable)
     BIOS-e801: 0000000000100000 - 0000000020000000 (usable)
    512MB LOWMEM available.
    On node 0 totalpages: 131072
    zone(0): 4096 pages.
    zone(1): 126976 pages.
    zone(2): 0 pages.
    DMI not present.
    Kernel command line: console=ttyS0,115200 debug ip=on root=/dev/nfs nfsroot=/nfsroot-x86,rsize=8192
    Initializing CPU#0
    Detected 448.219 MHz processor.
    Calibrating delay loop... 894.56 BogoMIPS
    Memory: 516556k/524288k available (1141k kernel code, 7344k reserved, 244k data, 100k init, 0k highmem)
    Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
    Inode cache hash table entries: 32768 (order: 6, 262144 bytes)
    Mount cache hash table entries: 512 (order: 0, 4096 bytes)
    Buffer cache hash table entries: 32768 (order: 5, 131072 bytes)
    Page-cache hash table entries: 131072 (order: 7, 524288 bytes)
    Enabling new style K6 write allocation for 512 Mb
    CPU: L1 I Cache: 32K (32 bytes/line), D cache 32K (32 bytes/line)
    CPU: L2 Cache: 128K (32 bytes/line)
    CPU:     After generic, caps: 008021bf c08029bf 00000000 00000002
    CPU:             Common caps: 008021bf c08029bf 00000000 00000002
    CPU: AMD-K6(tm)-III Processor stepping 04
    Checking 'hlt' instruction... OK.
    POSIX conformance testing by UNIFIX
    mtrr: v1.40 (20010327) Richard Gooch (rgooch@atnf.csiro.au)
    mtrr: detected mtrr type: AMD K6
    PCI: Using configuration type 1
    PCI: Probing PCI hardware
    PCI: Probing PCI hardware (bus 00)
    Linux NET4.0 for Linux 2.4
    Based upon Swansea University Computer Society NET3.039
    Initializing RT netlink socket
    Starting kswapd
    VFS: Disk quotas vdquot_6.5.1
    Journalled Block Device driver loaded
    pty: 256 Unix98 ptys configured
    Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI enabled
    ttyS00 at 0x03f8 (irq = 4) is a 16550A
    ttyS01 at 0x02f8 (irq = 3) is a 16550A
    Real Time Clock Driver v1.10f
    Non-volatile memory driver v1.2
    loop: loaded (max 8 devices)
    natsemi dp8381x driver, version 1.07+LK1.0.17, Sep 27, 2002
      originally by Donald Becker <becker@scyld.com>
      http://www.scyld.com/network/natsemi.html
      2.4.x kernel port by Jeff Garzik, Tjeerd Mulder
    eth0: NatSemi DP8381[56] at 0xe0800000, 00:10:e0:03:ce:a0, IRQ 11.
    eth1: NatSemi DP8381[56] at 0xe0802000, 00:10:e0:03:c5:6c, IRQ 10.
    Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4
    ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
    ALI15X3: IDE controller at PCI slot 00:0f.0
    ALI15X3: chipset revision 193
    ALI15X3: 100% native mode on irq 14
        ide0: BM-DMA at 0xfdd0-0xfdd7, BIOS settings: hda:DMA, hdb:DMA
        ide1: BM-DMA at 0xfdd8-0xfddf, BIOS settings: hdc:DMA, hdd:DMA
    hda: Flash Module, ATA DISK drive
    hdb: Flash Module, ATA DISK drive
    ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
    blk: queue c0298fa0, I/O limit 4095Mb (mask 0xffffffff)
    blk: queue c02990dc, I/O limit 4095Mb (mask 0xffffffff)
    ide0 at 0xfdf8-0xfdff,0xfdf6 on irq 14
    hda: attached ide-disk driver.
    hda: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
    hda: task_no_data_intr: error=0x04 { DriveStatusError }
    hda: 3940272 sectors (2017 MB) w/1KiB Cache, CHS=3909/16/63, UDMA(33)
    hdb: attached ide-disk driver.
    hdb: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
    hdb: task_no_data_intr: error=0x04 { DriveStatusError }
    hdb: 3940272 sectors (2017 MB) w/1KiB Cache, CHS=3909/16/63, UDMA(33)
    Partition check:
     hda:hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
    hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
     [PTBL] [977/64/63] hda1
     hdb:hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
    hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
    hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
    hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
    hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
    hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
    hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
    hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
    blk: queue c0298fa0, I/O limit 4095Mb (mask 0xffffffff)
    blk: queue c02990dc, I/O limit 4095Mb (mask 0xffffffff)
    ide0: reset: success
    hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
    hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
    hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
    hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
    hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
    hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
    hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
    hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
    hda: DMA disabled
    ide0: reset: success
    hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
    hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
    end_request: I/O error, dev 03:40 (hdb), sector 0
    hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
    hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
    hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
    hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
    hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
    hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
    hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
    hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
    ide0: reset: success
     unable to read partition table
    md: linear personality registered as nr 1
    md: raid0 personality registered as nr 2
    md: raid1 personality registered as nr 3
    md: raid5 personality registered as nr 4
    raid5: measuring checksumming speed
       8regs     :   621.200 MB/sec
       32regs    :   367.200 MB/sec
       pII_mmx   :   849.600 MB/sec
       p5_mmx    :   825.200 MB/sec
    raid5: using function: pII_mmx (849.600 MB/sec)
    md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
    md: Autodetecting RAID arrays.
    md: autorun ...
    md: ... autorun DONE.
    NET4: Linux TCP/IP 1.0 for NET4.0
    IP Protocols: ICMP, UDP, TCP
    IP: routing cache hash table of 4096 buckets, 32Kbytes
    TCP: Hash tables configured (established 131072 bind 65536)
    eth0: link up.
    eth0: Setting full-duplex based on negotiated link capability.
    eth1: autonegotiation did not complete in 4000 usec.
    Sending DHCP and RARP requests .,. OK
    IP-Config: Got DHCP answer from 10.0.0.254, my address is 10.0.0.150
    eth1: remaining active for wake-on-lan
    IP-Config: Complete:
          device=eth0, addr=10.0.0.150, mask=255.0.0.0, gw=255.255.255.255,
         host=10.0.0.150, domain=mfg.cobaltmicro.com, nis-domain=(none),
         bootserver=10.0.0.254, rootserver=10.0.0.254, rootpath=
    NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
    Looking up port of RPC 100003/2 on 10.0.0.254
    Looking up port of RPC 100005/1 on 10.0.0.254
    VFS: Mounted root (nfs filesystem).
    Freeing unused kernel memory: 100k freed
    INIT: version 2.82 booting
    Mounting /proc: done
    Bringing up lo: ifconfig  lo  127.0.0.1 netmask 255.0.0.0 broadcast 127.255.255.255
    done
    Starting portmap: done
    Configured network: eth0
    My MAC is: 00:10:E0:03:CE:A0
    Mounting tester:/test_dir/tmp/03CEA0 as /tmp
    Hardware generation is: III
    getting build...
    Build: 4100WG_1.12
    Updates:
      01_Qube3-en-Mfg-0.0.2-9690.pkg
      02_Qube3-en-Update-1.0.3BTO.pkg
      03_Qube3-en-Update-2.0.8-cache-raid.pkg
      04_Qube3-All-System-1.0.1-9819.pkg
      05_Qube3-All-Security-2.0.1-8061.pkg
      06_Qube3-ml-Update-4.0.pkg
      07_Qube3-en-Manual-1.2.pkg
      08_Qube3-fr-Manual-1.2.pkg
      09_Qube3-es-Manual-1.2.pkg
      10_Qube3-de-Manual-1.2.pkg
      11_Qube3-ja-Manual-1.2.pkg
      12_Qube3-zh_CN-Manual-1.2.pkg
      13_Qube3-zh_TW-Manual-1.2.pkg
    CTO Packages:
    You currently have ROM: 2.10.3 installed
    ROM version ok
    Building product 4100WG_1.12
     with updates: 01_Qube3-en-Mfg-0.0.2-9690.pkg,02_Qube3-en-Update-1.0.3BTO.pkg,03_Qube3-en-Update-2.0.8-cache-raid.pkg,04_Qube3-All-System-1.0.1-9819.pkg,05_Qube3-All-Security-2.0.1-8061.pkg,06_Qube3-ml-Update-4.0.pkg,07_Qube3-en-Manual-1.2.pkg,08_Qube3-fr-Manual-1.2.pkg,09_Qube3-es-Manual-1.2.pkg,10_Qube3-de-Manual-1.2.pkg,11_Qube3-ja-Manual-1.2.pkg,12_Qube3-zh_CN-Manual-1.2.pkg,13_Qube3-zh_TW-Manual-1.2.pkg
          and CTO:
    Prod field is 4100WG
    Building Cobalt Linux Release 6.0 (Carmel) build 1.12 for a 4100WG in en_US
    Verifying release_spec
    Found 0 script(s) to execute prior to drive partitioning.
    Found 0 script(s) to execute prior to installation.
    Found 461 rpm(s) for the 4100WG.
    Found 14 script(s) to execute after installation.
    Found 0 packages(s) to install at end of build.
    Building system with RAID support
    WARNING: disk-to-disk builds will not work
    Destination device: /dev/md
    Destination / partition: 1
    Destination swap partition: 6
    Destination /var partition: 3
    Destination /home partition: 4
    Partitioning disk
    /dev/md1: No such device
    /dev/md6: No such device
    /dev/md3: No such device
    /dev/md4: No such device
    /dev/md5: No such device
    Checking that no hda:-one is using this disk right no hda1w ...
    
    
    OK
    
    
    Disk /dev/hda: 977 cylinders, 64 heads, 63 sectors/track
    Old situation:
    Units = megabytes of 1048576 bytes, blocks of 1024 bytes, counting from 0
    
    
       Device Boot Start   End     MB   #blocks   Id  System
    /dev/hda1         0+  1921-  1922-  1967584+   6  FAT16
    /dev/hda2         0      -      0         0    0  Empty
    /dev/hda3         0      -      0         0    0  Empty
    /dev/hda4         0      -      0         0    0  Empty
    Warning: given size (501) exceeds max allowable size (263)
    New situation:
    Units = megabytes of 1048576 bytes, blocks of 1024 bytes, counting from 0
    
    
       Device Boot Start   End     MB   #blocks   Id  System
    /dev/hda1         0+  1500-  1501-  1536191+  fd  Linux raid autodetect
    /dev/hda2      1500+  1659-   160-   163296    5  Extended
    /dev/hda3      1659+  2159-   501-   512064   fd  Linux raid autodetect
    /dev/hda4         0      -      0         0   fd  Linux raid autodetect
    /dev/hda5      1500+  1531-    32-    32255+  fd  Linux raid autodetect
    /dev/hda6      1531+  1659-   128-   131039+  fd  Linux raid autodetect
    Warning: partition 4 has size 0 but is not marked Empty
    Warning: partition 3 extends past end of disk
    Successfully wrote the new partition table
    
    
    Re-reading the partition table ...
     hda: hda1 hda2 < hda5 hda6 > hda3
    
    
    If you created or changed a DOS partition, /dev/foo7, say, then use dd(1)
    to zero the first 512 bytes:  dd if=/dev/zero of=/dev/foo7 bs=512 count=1
    (See fdisk(8).)
    Checking that no hdb:-one is using th hdb1is disk right no hdb2w ...
     hdb3 hdb4
    OK
    
    
    Disk /dev/hdb: 3909 cylinders, 16 heads, 63 sectors/track
    Old situation:
    Warning: The first partition looks like it was made
      for C/H/S=*/33/45 (instead of 3909/16/63).
    For this listing I'll assume that geometry.
    Units = megabytes of 1048576 bytes, blocks of 1024 bytes, counting from 0
    
    
       Device Boot Start   End     MB   #blocks   Id  System
    /dev/hdb1   ? 379949+ 937326- 557378- 570754815+  72  Unknown
                    start: (c,h,s) expected (1023,32,45) found (357,116,40)
                    end: (c,h,s) expected (1023,32,45) found (357,32,45)
    /dev/hdb2   ? 82367+ 1027694- 945327- 968014120   65  Novell Netware 386
                    start: (c,h,s) expected (1023,32,45) found (288,115,43)
                    end: (c,h,s) expected (1023,32,45) found (367,114,50)
    /dev/hdb3   ? 913028+ 1858354- 945327- 968014096   79  Unknown
                    start: (c,h,s) expected (1023,32,45) found (366,32,33)
                    end: (c,h,s) expected (1023,32,45) found (357,32,43)
    /dev/hdb4   ?     0  1775989- 1775990- 1818613248    d  Unknown
                    start: (c,h,s) expected (0,0,1) found (372,97,50)
                    end: (c,h,s) expected (1023,32,45) found (0,10,0)
    Warning: given size (501) exceeds max allowable size (265)
    New situation:
    Units = megabytes of 1048576 bytes, blocks of 1024 bytes, counting from 0
    
    
       Device Boot Start   End     MB   #blocks   Id  System
    /dev/hdb1         0+  1500-  1501-  1536191+  fd  Linux raid autodetect
    /dev/hdb2      1500+  1658-   159-   162288    5  Extended
    /dev/hdb3      1658+  2158-   501-   512064   fd  Linux raid autodetect
    /dev/hdb4         0      -      0         0   fd  Linux raid autodetect
    /dev/hdb5      1500+  1530-    31-    30743+  fd  Linux raid autodetect
    /dev/hdb6      1530+  1658-   129-   131543+  fd  Linux raid autodetect
    Warning: partition 4 has size 0 but is not marked Empty
    Warning: partition 3 extends past end of disk
    Successfully wrote the new partition table
    
    
    Re-reading the partition table ...
     hdb: hdb1 hdb2 < hdb5 hdb6 > hdb3
    
    
    If you created or changed a DOS partition, /dev/foo7, say, then use dd(1)
    to zero the first 512 bytes:  dd if=/dev/zero of=/dev/foo7 bs=512 count=1
    (See fdisk(8).)
    Formatting /dev/md1
    handling MD device /dev/md1
    analyzing super-block
    disk 0: /dev/hda1, 1536191kB, raid superblock at 1536064kB
    couldn't open device /dev/hdc1 -- Device not configured
    mkraid: aborted, see the syslog and /proc/mdstat for potential clues.
    Personalities : [linear] [raid0] [raid1] [raid5]
    read_ahead not set
    unused devices: <none>
    mke2fs 1.14, 9-Jan-1999 for EXT2 FS 0.5b, 95/08/09
    /dev/md1: Invalid argument passed to ext2 library while setting up superblock
    Personalities : [linear] [raid0] [raid1] [raid5]
    read_ahead not set
    unused devices: <none>
    Formatting /dev/md3
    handling MD device /dev/md3
    analyzing super-block
    disk 0: /dev/hda3, 512064kB, raid superblock at 512000kB
    couldn't open device /dev/hdc3 -- Device not configured
    mkraid: aborted, see the syslog and /proc/mdstat for potential clues.
    Personalities : [linear] [raid0] [raid1] [raid5]
    read_ahead not set
    unused devices: <none>
    mke2fs 1.14, 9-Jan-1999 for EXT2 FS 0.5b, 95/08/09
    /dev/md3: Invalid argument passed to ext2 library while setting up superblock
    Personalities : [linear] [raid0] [raid1] [raid5]
    read_ahead not set
    unused devices: <none>
    Formatting /dev/md4
    handling MD device /dev/md4
    analyzing super-block
    /dev/hda4: device too small (0kB)
    mkraid: aborted, see the syslog and /proc/mdstat for potential clues.
    Personalities : [linear] [raid0] [raid1] [raid5]
    read_ahead not set
    unused devices: <none>
    mke2fs 1.14, 9-Jan-1999 for EXT2 FS 0.5b, 95/08/09
    /dev/md4: Invalid argument passed to ext2 library while setting up superblock
    Personalities : [linear] [raid0] [raid1] [raid5]
    read_ahead not set
    unused devices: <none>
    Creating swap
    /dev/md6: No such device
    handling MD device /dev/md6
    analyzing super-block
    disk 0: /dev/hda6, 131039kB, raid superblock at 130944kB
    couldn't open device /dev/hdc6 -- Device not configured
    mkraid: aborted, see the syslog and /proc/mdstat for potential clues.
    mkswap: error: swap area needs to be at least 40kB
    Usage: mkswap [-c] [-v0|-v1] [-pPAGESZ] /dev/name [blocks]
    swapon: /dev/md6: No such device
    Mounting /dev/md1 on /mntdir/
    /dev/md1: Invalid argument
    EXT3-fs: unable to read superblock
    mount: you must specify the filesystem type
    ./cobalt_install: mount /dev/md1 /mntdir/ failed. Terminating.
    build_release: /bin/sh - ./cobalt_install failed. Terminating.
    /dev/md1: InvaliEXT3-fs: unable to read superblock
    d argument
    mount: you must specify the filesystem type
    Loading MFG hook
    sh: /mntdir/etc/rc.d/rc3.d/S98zzzDELETE_MEzzz: No such file or directory
    /bin/chmod: /mntdir/etc/rc.d/rc3.d/S98zzzDELETE_MEzzz: No such file or directory
    Creating .master files if needed
    eth0      Link encap:Ethernet  HWaddr 00:10:E0:03:CE:A0
              inet addr:10.0.0.150  Bcast:10.255.255.255  Mask:255.0.0.0
    Found Broadcast(10.255.255.255) and Netmask(255.0.0.0)!
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:6113 errors:0 dropped:0 overruns:0 frame:0
              TX packets:3929 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000
              Interrupt:11
    
    
    Kernel IP routing table
    Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
    10.0.0.0        0.0.0.0         255.0.0.0       U     0      0        0 eth0
    Found Network(10.0.0.0)!
    127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo
    cp: cannot create regular file `/mntdir/etc/resolv.conf': No such file or directory
    
    
    Contents of /mntdir/etc/resolv.conf:
    cat: /mntdir/etc/resolv.conf: No such file or directory
    
    
    Contents of /mntdir/etc/sysconfig/network:
    cat: /mntdir/etc/sysconfig/network: No such file or directory
    sh: /mntdir/etc/HOSTNAME: No such file or directory
    
    
    Contents of /mntdir/etc/HOSTNAME:
    cat: /mntdir/etc/HOSTNAME: No such file or directory
    sh: /mntdir/etc/NET-CONFIG: No such file or directory
    
    
    Contents of /mntdir/etc/NET-CONFIG:
    cat: /mntdir/etc/NET-CONFIG: No such file or directory
    
    
    Contents of /mntdir/etc/sysconfig/network-scripts/ifcfg-eth0:
    cat: /mntdir/etc/sysconfig/network-scripts/ifcfg-eth0: No such file or directory
    Writing Updates to the disk:
      01_Qube3-en-Mfg-0.0.2-9690.pkg
      02_Qube3-en-Update-1.0.3BTO.pkg
      03_Qube3-en-Update-2.0.8-cache-raid.pkg
      04_Qube3-All-System-1.0.1-9819.pkg
      05_Qube3-All-Security-2.0.1-8061.pkg
      06_Qube3-ml-Update-4.0.pkg
      07_Qube3-en-Manual-1.2.pkg
      08_Qube3-fr-Manual-1.2.pkg
      09_Qube3-es-Manual-1.2.pkg
      10_Qube3-de-Manual-1.2.pkg
      11_Qube3-ja-Manual-1.2.pkg
      12_Qube3-zh_CN-Manual-1.2.pkg
      13_Qube3-zh_TW-Manual-1.2.pkg
    Writing Bundles to the disk:
    /bin/cp: cannot create regular file `/mntdir/etc': Read-only file system
    umount: /mntdir: not mounted
    INIT: Switching to runlevel: 6
    INIT: Sending processes the TERMSending all processes the TERM signal...
    INIT: no more processes left in this runlevel
    Sending all procmd: recovery thread got woken up ...
    esses the KILL smd: recovery thread finished ...
    ignal..
    Unmounting file systems
    Remounting remaining filesystems (if any) readonly
    SYSTEM REBOOTING
    md: stopping all md devices.
    flushing ide devices: hda hdb
    Restarting system.
    waiting for devices to flush..........done
    It is a mistake to think you can solve any major problems just with potatoes.

    #2
    Some quick questions although I'm not sure how much help I'll be.

    Are you doing the new partitioning on the CF drive or is it auto partitioning it that way with all those partitions and sizes? In the event that it's not finding enough space or expected space allocations you might try formatting just one partition for / and let it install to that or one for / and one for swap.

    It looks like it's trying to do some sort of RAID-5 which would imply 3 drives being installed. If there's a way not to do RAID that also may be part of the problem.

    Do you happen to have an IDE or SATA drive of the same size to test if it's the converter or a size issue?

    I see this is debian linux, is that something made for it or just a personal choice?
    Looking to acquire: IBM 5100, Altair 8800

    Comment


      #3
      looks like it's running some type of automated installation script, and physical reality isn't matching its assumptions.
      I see it's trying to use /dev/hdc which doesn't exist. is this installation script fully automated? does it have a list of hardware requirement somewhere? I am guessing it's trying to make RAID 5 which with only two CF card isn't feasible.

      Comment


        #4
        sorry, forgot that bit. the install cd takes over a 2nd pc and turns it into a boot/dhcp server. You then tell the cube to boot from network, and its all automated. I tried the install with 250gb drives and it seems to work okay, but it takes over an hour to boot, because it insists on checking the drives during boot with a fine-tooth comb. Thus I was thinking some small cf cards would make everything nice and simple. HA!

        It does default to a raid, but a mirror. by default it wants to mirror hda to hdc via software. The readout I have I got through the serial port, basically I just get to watch.

        Edit: Not all configs came with 2 hard drives. So its not REQUIRED to have 2 hard drives.
        It is a mistake to think you can solve any major problems just with potatoes.

        Comment

        Working...
        X