no serial, no network, bricked? led flashes...

[enki]

Peaslaker,

Yuppppii, I managed to boot and install Arch Linux ARM install. I did an update and installed SAMBA.

I plugged in the unit a GoFlex HDD in one of the SATA ports. It seams the SATA link up and the HDD was identified , but GoFlex Net but doesn't seams to have it mounted.


What can we do to recognize the HDD attached to GoFlex Net? I am booting from USB DISK.

Here are the relevant parts of my dmesg:

$this->bbcode_second_pass_code('', '
Linux version 2.6.37-ubit-01711-g50c16ad (root@vmdebian-cli) (gcc version 4.3.5 (Buildroot 2010.11-00070-g82ec21e) ) #1 Tue Feb 1 14:11:22 GMT 2011
CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977
CPU: VIVT data cache, VIVT instruction cache
Machine: Seagate GoFlex Net
.....................................
loop: module loaded
sata_mv sata_mv.0: version 1.28
sata_mv sata_mv.0: slots 32 ports 2
scsi0 : sata_mv
scsi1 : sata_mv
ata1: SATA max UDMA/133 irq 21
ata2: SATA max UDMA/133 irq 21
.......................................
ONFI flash detected
ONFI param page 0 valid
NAND device: Manufacturer ID: 0x2c, Chip ID: 0xda (Micron NAND 256MiB 3,3V 8-bit)
Scanning device for bad blocks
Bad eraseblock 38 at 0x0000004c0000
Bad eraseblock 246 at 0x000001ec0000
Bad eraseblock 269 at 0x0000021a0000
Bad eraseblock 480 at 0x000003c00000
Bad eraseblock 521 at 0x000004120000
Bad eraseblock 543 at 0x0000043e0000
Bad eraseblock 1916 at 0x00000ef80000
4 cmdlinepart partitions found on MTD device orion_nand
Creating 4 MTD partitions on "orion_nand":
0x000000000000-0x000000100000 : "u-boot"
0x000000100000-0x000000500000 : "uImage"
0x000000500000-0x000002500000 : "pogoplug"
0x000002500000-0x000010000000 : "root"
UBI: attaching mtd3 to ubi0
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 129024 bytes
UBI: smallest flash I/O unit: 2048
UBI: sub-page size: 512
UBI: VID header offset: 512 (aligned 512)
UBI: data offset: 2048
ata1: SATA link down (SStatus 0 SControl F300)
UBI: max. sequence number: 207
UBI: attached mtd3 to ubi0
UBI: MTD device name: "root"
UBI: MTD device size: 219 MiB
UBI: number of good PEBs: 1748
UBI: number of bad PEBs: 4
...........................

ata2: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
ata2.00: ATA-8: ST1000LM002-9VQ14L, CC94, max UDMA/133
ata2.00: 1953525168 sectors, multi 0: LBA48
ata2.00: configured for UDMA/133
scsi 1:0:0:0: Direct-Access ATA ST1000LM002-9VQ1 CC94 PQ: 0 ANSI: 5
sd 1:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
sd 1:0:0:0: [sda] 4096-byte physical blocks
sd 1:0:0:0: Attached scsi generic sg0 type 0
sd 1:0:0:0: [sda] Write Protect is off
sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sda: sda1
sd 1:0:0:0: [sda] Attached SCSI disk
..................................................
udev: starting version 157
udevd (897): /proc/897/oom_adj is deprecated, please use /proc/897/oom_score_adj instead.
(END)
')

Many thanks for your support,

[peaslaker]

We need to see the output of:
$this->bbcode_second_pass_code('', '
blkid
fdisk -l
mount
')

[enki]

$this->bbcode_second_pass_quote('peaslaker', 'W')e need to see the output of:
$this->bbcode_second_pass_code('', '
blkid
fdisk -l
mount
')

[peaslaker]

HPFS/NTFS

[peaslaker]

NTFS is just about the worst supported file system under Linux, with built-in fragility from open source trying to keep up with proprietary specification from Microsoft. Plus, there aren't any tools to repair the partition if anything bad should happen. The latest versions are better, but tend to be slower than alternatives.

Options are:
1. $this->bbcode_second_pass_code('', '
pacman -Sy ntfs-3g # never used it, can't support you in using it
')

2. Reformat to something else. If the disk is not going to be plugged in to other devices, go straight to a Linux native filesystem like ext3, but this will wipe the current content from the disk.

[enki]

Peaslaker,

Thank you for the unconditioned support. Thanks to you and forum I have managed to unbrick my GoFlex Net and get it working. Now I am using Samba and I have all hdds connected to it mapped to windowze on my laptops.

Leassons learned:
-go for UBIT boot it has much more recovery alternatives than any others,
-do not be afraid to use CA-42 cable for serial console, it's very easy, we have everything explained in wiki by courtesy of the team,
-put any questions you have on the forum or irc, there are people who can help you for sure

It was a nice journey and more will come along,
Regards