Using the Qube as a NAS device 2

In an earlier post I forgot to mention that installing NetBSD using the Restore CD option will wipe out your whole drive. So, before I started, I disconnected the hard drive and installed everything on the CF card. A basic installation of NetBSD does not require a lot of space. The 1 GB CF card was big enough for a basic install, but, to be able to use pkgsrc, I installed a 4 GB card.

After I verified the installation was working properly, I decided to connect the hard drive again. This is where the problems started :(

VIA Technologies VT83C572 USB Controller (USB serial bus, revision 0x02) at 
pci0 dev 9 function 2 not configured
tlp1 at pci0 dev 12 function 0: DECchip 21143 Ethernet, pass 4.1
tlp1: interrupting at level 2
tlp1: Ethernet address 00:10:e0:00:3c:5d
lxtphy1 at tlp1 phy 1: LXT970 10/100 media interface, rev. 3
lxtphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
wd0 at atabus0 drive 0: 
wd0: 977 MB, 1986 cyl, 16 head, 63 sec, 512 bytes/sect x 2001888 sectors
wd1 at atabus0 drive 1: 
wd1: 298 GB, 620181 cyl, 16 head, 63 sec, 512 bytes/sect x 625142448 sectors 
Kernelized RAIDframe activated
viaide0:0:1: lost interrupt
       type: ata tc_bcount: 512 tc_skip: 0
viaide0:0:1: bus-master DMA error: missing interrupt, status=0x61
viaide0:0:1: device timeout, c_bcount=512, c_skip0
wd1d: device timeout reading fsbn 0 (wd1 bn 0; cn 0 tn 0 sn 0), retrying
viaide0 channel 0: reset failed for drive 0 drive 1
viaide0:0:1: lost interrupt
       type: ata tc_bcount: 512 tc_skip: 0
viaide0:0:1: bus-master DMA error: missing interrupt, status=0x61
viaide0:0:1: device timeout, c_bcount=512, c_skip0
wd1d: device timeout reading fsbn 0 (wd1 bn 0; cn 0 tn 0 sn 0), retrying
... (several minutes, same message)
viaide0:0:1: lost interrupt
       type: ata tc_bcount: 512 tc_skip: 0
viaide0:0:1: bus-master DMA error: missing interrupt, status=0x61
viaide0:0:1: device timeout, c_bcount=512, c_skip0
wd1d: device timeout reading fsbn 1 (wd1 bn 1; cn 0 tn 0 sn 1), retrying
viaide0:0:1: lost interrupt
       type: ata tc_bcount: 512 tc_skip: 0
viaide0:0:1: bus-master DMA error: missing interrupt, status=0x61
viaide0:0:1: device timeout, c_bcount=512, c_skip0
wd1d: device timeout reading fsbn 1 (wd1 bn 1; cn 0 tn 0 sn 1), retrying
wd1: soft error (corrected)
wd1: no disk label
boot device: wd0
Hmmm, strange. This was definitely not a hardware problem, since the disk is fairly new and was working without any issues in Debian Lenny and Squeeze.

I suspected some kind of DMA problem, so I asked the friendly (yes, they are very friendly, not the RTFM kind) people for help. They suggested to recompile the kernel, and make it more suitable for running on my Qube. The following procedure describes how to do this on a recent Linux box (tried on openSUSE 12.1):

Go somewhere on the Linux machine, and do this: 

mkdir src tools obj
cvs -d :pserver:anoncvs%anoncvs.netbsd.org@localhost:/cvsroot checkout -PA  -rnetbsd-5 src
This will get you the latest 5.x source tree.
Go to src/sys/arch/cobalt/conf/
Copy GENERIC to some other name, edit it and save it.
Go back to src
Now, create tools ./build.sh -m cobalt tools
Now, build the kernel ./build.sh -m cobalt -T ./tooldir.Linux-3.1.9-1.4-desktop-x86_64 -O ../obj kernel=MyKernel
After a while it will end up in the obj/sys/.../netbsd
Put the kernel (netbsd) in / on the Qube, and rename the old kernel netbsd.old You can choose which kernel is booted at the Qube's boot prompt, by simply typing its name (if you're connected to the serial console).

Disabling DMA in the kernel config (GENERIC) was fairly easy. Locate the following lines: 

# IDE drives
# Flags are used only with controllers that support DMA operations
# and mode settings (e.g. some pciide controllers)
# The lowest order four bits (rightmost digit) of the flags define the PIO
# mode to use, the next set of four bits the DMA mode and the third set the
# UltraDMA mode. For each set of four bits, the 3 lower bits define the mode
# to use, and the last bit must be 1 for this setting to be used.
# For DMA and UDMA, 0xf (1111) means 'disable'.
# 0x0fac means 'use PIO mode 4, DMA mode 2, disable UltraDMA'.
# (0xc=1100, 0xa=1010, 0xf=1111)
# 0x0000 means "use whatever the drive claims to support".
wd*             at atabus? drive ? flags 0x0000
Now, do what the documentation says and put 0xf to disable DMA: 
wd*             at atabus? drive ? flags 0x0ff0
After compiling the kernel using the above procedure, the Qube boots just fine. What's more important; I can now actually use the machine as a NAS device. I already produced several backups using mondo on the Qube, without any problems.

Comments

Post a Comment

Popular posts from this blog

Remove copy protection from PDF documents

This is probably illegal, so use it at your own risk. Some PDFs on the internet have a copy protection to make sure you cannot copy-paste any content from the PDF into a document you're writing. To circumvent this protection there are several tools available on the internet. I haven't tried any of them, because they're not free ;) There is however a procedure that will enable you to circumvent the copy protection using free tools. The trick is to convert the PDF to a PS (PostScript) document first and then convert it back into a PDF. So, download Ghostview en Ghostscript from: http://www.cs.wisc.edu/~ghost/ . Next, open your PDF in Ghostview. Next, from the "File" menu, select "Convert" (a dialog will pop up) Press "Ok" Fill in the name of the "converted" file. Press "Save" Tada, you can now copy content from your newly created PDF ;)
Read more

The story of the Cobalt Qube

Image
The other week, a friendly colleague of mine brought me a small present. He gave me one of his Cobalt Qube s (for free!) which was collecting dust at his home. He was certain that I could give it a better use. I think I can still remember the days these things hit the market (somewhere in the late 90's). This was a home / office server appliance way before the people of Microsoft thought up their Windows Home Server . It was running some modified version of Linux RedHat, featuring a web interface for all administrative tasks. It also had 2 network cards, so you could easily turn it into a gateway / firewall. The RedHat version running on the Qube was known to be notoriously insecure. It was also running an older 2.0.x kernel which was outdated, even at that time. The Qube 2700 and Qube 2 were both equipped with a MIPS processor. Later models had an i386 architecture. Mine was a Qube 2. Getting the serial connection to work The Qube does not have any VGA adapter, so if you want to s...
Read more

The end of vinyl records

Vinyl records have been there for ages. My dad still has a couple of old records but he has no turntable anymore to play them. This is because _I_ claimed his turntable a long time ago, which he thought had become old fashioned. I started buying vinyl records about 12 years ago. I remember saving all my pocket money and buying the latest records with it, instead of visiting pubs with friends. I remember everyone thinking vinyl records belonged to the past and MP3's and CD's were taking over. In fact, this was not true. DJ's playing at parties and clubs never stopped buying records and from my experience, about 80% of their music came from plain old vinyl and a tiny 20% from other media like CD's or MP3's. The reasoning behind this is simple, if you wanted something new, something not popular (yet), you bought it on vinyl. If it became popular, some record company would probably be so kind to put it on some CD and sell it. But then again, ages, if not decades ( :) ) ...
Read more