[Goflex Home 3TB] Newbie help

by **dannyp** » Tue Mar 20, 2012 1:44 am

@moonman. Yes I did the full upgrade first.

by **moonman** » Tue Mar 20, 2012 2:04 am

Well, I don't know why it is like that, but you shouldn't have any problems if you won't attach any usb drives. There's only one USB port anyway

I use it with USB to SERIAL adapter to U.S. Robotics modem

.

by **dannyp** » Fri Mar 23, 2012 1:34 pm

I just want to thank all that helped in sorting out my drive.

All is now good and I have had no problems, I now have samba, minidlna & mysql installed and working.

Thanks again,

Danny.

by **moonman** » Fri Mar 23, 2012 7:40 pm

Did you figure out "defauly"? Is automounting working right now?

by **JackDanielZ** » Mon Apr 09, 2012 5:08 am

Hi guys,

I wanted to tell you that the 3TB support works for me now, thanks to dannyp logs that helped me to understand how to configure it. It doesn't mean that I understood everything but for now, it works so I won't touch a long time.

Daniel

by **porchmonkey** » Sun May 06, 2012 12:05 pm

hey folks,

just wanted to drop by and thank you guys.
followed dannyp's post on how-to create the partitions using a desktop pc (fedora 16 live cd).
now i got alARM + sabnzbd / vsftpd running smooth, serving my needs.

thanks for sharing all the knowledge/ keep up the good work / you guys rock!

by **ajblowing** » Sun May 06, 2012 4:43 pm

Hi there, this is my first post as I am having the same issues with a 3TB Goflex Home. Was hoping someone could help me set this up using Mac OS X?

I have read through the thread and have got to the point of hooking up the Goflex base via ethernet to my Mac.

Then used terminal to enter the netconsole:

Code: Select all: macintosh:~ ajblowing$ sudo ifconfig en0 alias 10.10.10.5 macintosh:~ ajblowing$ nc -lu 10.10.10.5 6666 U-Boot 2010.09 (Feb 16 2011 - 18:44:23) 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: not available Device 0: Model: ST33000651AS Firm: CC43 Ser#: 9XK095R8 Type: Hard Disk Supports 48-bit addressing Capacity: 764436.4 MB = 746.5 GB (1565565872 x 512) Loading file "/boot/uImage" from ide device 0:1 (hda1) 2861640 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) 2643638 bytes read ## Booting kernel from Legacy Image at 00680000 ... Image Name: Linux-3.1.10-9-ARCH Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 2861576 Bytes = 2.7 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: 2643574 Bytes = 2.5 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ...

But it just says 'starting kernel' and I'm a bit lost as to how to repartition the drive with hmbr from this point?

Any advice would be greatly appreciated.

Thanks a lot.

by **moonman** » Sun May 06, 2012 9:59 pm

netconsole for kernel is on a different port, open up TWO console windows : one for kernel and one for u-Boot (they do have different ports, look in the guide)

Get gdisk for mac here: http://sourceforge.net/projects/gptfdis ... -binaries/

If it's not a Mac Pro then you need a usb to sata adapter to connect your 3TB drive to the computer directly. If you don't have one, get a PC Desktop and download a linux live cd to do everything.

by **ajblowing** » Wed May 09, 2012 10:33 pm

Ok, so I've repartitioned and created the hybrid MBR but the 2.7TB partition isn't showing up.

Output logs for reference:

fdisk -l

Code: Select all: [root@alarm ~]# fdisk -l Disk /dev/mtdblock0: 1 MB, 1048576 bytes 255 heads, 63 sectors/track, 0 cylinders, total 2048 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/mtdblock1: 6 MB, 6291456 bytes 255 heads, 63 sectors/track, 0 cylinders, total 12288 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/mtdblock2: 261 MB, 261095424 bytes 255 heads, 63 sectors/track, 31 cylinders, total 509952 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted. Disk /dev/sda: 3000.6 GB, 3000592982016 bytes 255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sda1 * 2048 40962047 20480000 83 Linux /dev/sda4 1 2047 1023+ ee GPT Partition table entries are not in disk order

gdisk -l /dev/sda

Code: Select all: [root@alarm ~]# gdisk -l /dev/sda GPT fdisk (gdisk) version 0.8.4 Partition table scan: MBR: hybrid BSD: not present APM: not present GPT: present Found valid GPT with hybrid MBR; using GPT. Disk /dev/sda: 5860533168 sectors, 2.7 TiB Logical sector size: 512 bytes Disk identifier (GUID): CCD1EB1A-74EC-4AB1-957C-BFE508805D7E Partition table holds up to 128 entries First usable sector is 34, last usable sector is 5860533131 Partitions will be aligned on 2048-sector boundaries Total free space is 2014 sectors (1007.0 KiB) Number Start (sector) End (sector) Size Code Name 1 2048 40962047 19.5 GiB 8300 Linux filesystem 2 40962048 5860533131 2.7 TiB 8300 Linux filesystem

dmesg | grep sd

Code: Select all: [root@alarm ~]# dmesg | grep sd [ 0.000000] Kernel command line: console=ttyS0,115200 mtdparts=orion_nand:1M(u-boot),6M(uImage),-(root) root=/dev/sda1 netconsole=@10.10.10.6/eth0,@10.10.10.4/ [ 20.317331] sdhci: Secure Digital Host Controller Interface driver [ 20.317341] sdhci: Copyright(c) Pierre Ossman [ 20.317410] sdhci-pltfm: SDHCI platform and OF driver helper [ 20.666524] sd 0:0:0:0: [sda] 5860533168 512-byte logical blocks: (3.00 TB/2.72 TiB) [ 20.666777] sd 0:0:0:0: [sda] Write Protect is off [ 20.666791] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [ 20.666899] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 20.667562] sd 0:0:0:0: Attached scsi generic sg0 type 0 [ 20.706845] sda: sda1 sda2 [ 20.708010] sd 0:0:0:0: [sda] Attached SCSI disk [ 22.147215] EXT2-fs (sda1): warning: mounting unchecked fs, running e2fsck is recommended [ 22.855718] EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 359523 [ 22.883960] EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 359523 [ 23.222189] EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 359523 [ 23.354672] EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 359523 [ 23.407489] EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 359523 [ 23.417468] EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 359523 [ 23.464192] EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 359523 [ 23.534834] EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 359523 [ 23.695208] EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 359523 [ 24.218666] EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 359523 [ 24.538474] EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 359523 [ 24.555154] EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 359523 [ 24.590445] EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 359523 [ 24.601475] EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 359523 [ 24.617410] EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 359523 [ 24.628890] EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 359523 [ 24.641209] EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 359523 [ 24.675019] EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 359523 [ 24.691661] EXT2-fs (sda1): warning: mounting unchecked fs, running e2fsck is recommended [ 24.695898] EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 359523 [ 24.713803] EXT2-fs (sda2): error: can't find an ext2 filesystem on dev sda2. [ 24.739953] EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 359523 [ 24.775114] EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 359523 [ 24.785236] EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 359523 [ 24.810477] EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 359523 [ 24.855316] EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 359523 [ 25.192512] EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 359523 [ 25.226074] EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 359497 [ 25.246225] EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 359523 [ 25.258764] EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 359523 [ 25.271660] EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 359523 [ 25.407640] EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 359523 [ 25.416254] EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 359523 [ 25.597805] EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 359523 [ 25.635679] EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 359523 [ 25.960829] EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 359501 [ 25.970420] EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 359501 [ 25.983982] EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 359523 [ 26.124838] EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 359523 [ 26.142453] EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 359523 [ 26.380938] EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 359507 [ 26.652343] EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 359523 [ 27.161186] EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 359523 [ 27.670067] EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 359523 [ 28.179009] EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 359523 [ 28.687861] EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 359523 [ 29.196215] EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 359523 [ 29.704580] EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 359523 [ 30.213337] EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 359523 [ 30.722189] EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 359523 [ 31.230951] EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 359523 [ 31.739806] EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 359523 [ 32.248573] EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 359523 [ 32.757263] EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 359523 [ 33.265620] EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 359523 [ 33.617019] EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 359507 [ 33.756016] EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 359523 [ 33.833728] EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 359523 [ 33.850808] EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 359523 [ 33.875813] EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 359523 [ 33.965731] EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 359523 [ 33.976919] EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 359523 [ 33.986668] EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 359523 [ 34.005481] EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 359523 [ 34.121484] EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 359523 [ 34.205665] EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 359523 [ 34.391377] EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 359523 [ 34.436597] EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 359523 [ 34.444409] EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 359523 [ 34.453353] EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 359523 [ 34.475761] EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 359523

Any ideas on how to resolve this?

Thanks in advance.

by **WarheadsSE** » Thu May 10, 2012 12:00 am

ajblowing wrote:Ok, so I've repartitioned and created the hybrid MBR but the 2.7TB partition isn't showing up.
Code: Select all
2 40962048 5860533131 2.7 TiB 8300 Linux filesystem

Code: Select all
[ 20.706845] sda: sda1 sda2 [ 24.713803] EXT2-fs (sda2): error: can't find an ext2 filesystem on dev sda2.

It's right there. Is it formatted?

[Goflex Home 3TB] Newbie help

Re: [Goflex Home 3TB] Newbie help

Re: [Goflex Home 3TB] Newbie help

Re: [Goflex Home 3TB] Newbie help

Re: [Goflex Home 3TB] Newbie help

Re: [Goflex Home 3TB] Newbie help

Re: [Goflex Home 3TB] Newbie help

Re: [Goflex Home 3TB] Newbie help

Re: [Goflex Home 3TB] Newbie help

Re: [Goflex Home 3TB] Newbie help

Re: [Goflex Home 3TB] Newbie help

Who is online