Buffalo NAS-Central Forums

Hi. I have just bought a used HS-DHTGL/R5 server, but whenever I boot it up, it is going into HS-DHTGL-EMFD8(?) -mode.
I have tried resetting it, with the button under the display, but same thing occours.
This resulting that I cannot install any firmware, even tho I am availible to access via. TFTP bootrecovery tools.
But whenever I try to use the hs-dhtgl-up_214_102-updater, with Debug enabled and a force update, it keeps telling me ACP_STATE_FAILURE.
Both discs are newly formatted, and hold no bootrecord.

I try using the acp_commander with following arguments: -t IP -cb; to clean an eventually boot, giving me this output:

Using target: 192.168.11.150/192.168.11.150
Starting authentication procedure...
Sending Discover packet...
Found: HS-DHTGL-EMFD8 (/192.168.11.150) HS-DHTGL/R5(ANNEI) (ID=00326)
mac: 00:16:01:BB:0F:D8 Firmware= 6.00 Key=688B3C1D
Trying to authenticate EnOneCmd... ACP_STATE_OK
Sending clear /boot command sequence... OK (ACP_STATE_OK)
Output of df for verification... Filesystem 1k-blocks Used
Available Use% Mounted on
/dev/root.old 13303 12655 648 95% /
/dev/ram1 15360 48 15312 0% /mnt/ram

-

Could anyone be helpfull on this subject, if any knowledge? Thanks in advance!
If any further information is needed, i will do my best

/Opiz

Did you followed this FAQ from Buffalo?
http://forums.buffalotech.com/t5/Storage/FAQ-2-of-5-Force-Firmware-update-procedure/td-p/100317

_________________
Please do not use private mail (PN/M) to ask questions. Use the proper forum instead. (me)

If there is no verified backup of a dataset, the dataset, by definition, is unimportant. (c't 2012)

RAID (no matter which level) never ever substitutes a backup. (me)

I have followed the FAQ, but nomatter what I do.. It keeps booting in EM-mode. And I get the ACP_STATE_FAILURE, whenever I try to update.
I've tried using the force-option, but with no luck either.. It keeps telling me there is the ACP error.

This is a screencap of the updater, before any attempts are made.

This is my uname on the server

root@HS-DHTGL-EMFD8:/sys# uname -a
Linux HS-DHTGL-EMFD8 2.6.16.16-arm1 #3 Wed Mar 7 13:21:58 JST 2007 armv5tejl unknown

followed by dmesg

root@HS-DHTGL-EMFD8:/mnt# dmesg
e: colour dummy device 80x30
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 128MB 0MB 0MB 0MB = 128MB total
Memory: 110464KB available (3128K code, 573K data, 112K init)
Calibrating delay loop... 498.07 BogoMIPS (lpj=2490368)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
checking if image is initramfs...it isn't (no cpio magic); looks like an initrd
Freeing initrd memory: 15360K
NET: Registered protocol family 16
FLASH boardId = 14
Flash bankwidth 1, base ff800000, size 400000
BUFFALO TS_HTGL FLASH size 4096[KB]

  Marvell Development Board (LSP Version 1.7.8_NAS)-- BUFFALO_BOARD_TS_HTGL_R5

 Detected Tclk 166664740 and SysClk 250000000
Marvell USB EHCI Host controller #0: c16f5e00
pexBarOverlapDetect: winNum 2 overlap current 0
mvPexInit:Warning :Bar 2 size is illigal
it will be disabled
please check Pex and CPU windows configuration
PCI: bus0: Fast back to back transfers enabled
PCI: bus1: Fast back to back transfers enabled
SCSI subsystem initialized
usbcore: registered new driver usbfs
usbcore: registered new driver hub
use IDMA acceleration in copy to/from user buffers. used channels 2 and 3
Done.
Fast Floating Point Emulator V0.9 (c) Peter Teichmann.
SGI XFS with large block numbers, no debug enabled
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
serial8250: ttyS0 at MMIO 0x0 (irq = 3) is a 16550A
serial8250: ttyS1 at MMIO 0x0 (irq = 4) is a 16550A
RAMDISK driver initialized: 3 RAM disks of 16384K size 1024 blocksize
loop: loaded (max 8 devices)
Marvell Gigabit Ethernet Driver 'egiga':
  o Ethernet descriptors in DRAM
  o DRAM SW cache-coherency
  o Checksum offload enabled
  o Loading network interface ** egiga_init_module (0)
'eth0'
Core Driver (ERROR)  0 : Warning: Future revision ID 02 for Device 6042. Impleme
nting latest workarounds
Core Driver (ERROR)  0 : disable pci conventional features when working in PCI-X
. pciCommand original value:0x0107e371. new value: 0x0107e011.
scsi0 : Marvell SCSI to SATA adapter
scsi1 : Marvell SCSI to SATA adapter
scsi2 : Marvell SCSI to SATA adapter
scsi3 : Marvell SCSI to SATA adapter
** BUFFALO Disable Command Queuing Function [0 0] **
** BUFFALO Disable Command Queuing Function [0 1] **
  Vendor: Maxtor    Model: 6V250F0           Rev: VA11
  Type:   Direct-Access                      ANSI SCSI revision: 03
  Vendor: Seagate   Model: ST9160310AS       Rev: 0303
  Type:   Direct-Access                      ANSI SCSI revision: 03
Linux IAL (ERROR) : retry command host=0, bus=0 SCpnt = c162d920
SCSI device sda: 490234752 512-byte hdwr sectors (251000 MB)
sda: Write Protect is off
sda: Mode Sense: 23 00 00 00
SCSI device sda: drive cache: write back
SCSI device sda: 490234752 512-byte hdwr sectors (251000 MB)
sda: Write Protect is off
sda: Mode Sense: 23 00 00 00
SCSI device sda: drive cache: write back
 sda: sda1
sd 0:0:0:0: Attached scsi disk sda
Linux IAL (ERROR) : retry command host=1, bus=1 SCpnt = c162d920
SCSI device sdb: 312581808 512-byte hdwr sectors (160042 MB)
sdb: Write Protect is off
sdb: Mode Sense: 23 00 00 00
SCSI device sdb: drive cache: write back
SCSI device sdb: 312581808 512-byte hdwr sectors (160042 MB)
sdb: Write Protect is off
sdb: Mode Sense: 23 00 00 00
SCSI device sdb: drive cache: write back
 sdb: sdb1 sdb2 < sdb5 >
sd 1:0:0:0: Attached scsi disk sdb
sd 0:0:0:0: Attached scsi generic sg0 type 0
sd 1:0:0:0: Attached scsi generic sg1 type 0
physmap flash device: 400000 at ff800000
CFI: Found no phys_mapped_flash device at location zero
>jedec_probe
Found: SST 39LF020
phys_mapped_flash: Found 1 x8 devices at 0x0 in 8-bit bank
phys_mapped_flash: Found an alias at 0x40000 for the chip at 0x0
phys_mapped_flash: Found an alias at 0x80000 for the chip at 0x0
phys_mapped_flash: Found an alias at 0xc0000 for the chip at 0x0
phys_mapped_flash: Found an alias at 0x100000 for the chip at 0x0
phys_mapped_flash: Found an alias at 0x140000 for the chip at 0x0
phys_mapped_flash: Found an alias at 0x180000 for the chip at 0x0
phys_mapped_flash: Found an alias at 0x1c0000 for the chip at 0x0
phys_mapped_flash: Found an alias at 0x200000 for the chip at 0x0
phys_mapped_flash: Found an alias at 0x240000 for the chip at 0x0
phys_mapped_flash: Found an alias at 0x280000 for the chip at 0x0
phys_mapped_flash: Found an alias at 0x2c0000 for the chip at 0x0
phys_mapped_flash: Found an alias at 0x300000 for the chip at 0x0
phys_mapped_flash: Found an alias at 0x340000 for the chip at 0x0
phys_mapped_flash: Found an alias at 0x380000 for the chip at 0x0
phys_mapped_flash: Found an alias at 0x3c0000 for the chip at 0x0
number of JEDEC chips: 1
cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
cmdlinepart partition parsing not available
RedBoot partition parsing not available
ehci_platform ehci_platform.4523: EHCI Platform Host Controller
ehci_platform ehci_platform.4523: new USB bus registered, assigned bus number 1
ehci_platform ehci_platform.4523: irq 17, io mem 0x00000000
ehci_platform ehci_platform.4523: 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
ohci_hcd: 2005 April 22 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
USB Universal Host Controller Interface driver v2.3
Initializing USB Mass Storage driver...
usb 1-1: new high speed USB device using ehci_platform and address 2
usb 1-1: configuration #1 chosen from 1 choice
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 4 ports detected
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
mice: PS/2 mouse device common for all mice
md: linear personality registered for level -1
md: raid0 personality registered for level 0
md: raid1 personality registered for level 1
md: raid5 personality registered for level 5
md: raid4 personality registered for level 4
raid5: measuring checksumming speed
   arm4regs  :   429.200 MB/sec
   8regs     :   330.000 MB/sec
   32regs    :   513.600 MB/sec
raid5: using function: 32regs (513.600 MB/sec)
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
Kernel event proc (C) BUFFALO INC. V.1.00 installed.
MICON ctrl (C) BUFFALO INC. V.1.00 installed.
MICON V2 (C) BUFFALO INC. V.1.00 installed.
UPSDRV (C) BUFFALO INC. V.1.00 installed.
BUFFALO UPS Recover Function Initialized.
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 3, 32768 bytes)
TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP reno registered
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
RAMDISK: Compressed image found at block 0
VFS: Mounted root (ext2 filesystem).
md: md0 stopped.
md: md1 stopped.
Freeing init memory: 112K
md: md0 stopped.
md: md1 stopped.
md: md0 stopped.
md: md1 stopped.
md: md0 stopped.
md: md1 stopped.
eth0: link down
eth0: link up<5>, full duplex<5>, speed 1 Gbps<5>
eth0: link down
eth0: link up<5>, full duplex<5>, speed 1 Gbps<5>
eth0: link down
eth0: link up<5>, full duplex<5>, speed 1 Gbps<5>
eth0: link down
eth0: link up<5>, full duplex<5>, speed 1 Gbps<5>
md: md0 stopped.
md: md1 stopped.
eth0: link down
eth0: link up<5>, full duplex<5>, speed 1 Gbps<5>

Maybe you should try to use only one drive or four drives
(and not two different ones) for firmware recovery.
Have you tried to start your OS in Safe-Mode (like advised
in the Buffalo FAQ) when starting the firmware updater?

_________________
Please do not use private mail (PN/M) to ask questions. Use the proper forum instead. (me)

If there is no verified backup of a dataset, the dataset, by definition, is unimportant. (c't 2012)

RAID (no matter which level) never ever substitutes a backup. (me)

I tried with only one drive, but no luck either. I still get the ACP_STATE_FAILURE, regardless if I bootup in Safe-Mode or not.

I first ran the TFTP boot, in order to get access, and then i ran the acp_commander to prevent ACP failure.
But the same error still occours when I try to install/update firmware

Sorry, but I am out of good advises then.
Maybe someone else has another good idea??

_________________
Please do not use private mail (PN/M) to ask questions. Use the proper forum instead. (me)

If there is no verified backup of a dataset, the dataset, by definition, is unimportant. (c't 2012)

RAID (no matter which level) never ever substitutes a backup. (me)

Thank you anyways for you time trying to help me out.

Another question would be, if there by any chance, is a possibility for me to install some Debian on the primary disk, and force the NAS to boot up on that disk instead of running own firmware/ramdisk?