Help activity led flash blue\yellow

Post Reply
infinityxp
Posts: 2
Joined: Fri Jan 27, 2012 5:34 pm

Help activity led flash blue\yellow

Post by infinityxp » Fri Jan 27, 2012 6:01 pm

Hi,
I'm new here and i'm Italian (Yes italian, Berlusconi, Pizza, Mandolino and so on...) and i'm not very good to *write* in English. =)
Let's start with the story...
A my friend gave to me an Home Media Network with a faulty HD and firmware v. 1.029 (if i remember well), so i tried to change the HD with a test HD (80 GB) where i installed the firmware using this guide.
The test HD appears to boot normally, a blue led blinks for a while then it starts to blink blue\yellow.
I know, by reading all the wiki :), that it can be caused from my home network so i tried to restart all router\switch, i tried to connect it directly to a computer, but nothing.
I tried to reconnect the old and faulty HD (it was visible on network at first), but nothing it do like the test HD.
Reading around the forum i saw that the "dmesg" file can be usefull to understand what is the problem so i connected the test HD to PC and i took it and attached here.

If it can be fixed, who will help me have to know that i'm basically noob in linux environment so be very clear. Thanks
Another question; if network cannot be fixed, can i connect the Home media USB port to PC in order to use as normal external HD?

Thanks :)

I cannot attach the file... :(

Code: Select all

Linux version 2.6.24.4 (gp@mactel1.local) (gcc version 4.3.2 (crosstool-NG-1.3.1) ) #1 Mon Jun 1 11:21:53 MDT 2009
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
Machine: Oxsemi NAS
Ignoring unrecognised tag 0x00000000
Memory policy: ECC disabled, Data cache writeback
On node 0 totalpages: 16384
  DMA zone: 128 pages used for memmap
  DMA zone: 0 pages reserved
  DMA zone: 16256 pages, LIFO batch:3
  Normal zone: 0 pages used for memmap
  Movable zone: 0 pages used for memmap
CPU0: D VIVT write-back cache
CPU0: I cache: 32768 bytes, associativity 4, 32 byte lines, 256 sets
CPU0: D cache: 32768 bytes, associativity 4, 32 byte lines, 256 sets
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 16256
Kernel command line: elevator=cfq panic=20 root=/dev/sda1 console=ttyS0,115200 init=/linuxrc mem=64M powermode=controlledpup timeINC=46880
PID hash table entries: 256 (order: 8, 1024 bytes)
Console: colour dummy device 80x30
Using fractional divider baud 115200, clock 183333333 dlf 80
console [ttyS0] enabled
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 64MB = 64MB total
Memory: 61860KB available (2712K code, 156K data, 104K init)
Calibrating delay loop... 183.09 BogoMIPS (lpj=915456)
Security Framework initialized
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
net_namespace: 64 bytes
NET: Registered protocol family 16
Number of DMA channels = 5, version = 4
Allocating 891 SRAM generic DMA descriptors
Chip Id: die-id 0x07a032f0ec40 read back 0xbeefcafe
PCI: bus0: Fast back to back transfers enabled
SCSI subsystem initialized
libata version 3.00 loaded.
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 2048 (order: 2, 16384 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
TCP reno registered
Power button driver registered
Recovery button driver registered
SGI XFS with no debug enabled
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
serial8250: ttyS0 at MMIO 0x44300000 (irq = 24) is a 16550A
RAMDISK driver initialized: 16 RAM disks of 10240K size 1024 blocksize
loop: module loaded
Driver 'sd' needs updating - please use bus_type methods
ox810sata: OX810 sata core.
scsi0 : oxnassata
ata1: SATA max UDMA/133 irq 18
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata1.00: ATA-7: MAXTOR STM380215AS, 3.AAD, max UDMA/133
ata1.00: 156301488 sectors, multi 0: LBA48 NCQ (depth 0/32)
ata1.00: configured for UDMA/133
scsi 0:0:0:0: Direct-Access     MAXTOR   MAXTOR STM380215 3.AA PQ: 0 ANSI: 5
sd 0:0:0:0: [sda] 156301488 512-byte hardware sectors (80026 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 0:0:0:0: [sda] 156301488 512-byte hardware sectors (80026 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sda: sda1 sda2 sda3
sd 0:0:0:0: [sda] Attached SCSI disk
ox810sata: OX810 sata core.
scsi1 : oxnassata
ata2: SATA max UDMA/133 irq 18
ata2: SATA link down (SStatus 0 SControl 300)
mice: PS/2 mouse device common for all mice
Registered led device: oxnas-leds:bright
Registered led device: oxnas-leds:state
Registered led device: oxnas-leds:gauge
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem).
Freeing init memory: 104K
Using fractional divider baud 115200, clock 183333333 dlf 80
Using fractional divider baud 115200, clock 183333333 dlf 80
Using fractional divider baud 115200, clock 183333333 dlf 80
Using fractional divider baud 115200, clock 183333333 dlf 80
Using fractional divider baud 115200, clock 183333333 dlf 80
Using fractional divider baud 115200, clock 183333333 dlf 80
Using fractional divider baud 115200, clock 183333333 dlf 80
Probing for Synopsis GMAC, unit 0
eth0: No PHY found
synopsys_gmac_probe() Probing failed for eth0, err = 6
gmac_module_init() Failed to register platform driver instance 0
thermAndFan: initializing - ox810
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
10 Dec 2004 USB 2.0 'Enhanced' Host Controller (EHCI) Driver@e7000000 Device ID register 42fa05
oxnas-ehci oxnas-ehci.0: OXNAS EHCI Host Controller
oxnas-ehci oxnas-ehci.0: new USB bus registered, assigned bus number 1
oxnas-ehci oxnas-ehci.0: irq 7, io mem 0x00000000
oxnas-ehci oxnas-ehci.0: 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: 3 ports detected
usbcore: registered new interface driver libusual
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver usblp
Adding 524280k swap on /usr/local/swap.  Priority:-1 extents:137 across:545928k
it seems that there is a problem with the PHY.

Mijzelf
Posts: 6224
Joined: Mon Jun 16, 2008 10:45 am

Re: Help activity led flash blue\yellow

Post by Mijzelf » Fri Jan 27, 2012 7:29 pm

When you compare your log with the serial bootlog here, then you can see that the message

Code: Select all

eth0: No PHY found
synopsys_gmac_probe() Probing failed for eth0, err = 6
gmac_module_init() Failed to register platform driver instance 0
is well after init started. So it might be that something went wrong with preparing the disk.
The NIC of this board needs a kernel module to initialize. This module is readed from disk (/lib/modules/<kernel-version>/<something>/gmac.ko), and while initializing the module needs firmware which is also loaded from disk, by a helper process called udev. This is a delicate operation. When you -for instance- didn't have root credentials when unpacking sda1-2064.tgz, this could be the result.
infinityxp wrote:if network cannot be fixed, can i connect the Home media USB port to PC in order to use as normal external HD?
No, it's a host port, not a device port.

infinityxp
Posts: 2
Joined: Fri Jan 27, 2012 5:34 pm

Re: Help activity led flash blue\yellow

Post by infinityxp » Fri Jan 27, 2012 10:30 pm

Mijzelf wrote:When you compare your log with the serial bootlog here, then you can see that the message

Code: Select all

eth0: No PHY found
synopsys_gmac_probe() Probing failed for eth0, err = 6
gmac_module_init() Failed to register platform driver instance 0
is well after init started. So it might be that something went wrong with preparing the disk.
The NIC of this board needs a kernel module to initialize. This module is readed from disk (/lib/modules/<kernel-version>/<something>/gmac.ko), and while initializing the module needs firmware which is also loaded from disk, by a helper process called udev. This is a delicate operation. When you -for instance- didn't have root credentials when unpacking sda1-2064.tgz, this could be the result.
Still doesn't work. (same dmesg)
This time i got a copy of my terminal screen.
I'm using Linux Mint 64bit live on a USB flash.
Before this terminal session i set the root password using "sudo passwd"
Test HD is the only HD Connected.

Code: Select all

mint@mint ~ $ cat /proc/partitions
major minor  #blocks  name

   8        0   78150744 sda
   8       16    7812608 sdb
   8       17    7807558 sdb1
   7        0    1138776 loop0
mint@mint ~ $ su
Password:
mint mint # gzip -dc /home/mint/Desktop/stuff/mbr+uboot+kernel.gz | dd of=/dev/sda
14336+0 records in
14336+0 records out
7340032 bytes (7.3 MB) copied, 0.711593 s, 10.3 MB/s
mint mint # fdisk /dev/sda

WARNING: DOS-compatible mode is deprecated. It's strongly recommended to
         switch off the mode (command 'c') and change display units to
         sectors (command 'u').

Command (m for help): d
Partition number (1-4): 2

Command (m for help): n
Command action
   e   extended
   p   primary partition (1-4)
p
Partition number (1-4): 2
First cylinder (516-9729, default 516):
Using default value 516
Last cylinder, +cylinders or +size{K,M,G} (516-9729, default 9729):
Using default value 9729

Command (m for help): t
Partition number (1-4): 2
Hex code (type L to list codes): fd
Changed system type of partition 2 to fd (Linux raid autodetect)

Command (m for help): w
The partition table has been altered!

Calling ioctl() to re-read partition table.
Syncing disks.
mint mint # mke2fs -j /dev/sda1
mke2fs 1.42-WIP (02-Jul-2011)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
257536 inodes, 1028160 blocks
51408 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=1056964608
32 block groups
32768 blocks per group, 32768 fragments per group
8048 inodes per group
Superblock backups stored on blocks:
    32768, 98304, 163840, 229376, 294912, 819200, 884736

Allocating group tables: done                           
Writing inode tables: done                           
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 0 mounts or
0 days, whichever comes first.  Use tune2fs -c or -i to override.
mint mint # mkdir /tmp/sda1
mint mint # mount /dev/sda1 /tmp/sda1
mint mint # cd /tmp/sda1
mint sda1 # tar -xzf /home/mint/Desktop/stuff/sda1-2064.tgz
mint sda1 # mkfs -t xfs /dev/sda2
mkfs.xfs: /dev/sda2 appears to contain an existing filesystem (xfs).
mkfs.xfs: Use the -f option to force overwrite.
mint sda1 #
I have done something wrong? What should I do?
How do you explain the fact that the old (and almost broken) HD flashes like this now?
I'm pretty worried about this step in guide:
Nas-Central's Guide wrote:

Code: Select all

cd /tmp/sdb1
tar -xzf /full/path/to/sda1-2064.tgz
The last command will maybe give a lot of errors about unresolved symlinks in /etc/ssl/. This is normal. The symlinks point to files which really don't exist
I didn't get any kind of error. Why? (Wow, only here i'm sorry that there are not errors :( )
Mijzelf wrote:
infinityxp wrote:if network cannot be fixed, can i connect the Home media USB port to PC in order to use as normal external HD?
No, it's a host port, not a device port.
Really Thanks :D

Mijzelf
Posts: 6224
Joined: Mon Jun 16, 2008 10:45 am

Re: Help activity led flash blue\yellow

Post by Mijzelf » Sat Jan 28, 2012 8:49 am

infinityxp wrote:I have done something wrong?
No. Looks fine.

About the symlinks, others have also reported they didn't get errors. Don't know. Maybe that was an older firmware version, or another version of tar? Anyway, nothing to worry about.

Have you checked your power supply?

And else, well, with some effort it *is* possible to use an USB network controller, but I don't think the box is worth it. Unless you do it for fun, of course.

Post Reply