Hard Drive Controller Issues ??

[gjdunga]

Greetings,

I have a Raq 3i
Intel  Flash [E28F008S5/Sharp LM28F008SCT 1024KB]
256MB  Ram
Amd Processor.

Firmware: 2.10.3-ext3

I am having issues with what appears to be the HDD controller.

My goal was to use this system as a Firewall.  I had also thought of the possibility of loading a slim hyper visor on it, and using it to load a small web server on it as well. 

However That would come later, provided i could actually get this thing to boot a normal enough *nix  system.

The system has had a previous Cobalt Os, and was in functional order when I got it..
I feel I've somehow mucked it up... 

I'm asking here, because I've not had a lot of  fruitful help or explanation. I've asked in a cpl of other places with little or no luck.  I'm hoping to find a raq guru to tell me what I'm doing wrong, or what's happening.. 

The answers I keep getting, amount to me sending my system into them, without explanation of what's wrong in the first place, and being charged money for them to install the software on the system..  I want to install it, feel I'm able to, and want to know what the duce is going on with it..  I am not a Linux Guru..  But I do quite well, when given the chance.

I even purchased a copy of Strong bolt 1 (Stupid me) to load on the system, as it was supposed to be be easy and had enough of a tool chain that i could have a fair place to start.  Their tech support and or guidance has been slim to none. 

Basically I'm getting a Kernel panic error, because of a drive seek error.
However, the drives and the cable have been tested and run *nix fine without errors or failures..  I've tried with a Segate U Series 5  20Gib &  40Gib drive.

Both Drives have been Dban'd  / And Check with Spinrite with a full flush of the drives.
I have been able to use them in other sytems just fine, and have seen no smart errors or channel chatter when loading other *Nix os's .  Ive seen no overheating of the drives, and the appear to work to spec. Even the Segate / WD tools say thier fine. (LOL)

I've Even purchased 2 new Cables to check just incase, each have the same effect.


I have my box connected to the Console port, when booting, and I have the console on to capture why it panics.  Log posted below.. 

Please review this, and tell me what in the heck I'm doing wrong? I don't think this is an LBA issue, as the 20Gb drive was what the system came with and had the cobalt OS on it!!  However I could be wrong.. Any suggestions would be helpful.. 

I have even had both drives going, and was able to mess with the system by putting the OS drive as hdb, but it too would eventually panic as well.. (Just tried harder /longer)

Code:

Sun Cobalt - Smaller, Bluer, Better, and Free
               Firmware version 2.10.3-ext3

Current date: May 04 03:16:17 UTC 2009
ROM build info: Thu Mar 11 08:51:36 MST 2004 .
System serial number: Uninitialized
System type: 3000 series system, Version 1 board
Silicon serial number: 7600000747224301
Monitor: 153536 bytes
Memory: 256 MB
CPU: 1 processor(s) detected
  CPU 0: AuthenticAMD 298MHz (3 x 100MHz host bus) [BSP]
Initializing flash: done
  Flash Bank 0: Intel E28F008S5/Sharp LM28F008SCT 1024KB (89:a6)
  Flash Bank 1: not installed.
Mounting ROM fs: done
Initializing PCI: done
  Host Bus: 0 (device 1f: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 8086:1209 Intel 82559ER EEPro100 Fast Ethernet (IRQ 11)
    Device: 12:00 8086:1209 Intel 82559ER EEPro100 Fast Ethernet (IRQ 10)
  Bridged Bus: 1 (bridge: 00:01:00)
Initializing ethernet: 2 controller(s) found
  Intel 82559ER Found at port 0xfd80, MAC: 00:10:e0:01:35:46
  Intel 82559ER Found at port 0xfd40, MAC: 00:10:e0:01:35:49
Initializing IDE: found ALI M5229 at 00:78
  scanning ide0: master
  scanning ide1:
IDE: stabilizing spinup:    100%
Checking Memory: done

Press spacebar to enter ROM mode
System is in LCD menu mode
Boot method is set to disk
Boot method is set to disk
Root device is set to 0x0304
Enabling L2 cache: done
First stage kernel (Linux): Decompressing -
- done
ERROR: cannot relocate with filesize 0
command line: 'console=ttyS0,115200 debug mem=22M cobalt_boot_image=/boot/vmlinux.bz2,/vmlinux.bz2,/boot/vmlinux.gz,/vmlinux.gz cobalt_boot_return=0x161f394 cobalt_boot_data=0x1634cc4 cobalt_boot_load=0x1700000 cobalt_ramcode_map=0x1600000,0xa00000 ip=off '
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 - 0000000010000000 (usable)
user-defined physical RAM map:
 user: 0000000000000000 - 000000000009f000 (usable)
 user: 0000000000100000 - 0000000001600000 (usable)
22MB LOWMEM available.
On node 0 totalpages: 5632
zone(0): 4096 pages.
zone(1): 1536 pages.
zone(2): 0 pages.
DMI not present.
Kernel command line: console=ttyS0,115200 debug mem=22M cobalt_boot_image=/boot/vmlinux.bz2,/vmlinux.bz2,/boot/vmlinux.gz,/vmlinux.gz cobalt_boot_return=0x161f394 cobalt_boot_data=0x1634cc4 cobalt_boot_load=0x1700000 cobalt_ramcode_map=0x1600000,0xa00000 ip=off
Initializing CPU#0
Detected 298.812 MHz processor.
Calibrating delay loop... 596.37 BogoMIPS
Memory: 20208k/22528k available (1141k kernel code, 1932k reserved, 244k data, 100k init, 0k highmem)
Dentry cache hash table entries: 4096 (order: 3, 32768 bytes)
Inode cache hash table entries: 2048 (order: 2, 16384 bytes)
Mount cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer cache hash table entries: 1024 (order: 0, 4096 bytes)
Page-cache hash table entries: 8192 (order: 3, 32768 bytes)
Enabling new style K6 write allocation for 22 Mb
CPU: L1 I Cache: 32K (32 bytes/line), D cache 32K (32 bytes/line)
CPU:     After generic, caps: 008021bf 808029bf 00000000 00000002
CPU:             Common caps: 008021bf 808029bf 00000000 00000002
CPU: AMD-K6(tm) 3D processor stepping 0c
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)
eepro100.c:v1.09j-t 9/29/99 Donald Becker http://www.scyld.com/network/eepro100.html
eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V. Savochkin <saw@saw.sw.com.sg> and others
eth0: Invalid EEPROM checksum 0x5815, check settings before activating this device!
eth0: PCI device 8086:1209, 00:10:E0:01:35:46, IRQ 11.
  Receiver lock-up bug exists -- enabling work-around.
  Board assembly 000000-000, Physical connectors present:
  Primary interface chip None PHY #0.
  General self-test: passed.
  Serial sub-system self-test: passed.
  Internal registers self-test: passed.
  ROM checksum self-test: passed (0xdbd8681d).
  Receiver lock-up workaround activated.
eth1: Invalid EEPROM checksum 0x5b15, check settings before activating this device!
eth1: PCI device 8086:1209, 00:10:E0:01:35:49, IRQ 10.
  Receiver lock-up bug exists -- enabling work-around.
  Board assembly 000000-000, Physical connectors present:
  Primary interface chip None PHY #0.
  General self-test: passed.
  Serial sub-system self-test: passed.
  Internal registers self-test: passed.
  ROM checksum self-test: passed (0xdbd8681d).
  Receiver lock-up workaround activated.
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: ST320413A, 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)
ide0 at 0xfdf8-0xfdff,0xfdf6 on irq 14
hda: attached ide-disk driver.
hda: host protected area => 1
hda: 39102336 sectors (20020 MB) w/1024KiB Cache, CHS=38792/16/63, UDMA(33)
Partition check:
 hda:hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide0: reset: success
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide0: reset: success
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
end_request: I/O error, dev 03:00 (hda), sector 0
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: 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     :   470.800 MB/sec
   32regs    :   264.000 MB/sec
   pII_mmx   :   676.000 MB/sec
   p5_mmx    :   650.400 MB/sec
raid5: using function: pII_mmx (676.000 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 512 buckets, 4Kbytes
TCP: Hash tables configured (established 1024 bind 2048)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
hda1: bad access: block=2, count=2
end_request: I/O error, dev 03:01 (hda), sector 2
EXT3-fs: unable to read superblock
hda1: bad access: block=2, count=2
end_request: I/O error, dev 03:01 (hda), sector 2
EXT2-fs: unable to read superblock
Kernel panic: VFS: Unable to mount root fs on 03:01

Gabriel J. Dungan
gjdunga@gmail.com

[Davesworld]

Before all else, try resetting the rom by holding down the E button while powering up, you will get an lcd indication when the reset was successful. Power it off then on again. I take it that you have Strongbolt installed?

[gjdunga]

Dave,

The Installer *WILL* run, but provides the panic as shown on boot..

Some have suggested to change default Boot device..  I've Tried hda /hdb in all partitions..   

I will try the ROM reset..

Rinse & Repeat..

(Thank you In advance!)

Gabriel

[gjdunga]

They System Stated that the CMOS was reset.

The same issue occured.  Tested with all three drives.

For Stupidity's sake, I'm assuming that the three Drive's i've used in the system up to this date are not going to work, even though I have tested them with spinrite / Dban / MFG tools.

Previous Drives Used: 
1 - * Came with Raq -OEM
Segate U Series 5 - 20 GB - Model: ST320413A -
CYL: 16,383 HDS: 16 SEC:63 LBA: 39,102,336

2 - * Spare I had lying around -OEM
Segate U Series 5 40GB - Model: ST340823A
CYL: 16,383 HDS: 16 SEC:63 LBA: 78,165,360

3- * Another Spare I had lying around - Retail - Used with Cobalt Restore
Maxtor 17.2-GB DiamondMax 4320 (91728D8)  UDMA/33 (EIDE)
CYL: 16383 HDS: 16 SEC: 63
 
 ---------------------------------------------------------------------------

I have an old maxtor 4320Mb (Model: 84320D4 )  Cyl: 6930 Hd: 185 Sec: 63
http://stason.org/TULARC/pc/hard-drives-hdd/maxtor/84320D4-DIAMOND-MAX-4320MB-3-5-SL-ATA4.html

When Placed in the Raq3 It didn't do the Seek Errors as described before, but i have no way to load an os on it, as the Cobalt Restore / Strongbolt CD will not accecpt it.. (Unable to partition to correct size) 

What would I need to do, to place your OS onto this drive using a registered version of Winimage?
The reason i ask, as it appears your default winimage is expandable from a 10gb up..  Or am I correct that if i were to expand your image onto it, it would take any space given it, and set it up dynamicly as long as it's  was 2500.mb (2179) for the hda1 ??  What sizes for the /boot and /swap ??

Thanks again in advance,

Gabriel Dungan

[gjdunga]

Boy I do have a lot of questions......

I was reading Something about the 550  Looking for ways to load linux on a raq.

http://wiki.archlinux.org/index.php/Installing_Arch_Linux_on_a_Sun_Cobalt_RAQ_550

Is any of the information here (Such as how the system boots) the same as My Raq device?
And if so, then I could Technically create a Vmware image the size of my drive, install Linux and Deps the Raq requires, write this to the drive, and try? 

Gabriel Dungan     

[Davesworld]

I have an old maxtor 4320Mb (Model: 84320D4 )  Cyl: 6930 Hd: 185 Sec: 63
http://stason.org/TULARC/pc/hard-drives-hdd/maxtor/84320D4-DIAMOND-MAX-4320MB-3-5-SL-ATA4.html

When Placed in the Raq3 It didn't do the Seek Errors as described before, but i have no way to load an os on it, as the Cobalt Restore / Strongbolt CD will not accecpt it.. (Unable to partition to correct size) 

What would I need to do, to place your OS onto this drive using a registered version of Winimage?
The reason i ask, as it appears your default winimage is expandable from a 10gb up..  Or am I correct that if i were to expand your image onto it, it would take any space given it, and set it up dynamicly as long as it's  was 2500.mb (2179) for the hda1 ??  What sizes for the /boot and /swap ??

Thanks again in advance,

Gabriel Dungan

That drive is too small for any of my images. The 10GB and 20GB will use the full size indicated when expanded. You only need the  registered version of Winimage once the trial is over. It's too bad you don't have a second raq to test the drives on. I haven't ruled out a bad rom flash since you DO have the Intel rom and the same drive worked before the flash.

[Davesworld]

Boy I do have a lot of questions......

I was reading Something about the 550  Looking for ways to load linux on a raq.

http://wiki.archlinux.org/index.php/Installing_Arch_Linux_on_a_Sun_Cobalt_RAQ_550

Is any of the information here (Such as how the system boots) the same as My Raq device?
And if so, then I could Technically create a Vmware image the size of my drive, install Linux and Deps the Raq requires, write this to the drive, and try? 

Gabriel Dungan     

The booting principle is the same although here we and IPCop for that matter do not use the newer ata drivers (for some reason they are still listed as experimental even on the newest 2.6 kernel) so the drives are still hdx not sdx.

The 550 is the newest Raq of the bunch and uses a larger flash rom. I have at least one of every Raq and a Qube3.

You need to sort the drive seek issue before anything else. Since this is happening while the rom kernel is running and occured AFTER Strongbolt installed the newer rom image (2.10.3-ext3), a reflash may be needed. There are a few versions of the flash tool but the larger one we have here works on Intel roms which is what you have.

[gjdunga]

Okay, I understand where you coming from..

The issue is, I going to have to flash this baby thru the Console port.. 

What version of the flash are you suggesting?

Gabriel