Welcome, Guest. Please login or register.

Login with username, password and session length

 
Advanced search

221 Posts in 53 Topics- by 95 Members - Latest Member: execcr

December 01, 2008, 09:13:52 PM
Tribbox CommunityTribbox - Get supportInstallation, configuration supportHow to connect a SATA hard disk to the Tribbox
Pages: [1]
Print
Author Topic: How to connect a SATA hard disk to the Tribbox  (Read 941 times)
Tribboxer
Administrator
Newbie
*****
Posts: 7


View Profile Email
« on: March 07, 2008, 11:40:24 AM »

As taken from the frontpage:
HD Installation on the Tribbox


Step 1 - Unscrew and open the box

Picture 2: The board

Picture 3: Star Tip screwdriver - Tip: Magnetic screwdrivers work best!

Picture 4: The open box

Picture 5: SATA hard drive

Picture 6: Included with the Tribbox: SATA connection cable (far left), Power cable, Hard disk frame, shock-absorbing rubbers, screws.

Picture 7: Fit the 4 rubbers on the hard disk frame...

Picture 8: Place the hard drive on the frame and insert the 4 screws

Picture 9: Connect the 2 cables to the hard drive. Power cable (left), SATA cable (right)

Picture 10: Insert the power cable into the 4-pins at the rear of the box

Picture 11: Install the Hard Drive on the the board by screwing the frame down in the slots shown in Picture 4

Picture 12: connect the SATA Cable to the black, 7-pin input, as shown.
« Last Edit: March 07, 2008, 11:43:46 AM by Tribboxer » Logged
Michel
Newbie
*
Posts: 3


View Profile
« Reply #1 on: April 13, 2008, 12:14:42 AM »

Hi,

I did just that and now I am struggeling to get Linux installed on it.
I created a couple of ext3 partitions and now I am copying from an NFS mounted volumne to the harddrive, but I am getting horrible errors.

I am copying from inside an SSH session. The harddrive is a 3.5" SATA-II 200GB Samsung drive.

See following error messages:
Code:
stm_sata_interrupt: SStatus 0x00000113, SError 0x00180000
stm_sata_interrupt: SStatus 0x00000113, SError 0x00180000
stm_sata_interrupt: SStatus 0x00000113, SError 0x00080000
stm_sata_interrupt: SStatus 0x00000113, SError 0x00180000
stm_sata_interrupt: SStatus 0x00000113, SError 0x00080000
stm_sata_interrupt: SStatus 0x00000113, SError 0x00180000
stm_sata_interrupt: SStatus 0x00000113, SError 0x00180000
stm_sata_interrupt: SStatus 0x00000113, SError 0x00180000
stm_sata_interrupt: SStatus 0x00000113, SError 0x00180000
stm_sata_interrupt: SStatus 0x00000113, SError 0x00080000
stm_sata_interrupt: SStatus 0x00000113, SError 0x00180000
stm_sata_interrupt: SStatus 0x00000113, SError 0x00180000
stm_sata_interrupt: SStatus 0x00000113, SError 0x00080000
stm_sata_interrupt: SStatus 0x00000113, SError 0x00180000
stm_sata_interrupt: SStatus 0x00000113, SError 0x00180000
stm_sata_interrupt: SStatus 0x00000113, SError 0x00180000
stm_sata_interrupt: SStatus 0x00000113, SError 0x00080000
stm_sata_interrupt: SStatus 0x00000113, SError 0x00080000
stm_sata_interrupt: SStatus 0x00000113, SError 0x00180000
stm_sata_interrupt: SStatus 0x00000113, SError 0x00180000
stm_sata_interrupt: SStatus 0x00000113, SError 0x00180000
stm_sata_interrupt: SStatus 0x00000113, SError 0x00080000
stm_sata_interrupt: SStatus 0x00000113, SError 0x00180000
stm_sata_interrupt: SStatus 0x00000113, SError 0x00080000
stm_sata_interrupt: SStatus 0x00000113, SError 0x00180000
stm_sata_interrupt: SStatus 0x00000113, SError 0x00180000
stm_sata_interrupt: SStatus 0x00000113, SError 0x00080000
stm_sata_interrupt: SStatus 0x00000113, SError 0x00080000
stm_sata_interrupt: SStatus 0x00000113, SError 0x00180000
stm_sata_interrupt: SStatus 0x00000113, SError 0x00180000
stm_sata_interrupt: SStatus 0x00000113, SError 0x00180000
stm_sata_interrupt: SStatus 0x00000113, SError 0x00180000
stm_sata_interrupt: SStatus 0x00000113, SError 0x00180000
stm_sata_interrupt: SStatus 0x00000113, SError 0x00400100
stm_sata_interrupt: SStatus 0x00000113, SError 0x00180000
stm_sata_interrupt: SStatus 0x00000113, SError 0x00180000
stm_sata_interrupt: SStatus 0x00000113, SError 0x00180000
stm_sata_interrupt: SStatus 0x00000113, SError 0x00080000
stm_sata_interrupt: SStatus 0x00000113, SError 0x00180000
stm_sata_interrupt: SStatus 0x00000113, SError 0x00180000
stm_sata_interrupt: SStatus 0x00000113, SError 0x00080000
stm_sata_interrupt: SStatus 0x00000113, SError 0x00180000
stm_sata_interrupt: SStatus 0x00000113, SError 0x00180000
stm_sata_interrupt: SStatus 0x00000113, SError 0x00180000
stm_sata_interrupt: SStatus 0x00000113, SError 0x00180000
stm_sata_interrupt: SStatus 0x00000113, SError 0x00180000
stm_sata_interrupt: SStatus 0x00000113, SError 0x00180000
stm_sata_interrupt: SStatus 0x00000113, SError 0x00180000
stm_sata_interrupt: SStatus 0x00000113, SError 0x00180000
stm_sata_interrupt: SStatus 0x00000113, SError 0x00180000
stm_sata_interrupt: SStatus 0x00000113, SError 0x00080000
stm_sata_interrupt: SStatus 0x00000113, SError 0x00180000
stm_sata_interrupt: SStatus 0x00000113, SError 0x00180000
stm_sata_interrupt: SStatus 0x00000113, SError 0x00180000
stm_sata_interrupt: SStatus 0x00000113, SError 0x00180000
stm_sata_interrupt: SStatus 0x00000113, SError 0x00180000
stm_sata_interrupt: SStatus 0x00000113, SError 0x00080000
stm_sata_interrupt: SStatus 0x00000113, SError 0x00080000
stm_sata_interrupt: SStatus 0x00000113, SError 0x00080000
stm_sata_interrupt: SStatus 0x00000113, SError 0x00180000
stm_sata_interrupt: SStatus 0x00000113, SError 0x00180000
stm_sata_interrupt: SStatus 0x00000113, SError 0x00180000
stm_sata_interrupt: SStatus 0x00000113, SError 0x00180000
stm_sata_interrupt: SStatus 0x00000113, SError 0x00180000
ata1: command 0x35 timeout, stat 0xd0 host_stat 0x4
ata1: translated ATA stat/err 0xd0/00 to SCSI SK/ASC/ASCQ 0xb/47/00
ata1: status=0xd0 { Busy }
sd 0:0:0:0: SCSI error: return code = 0x8000002
sda: Current: sense key=0xb
    ASC=0x47 ASCQ=0x0
end_request: I/O error, dev sda, sector 35613870
Buffer I/O error on device sda5, logical block 4373409
lost page write due to I/O error on sda5
stm_sata_interrupt: SStatus 0x00000113, SError 0x00000800
ata1: command 0x35 timeout, stat 0xd0 host_stat 0x4
ata1: translated ATA stat/err 0xd0/00 to SCSI SK/ASC/ASCQ 0xb/47/00
ata1: status=0xd0 { Busy }
sd 0:0:0:0: SCSI error: return code = 0x8000002
sda: Current: sense key=0xb
    ASC=0x47 ASCQ=0x0
end_request: I/O error, dev sda, sector 35613878
Buffer I/O error on device sda5, logical block 4373410
lost page write due to I/O error on sda5
stm_sata_interrupt: SStatus 0x00000113, SError 0x00000800
ata1: command 0x35 timeout, stat 0xd0 host_stat 0x4
ata1: translated ATA stat/err 0xd0/00 to SCSI SK/ASC/ASCQ 0xb/47/00
ata1: status=0xd0 { Busy }
sd 0:0:0:0: SCSI error: return code = 0x8000002
sda: Current: sense key=0xb
    ASC=0x47 ASCQ=0x0
end_request: I/O error, dev sda, sector 35613886
Buffer I/O error on device sda5, logical block 4373411
lost page write due to I/O error on sda5
stm_sata_interrupt: SStatus 0x00000113, SError 0x00000800
ata1: command 0x35 timeout, stat 0xd0 host_stat 0x4
ata1: translated ATA stat/err 0xd0/00 to SCSI SK/ASC/ASCQ 0xb/47/00
ata1: status=0xd0 { Busy }
sd 0:0:0:0: SCSI error: return code = 0x8000002
sda: Current: sense key=0xb
    ASC=0x47 ASCQ=0x0
end_request: I/O error, dev sda, sector 35613894
Buffer I/O error on device sda5, logical block 4373412
lost page write due to I/O error on sda5

Is this a known problem or is my harddrive incompatible?
Logged
rvherk
Administrator
Jr. Member
*****
Posts: 57


View Profile Email
« Reply #2 on: April 15, 2008, 08:53:32 AM »

Hi,

Please check the cable connections first

Second, please make sure you use the latest kernel. There have been sata errors in the past, but these were fixed with kernel #26 (the current version)

BR,
Ron
Logged
mhaugstrup
Newbie
*
Posts: 3


View Profile
« Reply #3 on: September 01, 2008, 09:28:24 PM »

Hi Ron

Would you care to share to details on the necessary changes to the kernel. I'm having the exact same issues with:

Code:
SStatus 0x00000113, SError 0x00180000

when trying to boot the Tribbox on a ST-Linux 2-3 kernel, otherwise the kernel works fine.

Btw it only happens once during boot, and it seems that I can use the HDD fine.

Regards
Mikkel
« Last Edit: September 02, 2008, 08:30:24 PM by mhaugstrup » Logged
vvj
Newbie
*
Posts: 2


View Profile Email
« Reply #4 on: September 10, 2008, 01:37:38 PM »

--- linux-2.6.17.14_stm22_0036_7109SATA.orig/drivers/scsi/sata_stm.c    2006-12-14 15:05:02.000000000 +0530
+++ linux-2.6.17.14_stm22_0036_7109SATA/drivers/scsi/sata_stm.c 2006-12-14 12:07:09.000000000 +0530
@@ -883,7 +883,7 @@
    hpriv->phy_init = sata_private_info->phy_init;
    hpriv->softsg = readl(mmio_base + DMAC_COMP_PARAMS_2) &
        DMAC_COMP_PARAMS_2_CH0_HC_LLP;
-   //hpriv->softsg = 1;
+   hpriv->softsg = 1;

    printk(KERN_DEBUG DRV_NAME " using %sware scatter/gather\n",
           hpriv->softsg ? "soft" : "hard");
Logged
Pages: [1]
Print
Jump to:  

Get your Tribbox today our AllSiiShop