hitachi hdd
- Thread starter levi45
- Start date
- Messages
- 6,174
Then it could be either hardware fault, cable broken up or still some software issue like that particular hard drive not being supported by current firmware. But maybe it is still worth a shot formatting it to ext3 first on pc or something then trying it again on ipbox.
What Hitachi model is it exactly, maybe somebody here already uses the same model with success. Then you could at least write off the option that firmware doesn't support that particular model.
What Hitachi model is it exactly, maybe somebody here already uses the same model with success. Then you could at least write off the option that firmware doesn't support that particular model.
The SATA Status and Error registers indicate that no link has been established, which points to a problem at the physical layer. Typically this would be a break in the cable or connector(s), or a fault with the PCB, or 5V rail to HDD, or the ST7109 chip, or the crystal used to derive the SATA bus clock, or the HDD itself.
I believe that when the HDD is detected, SStatus should have the value 0x00000113, which means that the interface is active at generation I signalling speed (1.5Gbps), and a device is detected and the PHY is ready.
If the HDD works in a PC with the same cable, it's likely that there's a fault in the IPBox. Whether this can be fixed with a firmware change is still TBD. It could just be mis-configuration of the ST7109 chip, such as a clock being set up incorrectly.
My box now works, and I still have U-Boot 1.1.2.
I believe that when the HDD is detected, SStatus should have the value 0x00000113, which means that the interface is active at generation I signalling speed (1.5Gbps), and a device is detected and the PHY is ready.
If the HDD works in a PC with the same cable, it's likely that there's a fault in the IPBox. Whether this can be fixed with a firmware change is still TBD. It could just be mis-configuration of the ST7109 chip, such as a clock being set up incorrectly.
My box now works, and I still have U-Boot 1.1.2.
@hulday,
I returned my box for repair via the shop I bought it from. I didn't receive any feedback about the fix for the problem though.
If you get in touch with the place you bought your box from, they may already be aware of the problem, or at least be able to ask the question of the approved repairer.
I returned my box for repair via the shop I bought it from. I didn't receive any feedback about the fix for the problem though.
If you get in touch with the place you bought your box from, they may already be aware of the problem, or at least be able to ask the question of the approved repairer.
so..on my HITACHI Deskstar HDD written:
P/N:0A35414
S/N:RE2EJNXA
CAPACUTY:500GB
MLC:BA2727
LBA:976.773.168 SECTOR
CHS:16383/16/63
MADE IN CHINA by Hitaci global E182115 CN
storage prducts(Shenzhen)Co..ltd CN
--------------------------------------------------
model: HDP725050GLA360
SATA: 3.0 Gb/s
RATED: 5v 360ml 12v 670 ml
PRM: 7200RPM
its have small place with 2 small pins,maybe for downgrade to sata 1?
what u think?
P/N:0A35414
S/N:RE2EJNXA
CAPACUTY:500GB
MLC:BA2727
LBA:976.773.168 SECTOR
CHS:16383/16/63
MADE IN CHINA by Hitaci global E182115 CN
storage prducts(Shenzhen)Co..ltd CN
--------------------------------------------------
model: HDP725050GLA360
SATA: 3.0 Gb/s
RATED: 5v 360ml 12v 670 ml
PRM: 7200RPM
its have small place with 2 small pins,maybe for downgrade to sata 1?
what u think?
There are data sheets at http://www.hitachigst.com/tech/techlib.nsf/products/Deskstar_P7K500 for this drive. Those two pins don't seem to be a feature selector on the SATA model... If it's not described on the HDD label, it's probably not a good idea to short those pins!
Hi guys,
I finally got my ipbox back.
you may remember this thread from august, when I was trying to get my IPBox to accept a HDD. I sent it back for repairs end of august. The distributor had to send it to Sweden. The repairs have taken a loooong time. so long that the distributor offered to give me a new box last week. So I went to pick it up and we tried out a Western Digital HDD there and it worked !!
So now I finally have an IPBox 9000 with HDD an I can get to do all the fun stuff I was dreaming of.
Thanks for the service, DVB Electronics !
I finally got my ipbox back.
you may remember this thread from august, when I was trying to get my IPBox to accept a HDD. I sent it back for repairs end of august. The distributor had to send it to Sweden. The repairs have taken a loooong time. so long that the distributor offered to give me a new box last week. So I went to pick it up and we tried out a Western Digital HDD there and it worked !!
So now I finally have an IPBox 9000 with HDD an I can get to do all the fun stuff I was dreaming of.
Thanks for the service, DVB Electronics !
here is my log.
what u think?
thanks man
what u think?
Code:
-sh-3.00# dmesg
Linux version 2.6.17.14_stm22_0037-cuberevo (dm7020@localhost) (gcc version 4.1.1 (STMicroelectronics/Linux Base 4.1.1-23)) #1 PREEMPT Mon Oct 6 13:10:53 CEST 2008
DGStation cuberevo board initialization
STb7109 version 3.x
On node 0 totalpages: 19200
DMA zone: 19200 pages, LIFO batch:3
Built 1 zonelists
Kernel command line: console=ttyAS1,115200 panic=3 root=/dev/mtdblock3 bigphysarea=1500 quiet
PID hash table entries: 512 (order: 9, 2048 bytes)
TMU0: ticks per jiffy = 16594
Using tmu for system timer
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 56320k/76800k available (2857k kernel code, 20424k reserved, 364k data, 96k init)
PVR=04061100 CVR=30480000 PRR=00009300
I-cache : n_ways=2 n_sets=256 way_incr=8192
I-cache : entry_mask=0x00001fe0 alias_mask=0x00001000 n_aliases=2
D-cache : n_ways=2 n_sets=512 way_incr=16384
D-cache : entry_mask=0x00003fe0 alias_mask=0x00003000 n_aliases=4
Calibrating delay loop... 263.16 BogoMIPS (lpj=131584)
Mount-cache hash table entries: 512
CPU: STb710x
NET: Registered protocol family 16
Generic PHY: Registered new driver
SCSI subsystem initialized
usbcore: registered new driver usbfs
usbcore: registered new driver hub
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 2, 16384 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 4096 bind 2048)
TCP reno registered
bigphysarea: Allocated 4060 pages at 0x847fe000.
squashfs: version 3.1 (2006/08/19) Phillip Lougher
JFFS2 version 2.2. (NAND) (C) 2001-2003 Red Hat, Inc.
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
STPIO layer initialised
STMicroelectronics ASC driver initialized
ttyAS0 at MMIO 0xb8032000 (irq = 121) is a asc
ttyAS1 at MMIO 0xb8033000 (irq = 120) is a asc
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
STMMAC driver:
platform registration... <6>done!
HW MAC address: 00:13:18:02:48:5a
mdiobus_register: found PHY and assigning IRQ -6
STMMAC MII Bus: probed
nwhw_config: device not found
libata version 1.20 loaded.
sata_stm version 0.3
sata_stm using hardware scatter/gather
sata_stm SATA version 1.00 DMA version 2.02
ata1: SATA max UDMA/133 cmd 0xB9209000 ctl 0xB9209820 bmdma 0x0 irq 170
ata1: SATA link down (SStatus 0)
scsi0 : sata_stm
Generic ST boards onboard flash device: 0x02000000 (32.0MB) at 0x00000000
drivers/mtd/maps/relook511.c init_stboards[217] onboard_map.virt = 0xa0000000
Onboard_Flash: Found 1 x16 devices at 0x0 in 16-bit bank
Amd/Fujitsu Extended Query Table at 0x0040
Onboard_Flash: CFI does not contain boot bank location. Assuming top.
number of CFI chips: 1
cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
Creating 9 MTD partitions on "Onboard_Flash":
0x00000000-0x00040000 : "nor.boot"
0x00040000-0x00060000 : "nor.config_welcome"
0x00060000-0x00260000 : "nor.kernel"
0x00260000-0x01600000 : "nor.root"
0x01600000-0x02000000 : "nor.db"
0x00060000-0x01600000 : "nor.kernel_root"
0x00060000-0x02000000 : "nor.kernel_root_db"
0x00040000-0x02000000 : "nor.all_noboot"
0x00000000-0x02000000 : "nor.all"
usbmon: debugfs is not available
ST40_start_host_control
ST40_start_host_control proceeding
ST40-ehci ST40-ehci.2: ST EHCI Host Controller
ST40-ehci ST40-ehci.2: new USB bus registered, assigned bus number 1
ST40-ehci ST40-ehci.2: irq 169, io mem 0xb91ffe00
ST40-ehci ST40-ehci.2: USB 0.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
2005 April 22 USB 1.1 'Open' Host Controller (OHCI) Driver (ST40)
ST40_start_host_control
ST40-ohci ST40-ohci.1: STB7100 OHCI
ST40-ohci ST40-ohci.1: new USB bus registered, assigned bus number 2
ST40-ohci ST40-ohci.1: irq 168, io mem 0xb91ffc00
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
Initializing USB Mass Storage driver...
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
pegasus: v0.6.13 (2005/11/13), Pegasus/Pegasus II USB Ethernet driver
usbcore: registered new driver pegasus
usbcore: registered new driver asix
usbcore: registered new driver cdc_ether
usbcore: registered new driver net1080
usbcore: registered new driver zaurus
i2c /dev entries driver
i2c_st40_pio: ST40 PIO based I2C Driver
i2c_st40_pio: allocated pin (2,0) for scl (0x84759c0c)
i2c_st40_pio: allocated pin (2,1) for sda (0x84759c1c)
i2c_st40_pio: allocated pin (3,0) for scl (0x84759c8c)
i2c_st40_pio: allocated pin (3,2) for sda (0x84759cac)
i2c_st40_pio: allocated pin (4,0) for scl (0x84759d0c)
i2c_st40_pio: allocated pin (4,1) for sda (0x84759d1c)
i2c_st40_pio bus 0: SCL=PIO2[0], SDA=PIO2[1]
i2c_st40_pio bus 1: SCL=PIO3[0], SDA=PIO3[2]
i2c_st40_pio bus 2: SCL=PIO4[0], SDA=PIO4[1]
STMicroelectronics - Coprocessors st231 Init
st-coprocessor-0: No RAM reserved
st231-0 Coprocessor -------------------------------------------
not configured!
---------------------------------------------------------------
st-coprocessor-1: No RAM reserved
st231-1 Coprocessor -------------------------------------------
not configured!
---------------------------------------------------------------
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
stmmac_open: MAC address 00:13:18:02:48:5a
IP-Config: Incomplete network configuration information.
VFS: Mounted root (squashfs filesystem) readonly.
Freeing unused kernel memory: 96k freed
Warning: unable to open an initial console.
Empty flash at 0x0000fffc ends at 0x00010000
CLEANMARKER node found at 0x00010000, not first node in block (0x00000000)
input: Relook IR Keyboard as /class/input/input0
ciio: module license 'unspecified' taints kernel.
ciio device driver.
ciio client i2c is attached
relook dvb device driver.
DVB: registering new adapter (relook).
slot_reset
slot_ts_enable
dvb_ca adapter 0: DVB CAM detected and initialised successfully
stmmac_open: MAC address 00:13:18:02:48:5a
stos_core_init_module(): Initializing STOS Module
stcommon_core_init_module(): Initializing STCOMMON Module
Setting all Group priorities done
PTI Clock: Cut 3.0 detected -> applying 27000000Hz oscillator config ...
Preproc Clock: Cut 3.0 detected -> setting Preproc clock.
mod_lxload_init: Initializing LXLOAD kernel Module, StartAddress: 0x04200000
LXLOADER virtual io kernel address of phys 0xa4200000 = 0xa4200000
lxload_open: major=254 minor=0
setting up Audio LX in NON-DEBUG mode
lxload_release: major=254 minor=0
Starting Audio LX by disabling reset
LX loaded:
Base: 0xa4200000
Last: 0xa427da24
Size:514596
mod_lxload_exit: Exiting LXLOAD kernel Module
mod_lxload_init: Initializing LXLOAD kernel Module, StartAddress: 0x04000000
LXLOADER virtual io kernel address of phys 0xa4000000 = 0xa4000000
lxload_open: major=254 minor=0
setting up LX in NON-DEBUG mode
lxload_release: major=254 minor=0
Starting video LX by disabling reset
LX loaded:
Base: 0xa4000000
Last: 0xa4093d9c
Size:605596
mod_lxload_exit: Exiting LXLOAD kernel Module
PHY: 0:01 - Link is Up - 100/Full
stvtg_ioctl_init_module: Initializing STVTG IOCTL Module
stvmix_ioctl_init_module: Initializing STVMIX IOCTL Module
Load module stevt_ioctl [251] by insmod (pid 366)
Load module stavmem_ioctl [250] by insmod (pid 366)
stvout_ioctl_init_module: Initializing STVOUT IOCTL Module
utils_ioctl_init_module: Initializing UTILS IOCTL Module
Load module stsmart_core [246] by insmod (pid 366)
Load module stsmart_ioctl [245] by insmod (pid 366)
Load module stmerge_ioctl [244] by insmod (pid 366)
Load module stpti4_core by insmod (pid 366)
Load module stpti4_ioctl [242] by insmod (pid 366)
sthdmi_ioctl_init_module: Initializing STHDMI IOCTL Module
Load module stpio_ioctl [239] by insmod (pid 366)
stpio_core_init_module(): Initializing STPIO Module
Load module staudlx_core [237] by insmod (pid 366)
Load module fdma [235] by insmod (pid 366)
Load module stfdma_ioctl [234] by insmod (pid 366)
stblit_ioctl_init_module: Initializing STBLIT IOCTL Module
Load module stclkrv_core by insmod (pid 366)
Load module stclkrv_ioctl [232] by insmod (pid 366)
ACCESS 00000002
Open Read/Write
stevt: Setting New buffer Size 102400
ACCESS 00000002
Open Read/Write
ACCESS 00000002
Open Read/Write
UTILS: ioctl command 0 [0x00007e00]
ACCESS 00000002
Open Read/Write
ACCESS 00000002
Open Read/Write
ACCESS 00000002
Open Read/Write
ACCESS 00000002
Open Read/Write
ACCESS 00000002
Open Read/Write
ACCESS 00000002
Open Read/Write
[stvid] start DecodeTaskFunc
ACCESS 00000002
Open Read/Write
[stvid] start DecodeTaskFunc
slot_shutdown
slot_reset
slot_ts_enable
dvb_ca adapter 0: DVB CAM detected and initialised successfully
Fixing up unaligned userspace access in "sbox" pid=548 pc=0x297f0f96 ins=0x6131
Fixing up unaligned userspace access in "sbox" pid=548 pc=0x297f0fa6 ins=0x2311
Fixing up unaligned userspace access in "sbox" pid=548 pc=0x00480c54 ins=0x06dd
Fixing up unaligned userspace access in "sbox" pid=548 pc=0x00480cde ins=0x01dd
stsmart_core: exports duplicate symbol STSMART_Unlock (owned by stapi)
[SCI] Smartcard wrapper ver 1.1 driver For Cuberevo and ipbox9000 (C)2008 Sandali
KERNEL API: Request Uart IRQ ...
KERNEL API: Interrupt Number 123
KERNEL API: Request Uart IRQ ...
KERNEL API: Interrupt Number 122
[SCI] Event daemon started!
Fixing up unaligned userspace access in "sbox" pid=498 pc=0x004776bc ins=0x61a1
Fixing up unaligned userspace access in "sbox" pid=498 pc=0x004776c8 ins=0x2a11
Fixing up unaligned userspace access in "sbox" pid=498 pc=0x00477720 ins=0x6261
Fixing up unaligned userspace access in "sbox" pid=498 pc=0x00477736 ins=0x2671
Fixing up unaligned userspace access in "sbox" pid=498 pc=0x004777a2 ins=0x8d02
Fixing up unaligned userspace access in "sbox" pid=498 pc=0x004777ae ins=0x6151
[stvid] Decoder started.
[stvid] Decoder stopped.
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decoder Error: 1
Decodthanks man
Last weekend I installed an internal Samsung 500 Gb on my IP 9000.
The issue is the Sata3Gb/s interface which is not accepted by the protocol of the IP BOX. What I did is I changed the jumper connects to 1.5 Gb/s Sata 1.
THere should be a 8 pin unused ( four on top, four beneath) box next to the Sata/power inputs.Normally there should be a jumper to provide backward compatibility between Sata 3gb/1.5 GB interfaces.
This jumper goes between pins 5 and 6 with the Sata plug input on the LEFT. This forces the protocol and makes the disc recognisable.Should be detailed in your Disk manual.
Either there wasn't a jumper in my shrink wrapping, or I through it out by mistake ! ( Samsung offer a DOS patch fix).
I physically shorted pins 5/6 with a piece of copper wire protected by some cardboard between the adjacent set of pins.
Box still hung before final reboot (hangs on START) so I re-flashed the image, re-booted, and hey, it worked.
Before you get to this, try a hard FORMAT HDD, same as USB upgrade except press arrow down instead of arrow right.
TerD
The issue is the Sata3Gb/s interface which is not accepted by the protocol of the IP BOX. What I did is I changed the jumper connects to 1.5 Gb/s Sata 1.
THere should be a 8 pin unused ( four on top, four beneath) box next to the Sata/power inputs.Normally there should be a jumper to provide backward compatibility between Sata 3gb/1.5 GB interfaces.
This jumper goes between pins 5 and 6 with the Sata plug input on the LEFT. This forces the protocol and makes the disc recognisable.Should be detailed in your Disk manual.
Either there wasn't a jumper in my shrink wrapping, or I through it out by mistake ! ( Samsung offer a DOS patch fix).
I physically shorted pins 5/6 with a piece of copper wire protected by some cardboard between the adjacent set of pins.
Box still hung before final reboot (hangs on START) so I re-flashed the image, re-booted, and hey, it worked.
Before you get to this, try a hard FORMAT HDD, same as USB upgrade except press arrow down instead of arrow right.
TerD
Hard drives: check Sat1 or Sata2
Well, I finaly got an HDD working.Got the internal Samsung 5OO G recommend by a forum member, only paid € 57 . But I gave up on the external LaCie which is now relegated to my photo backup.
Careful with the Samsung on opening the shrink wrap - I threw away the 4 mounting screws and probably the jumper for the Sata 2 to Sata 1 reset. In fact on Samsung box it doesn't say which version but warns you about protocol handshaking.The jumper is for backward compatibility.
I stuck a piece of copper wire between pins 5 and 6 to short them, reflashed Sifteam 8234 and rebooted - HDD came out of the grey zone and I was in business.
Contrary to reports on another forum the Samsung and the cooling fan are remarkably silent.
Moral: external HDD is not smart with the 6 times faster trasfer rates with SATA.But I'm surprised that Sata 1/2 is an issue at all with a Linux box.Samsung offer a quick patch fix ( but not for Linux).Make sure there's a jumper in the HDD box!
TerD
__________________
New owner of IPBOX 9000D with S&C tuners
Well, I finaly got an HDD working.Got the internal Samsung 5OO G recommend by a forum member, only paid € 57 . But I gave up on the external LaCie which is now relegated to my photo backup.
Careful with the Samsung on opening the shrink wrap - I threw away the 4 mounting screws and probably the jumper for the Sata 2 to Sata 1 reset. In fact on Samsung box it doesn't say which version but warns you about protocol handshaking.The jumper is for backward compatibility.
I stuck a piece of copper wire between pins 5 and 6 to short them, reflashed Sifteam 8234 and rebooted - HDD came out of the grey zone and I was in business.
Contrary to reports on another forum the Samsung and the cooling fan are remarkably silent.
Moral: external HDD is not smart with the 6 times faster trasfer rates with SATA.But I'm surprised that Sata 1/2 is an issue at all with a Linux box.Samsung offer a quick patch fix ( but not for Linux).Make sure there's a jumper in the HDD box!
TerD
__________________
New owner of IPBOX 9000D with S&C tuners
Hi Terd, just to be clear:
Is your box didn't work with HDD from the beginning as u can read in this thread?
becaus for many pepole the box work fine with HDD,just few boxes make this problem. so i wander if yours make the problem and u fix it your self,or yours was fine from the begining?
(sorry for my english)
Is your box didn't work with HDD from the beginning as u can read in this thread?
becaus for many pepole the box work fine with HDD,just few boxes make this problem. so i wander if yours make the problem and u fix it your self,or yours was fine from the begining?
(sorry for my english
)hulday,
The IPBox did recognise the SataII device as it accepted FORMAT HD forcing and I could see that the HDD was 'handshaking'.
THis was for both the Lacie external and the Samsung internal device.
However when rebooting both would caause the IP Box to hang on START, instead of moving on to the last channel selected.
Samsung say in their manual to expect this when a computer is only set up for Sata1.Protocol incompatibility between the 3 gb/s and 1.5 gb/s HDDs. So they offer backward compatibility with a jumper to set your new HDD to 1.5 gb/s.
My IPbox is version 2 so you may be quite right in suggesting that this may not even be an issue. If I had just re-flashed uboot and the latest sifteam image it could indeed have worked.
It's a shame that the firmware developers don't explain this to us. Samsung give a software patch to fix this, but only for Windows/Mac.
However advice from other members of this forum plus indications in the Samsung 500g manual made me work through this solution.
Regards
TerD
The IPBox did recognise the SataII device as it accepted FORMAT HD forcing and I could see that the HDD was 'handshaking'.
THis was for both the Lacie external and the Samsung internal device.
However when rebooting both would caause the IP Box to hang on START, instead of moving on to the last channel selected.
Samsung say in their manual to expect this when a computer is only set up for Sata1.Protocol incompatibility between the 3 gb/s and 1.5 gb/s HDDs. So they offer backward compatibility with a jumper to set your new HDD to 1.5 gb/s.
My IPbox is version 2 so you may be quite right in suggesting that this may not even be an issue. If I had just re-flashed uboot and the latest sifteam image it could indeed have worked.
It's a shame that the firmware developers don't explain this to us. Samsung give a software patch to fix this, but only for Windows/Mac.
However advice from other members of this forum plus indications in the Samsung 500g manual made me work through this solution.
Regards
TerD