Welcome! Log In Create A New Profile

Advanced

Do I have bad flash on my GoFlex Net?

Posted by bluemeanie 
Do I have bad flash on my GoFlex Net?
July 03, 2011 10:39PM
I have three GFN's, two of which seem to be happy and healthy on a new uBoot, and one that seems to be having issues. I followed the same procedure, using UBIT 0.6 on each of them, and they all boot identically up to loading the kernel:

U-Boot 2010.09 (Feb 16 2011 - 18:42:02)
UBIT v0.6 by Jeff Doozan and Peter Carmichael
(Re)start USB...
USB:   Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 1 USB Device(s) found
       scanning bus for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot:  0 
UBIFS error (pid 0): ubifs_get_sb: cannot open "ubi:fast", error -19
Error reading superblock on volume 'ubi:fast'!
UBIFS not mounted, use ubifs mount to mount volume first!
** Block device usb 0 not supported
** Block device usb 0 not supported

** Invalid boot device **

** Invalid boot device **
** Block device usb 1 not supported
** Block device usb 1 not supported

** Invalid boot device **

** Invalid boot device **
** Block device usb 2 not supported
** Block device usb 2 not supported

** Invalid boot device **

** Invalid boot device **
** Block device usb 3 not supported
** Block device usb 3 not supported

** Invalid boot device **

** Invalid boot device **

Reset IDE: Bus 0: OK Bus 1: OK 
  Device 0: Model: ST1500LM003-9YH148 Firm: CC94 Ser#: ********
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 1430799.3 MB = 1397.2 GB (-1364690128 x 512)
  Device 1: Model: ST1500LM003-9YH148 Firm: CC9F Ser#: ********
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 1430799.3 MB = 1397.2 GB (-1364690128 x 512)
Loading file "/boot/uImage" from ide device 0:1 (hda1)
2624664 bytes read
Loading file "/uInitrd" from ide device 0:1 (hda1)
** File not found /uInitrd
Loading file "/boot/uInitrd" from ide device 0:1 (hda1)
2640406 bytes read
## Booting kernel from Legacy Image at 00680000 ...
   Image Name:   Linux-2.6.39-ARCH
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2624600 Bytes = 2.5 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   UBIT-2010.11-00125-ga21bcca
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    2640342 Bytes = 2.5 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

After that, things go astray. The first two (good?) ones look something like this:

[   18.736339] rtc-mv rtc-mv: internal RTC not ticking
[   18.741553] mv_xor_shared mv_xor_shared.0: Marvell shared XOR driver
[   18.748019] mv_xor_shared mv_xor_shared.1: Marvell shared XOR driver
[   18.786365] mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
[   18.826366] mv_xor mv_xor.1: Marvell XOR: ( xor fill cpy )
[   18.866366] mv_xor mv_xor.2: Marvell XOR: ( xor cpy )
[   18.906366] mv_xor mv_xor.3: Marvell XOR: ( xor fill cpy )
[   18.912515] sdhci: Secure Digital Host Controller Interface driver
[   18.918790] sdhci: Copyright(c) Pierre Ossman
[   18.926375] usbcore: registered new interface driver r8712u
[   18.931996] oprofile: hardware counters not available
[   18.937222] oprofile: using timer interrupt.
[   18.942475] TCP cubic registered
[   18.945740] NET: Registered protocol family 17
[   18.950425] lib80211: common routines for IEEE802.11 drivers
[   18.956142] Registering the dns_resolver key type
[   18.961662] registered taskstats version 1
[   18.966560] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[   18.973129] Freeing init memory: 164K
[   19.716457] EXT3-fs: barriers not enabled
[   19.723770] kjournald starting.  Commit interval 5 seconds
[   19.729390] EXT3-fs (sda1): using internal journal
[   19.734231] EXT3-fs (sda1): mounted filesystem with writeback data mode

So far, so good.

The not-so-good one does this:

[   18.670427] rtc-mv rtc-mv: internal RTC not ticking
[   18.675636] mv_xor_shared mv_xor_shared.0: Marvell shared XOR driver
[   18.682104] mv_xor_shared mv_xor_shared.1: Marvell shared XOR driver
[   18.720455] mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
[   18.760455] mv_xor mv_xor.1: Marvell XOR: ( xor fill cpy )
[   18.800453] mv_xor mv_xor.2: Marvell XOR: ( xor cpy )
[   18.840455] mv_xor mv_xor.3: Marvell XOR: ( xor fill cpy )
[   18.846612] sdhci: Secure Digital Host Controller Interface driver
[   18.852881] sdhci: Copyright(c) Pierre Ossman
[   18.860474] usbcore: registered new interface driver r8712u
[   18.866096] oprofile: hardware counters not available
[   18.871322] oprofile: using timer interrupt.
[   18.876581] TCP cubic registered
[   18.879848] NET: Registered protocol family 17
[   18.884536] lib80211: common routines for IEEE802.11 drivers
[   18.890251] Registering the dns_resolver key type
[   18.895787] registered taskstats version 1
[   18.900688] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[   18.907265] Freeing init memory: 164K
[   19.152862] uncorrectable error : 
[   19.156998] end_request: I/O error, dev mtdblock3, sector 24
[   19.163453] Buffer I/O error on device mtdblock3, logical block 3
[   19.172628] uncorrectable error : 
[   19.175898] end_request: I/O error, dev mtdblock3, sector 40
[   19.181772] Buffer I/O error on device mtdblock3, logical block 5
[   19.209502] uncorrectable error : 
[   19.212785] end_request: I/O error, dev mtdblock3, sector 40
[   19.218658] Buffer I/O error on device mtdblock3, logical block 5
[   19.232858] uncorrectable error : 
[   19.236126] end_request: I/O error, dev mtdblock3, sector 272
[   19.242088] Buffer I/O error on device mtdblock3, logical block 34
[   19.250122] uncorrectable error : 
[   19.253429] end_request: I/O error, dev mtdblock2, sector 65408
[   19.259564] Buffer I/O error on device mtdblock2, logical block 8176
[   19.275923] uncorrectable error : 
[   19.279194] end_request: I/O error, dev mtdblock2, sector 64
[   19.285069] Buffer I/O error on device mtdblock2, logical block 8
[   19.293747] end_request: I/O error, dev mtdblock2, sector 88
[   19.299442] Buffer I/O error on device mtdblock2, logical block 11
[   19.310105] end_request: I/O error, dev mtdblock2, sector 128
[   19.315888] Buffer I/O error on device mtdblock2, logical block 16
[   19.324642] end_request: I/O error, dev mtdblock2, sector 152
[   19.330423] Buffer I/O error on device mtdblock2, logical block 19
[   19.338211] end_request: I/O error, dev mtdblock2, sector 168
[   19.343992] Buffer I/O error on device mtdblock2, logical block 21
[   19.352740] end_request: I/O error, dev mtdblock2, sector 192
[   19.377327] end_request: I/O error, dev mtdblock2, sector 320
[   19.383766] end_request: I/O error, dev mtdblock2, sector 328
[   19.396961] uncorrectable error : 
[   19.400221] end_request: I/O error, dev mtdblock2, sector 392
[   19.406816] uncorrectable error : 
[   19.410072] end_request: I/O error, dev mtdblock2, sector 400
[   19.416669] uncorrectable error : 
[   19.419925] end_request: I/O error, dev mtdblock2, sector 408
[   19.426522] uncorrectable error : 
[   19.429779] end_request: I/O error, dev mtdblock2, sector 416
[   19.436375] uncorrectable error : 
[   19.439633] end_request: I/O error, dev mtdblock2, sector 424
[   19.451109] end_request: I/O error, dev mtdblock2, sector 472
[   19.466007] uncorrectable error : 
[   19.469283] end_request: I/O error, dev mtdblock1, sector 56
[   19.476776] end_request: I/O error, dev mtdblock1, sector 72
[   19.488808] uncorrectable error : 
[   19.492083] end_request: I/O error, dev mtdblock1, sector 128
[   19.502939] end_request: I/O error, dev mtdblock1, sector 176
[   19.528480] uncorrectable error : 
[   19.531769] end_request: I/O error, dev mtdblock1, sector 312
[   19.547085] uncorrectable error : 
[   19.550344] end_request: I/O error, dev mtdblock1, sector 392
[   19.556941] uncorrectable error : 
[   19.560196] end_request: I/O error, dev mtdblock1, sector 400
[   19.566791] uncorrectable error : 
[   19.570049] end_request: I/O error, dev mtdblock1, sector 408
[   19.576644] uncorrectable error : 
[   19.579903] end_request: I/O error, dev mtdblock1, sector 416
[   19.586498] uncorrectable error : 
[   19.589756] end_request: I/O error, dev mtdblock1, sector 424
[   19.604575] end_request: I/O error, dev mtdblock0, sector 8
[   19.611807] uncorrectable error : 
[   19.615073] end_request: I/O error, dev mtdblock0, sector 24
[   19.623496] end_request: I/O error, dev mtdblock0, sector 48
[   19.631709] end_request: I/O error, dev mtdblock0, sector 72
[   19.640999] uncorrectable error : 
[   19.644260] end_request: I/O error, dev mtdblock0, sector 24
[   19.650805] uncorrectable error : 
[   19.654069] end_request: I/O error, dev mtdblock0, sector 24
[   19.991377] EXT3-fs: barriers not enabled
[   19.998896] EXT3-fs (sda1): warning: mounting unchecked fs, running e2fsck is recommended
[   20.007202] kjournald starting.  Commit interval 5 seconds
[   20.013051] EXT3-fs (sda1): using internal journal
[   20.017892] EXT3-fs (sda1): mounted filesystem with writeback data mode
[   20.048064] uncorrectable error : 
[   20.051549] end_request: I/O error, dev mtdblock3, sector 24
[   20.075813] end_request: I/O error, dev mtdblock1, sector 16
[   20.082318] end_request: I/O error, dev mtdblock1, sector 24

Does this one have bad flash or what? Did I make a mistake in the process of loading the new uBoot onto it?
I also notice that on the first two, running "fw_printenv" from within archlinux works correctly, where the third one gives me "Too few good blocks within range" when I run it. It at least starts up and boots, but I can't change any parms, like to fix the the ethernet address or anything. Is there a reasonable approach to getting this one back stable again - behaving like the other two that is - or am I going to have to cut my losses?

On another, related topic, I had intended to try re-flashing the third, problematic, one to see if it just didn't quite take correctly the first time. But it appears now that I can't get UBIT to start from within a running archlinux (it started fine from the stock pogoplug firmware, but that's gone now and I can't seem to get back to it). I'm using the same uInitrd and ubit_start that I've used for all of the other work, but when I run it from a booted archlinux, all I get is:

# ubit_start
No installed UBIT ramdisk could be found.
'ubit_start' needs to be run from the directory containing the UBIT ramdisk
or on a system with a UBIT ramdisk installed either at '/boot/uInitrd' or in 
        echo a UBIFS partition named 'fast', 'silent' or 'ramdisk'
#

Am I doing something wrong here? Is there a better/different way to get UBIT started? I have access to both netconsole and serial console if needed.

Help out a sorta-n00b anyone? I thought I was doing okay until this last GFN went all wonky on me.
Re: Do I have bad flash on my GoFlex Net?
February 02, 2012 11:08AM
Resurrecting an old post here, I know, but I apparently have exactly the same trouble as bluemeanie's 3rd unit with my GoFlex Home. Namely, fw_printenv returns "Too few good blocks within range" and dmesg is full of things like
[    5.883643] end_request: I/O error, dev mtdblock1, sector 12160
[    5.889601] Buffer I/O error on device mtdblock1, logical block 1520
[    5.896269] end_request: I/O error, dev mtdblock1, sector 0
[    5.901878] Buffer I/O error on device mtdblock1, logical block 0
[    5.908184] uncorrectable error : 
[    5.911443] uncorrectable error : 
[    5.914902] end_request: I/O error, dev mtdblock1, sector 8
[    5.920693] Buffer I/O error on device mtdblock1, logical block 1
and, earlier on,
[    3.718855] Bad eraseblock 0 at 0x000000000000
[    3.718902] Bad eraseblock 1 at 0x000000020000
[    3.718948] Bad eraseblock 2 at 0x000000040000
[    3.718994] Bad eraseblock 3 at 0x000000060000
[    3.719041] Bad eraseblock 4 at 0x000000080000
...etc, etc, all the way up to
[    3.814553] Bad eraseblock 2045 at 0x00000ffa0000
[    3.814600] Bad eraseblock 2046 at 0x00000ffc0000
[    3.814646] Bad eraseblock 2047 at 0x00000ffe0000

I've got to admit, I'm totally out of my depth here, so I'd really appreciate it if someone can talk me through this. I actually have a working ArchLinuxARM system, after following the instructions on the ArchLinuxARM website; I wouldn't have even noticed this problem, except the MAC address never got reset to the original one I entered, so I started digging! I've got this far, but I'm not ready to go firing off commands without knowing what I'm doing in case I brick my brand new drive!
Re: Do I have bad flash on my GoFlex Net?
April 26, 2012 08:10AM
I know this is an older topic, but I just came across it. This issue has now been resolved. I patched the board files for the kernel. Updating the kernel and rebooting should fix this.
Re: Do I have bad flash on my GoFlex Net?
April 26, 2012 03:34PM
It did indeed! Thanks :D
Author:

Your Email:


Subject:


Spam prevention:
Please, solve the mathematical question and enter the answer in the input field below. This is for blocking bots that try to post this form automatically.
Question: how much is 25 plus 13?
Message: