2big NAS

[panda88]

i feel so stupid.

disks are not spinning at all.

where should i send you my nas? :)

[fvdw]

I have send you a pm

[fvdw]

your nas arrived today

Initially I connected a spare disk I had of 40GB to your nas, it did not work, same behavior, the disks refuse to spin up.
I checked the mainboard and there was one capacitor damaged. The super capacitor used to keep memory when it is switched off.

2bignas-italy.jpg

I replaced it but that didn't solve the problem. The disks still refuse to spin. I checked the voltage on the connectors on the mainboard and it seems to miss the 5 v and 3.3V.

So I connected the disk to an external power supply and sata cable connected to your nas. The disk spins up now but I got the feared ticking sound of the disk trying to read :shocked .After some attemps it gives up. :fuming Disk lost so th see. I don't know if connecting it to your nas has destoyed it but it can also be coincidence. It was rather old disk but I used it still this morning with no problem. Anyhow that one seems to be gone. :sob

I connected a second disk to the external power supply and connected the sata cable to your nas and now it works the kernel finds the disk

Code: Select all

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 3.14.2 (root@fvdwsl-5big2.local) (gcc version 4.8.1 (GCC) ) #171 PREEMPT Wed Jan 17 23:33:31 CET 2018
[    0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977
[    0.000000] CPU: VIVT data cache, VIVT instruction cache
[    0.000000] Machine: LaCie 2Big NAS

root@fvdw-sta-kirkwood:/ # dmesg | grep ata
[    0.000000] CPU: VIVT data cache, VIVT instruction cache
[    0.000000] Memory policy: Data cache writeback
[    0.000000] Memory: 249884K/262144K available (5950K kernel code, 220K rwdata, 1596K rodata, 1933K init, 233K bss, 12260K reserved)
[    0.000000]       .data : 0xc094c000 - 0xc0983100   ( 221 kB)
[   15.547954] libata version 3.00 loaded.
[   16.649358] ata1: SATA max UDMA/133 abar m512@0xe0010000 port 0xe0010100 irq 9
[   16.657064] sata_mv sata_mv.0: version 1.28
[   16.657114] sata_mv sata_mv.0: cannot get optional clkdev
[   16.662625] sata_mv sata_mv.0: slots 32 ports 2
[   16.669311] scsi1 : sata_mv
[   16.672494] scsi2 : sata_mv
[   16.675582] ata2: SATA max UDMA/133 irq 21
[   16.679766] ata3: SATA max UDMA/133 irq 21
[   16.999434] ata1: SATA link down (SStatus 0 SControl 300)
[   17.188474] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl F300)
[   17.229494] ata2.00: ATA-7: ST340014AS, 3.40, max UDMA/100
[   17.235001] ata2.00: 78165360 sectors, multi 0: LBA48
[   17.306827] ata2.00: configured for UDMA/100
[   17.340443] device-name= sata_mv
[   17.716797] ata3: SATA link down (SStatus 0 SControl F300)


My conclusion, most likely your smoking disk has damaged the the power circuit on the main board of your nas or a failure on the main board has destroyed your disk (and later my disk as well). The only solution will be an external power supply to power the disks, repairing the main board is I think a no go. let me see if there is a simple solution.

Ps I tried your 3 TB disk as well indeed it starts to smoke. I took off the printed circuit board on the bottom. Seems to be short circuit , one of the smd components smoke and draws a lot of power (with disk itself not connected on pc board). Probably the disk itself is ok but don't know if the pc board can be obtained separately. If not the disk must be considered as lost

[fvdw]

also you nas seems to have a corrupt nand flash memory.

Not a real problem

Code: Select all

   93.711004] __nand_correct_data: uncorrectable ECC error
[   93.716199] __nand_correct_data: uncorrectable ECC error<3>[   93.721594] end_request: I/O error, dev mtdblock0, sector 0
[   93.733501] __nand_correct_data: uncorrectable ECC error
[   93.738684] __nand_correct_data: uncorrectable ECC error<3>[   93.744040] end_request: I/O error, dev mtdblock0, sector 8
[   93.755932] __nand_correct_data: uncorrectable ECC error
[   93.761115] __nand_correct_data: uncorrectable ECC error<3>[   93.766477] end_request: I/O error, dev mtdblock0, sector 16
[   93.778419] __nand_correct_data: uncorrectable ECC error
[   93.783583] __nand_correct_data: uncorrectable ECC error<3>[   93.788940] end_request: I/O error, dev mtdblock0, sector 24
[   93.800955] __nand_correct_data: uncorrectable ECC error
[   93.806127] __nand_correct_data: uncorrectable ECC error<3>[   93.811517] end_request: I/O error, dev mtdblock0, sector 0
root@fvdw-sta-kirkwood:/ #


[panda88]

idk what to say... first of all though... THANKS!
having explanations of the facts that were happening is satisfactory, even if they are not so good news though.
do what you like with all the stuff i sent you, but not cut time from family and business! do it like an hobby! swear!

i feel guilty you lost a disk doing tests..

I'm in your hands, i trust on ur knowledge and experience so, just let me know if i can help!

thanks again

[Jocko]

Probably the disk itself is ok but don't know if the pc board can be obtained separately. If not the disk must be considered as lost

Yes you can if the disk is not too old but I am not sure if it is worth (price around 30/40% of a new disk).
See https://www.hddzone.com/

[fvdw]

thx Jocko for this tip :thumbup . Will look at that later.

In the meantime I looked somewhat closer to the mainboard and indeed some damage can be seen on the ic supplying 3,3 and 5 V. They are partly molten, see in red circles in the pictures below.

Why they are damaged on both disks power suppplies ? probably because you have the put the "smoking" disk in both slots :doh :pound

$matches[2]

$matches[2]

$matches[2]

I ordered a small power converter that should be able to supply power of 5V and 3.3 V to the disk, price including shipment was only 5 euro :-D Just for fun to see if we can bring it to live again. It is only 3x 3 cm so should fit somewhere in the casing.

power supply.JPG

ps don't worry about the disk I think it was not caused by your nas , just bad luck. And yes it is a hobby and I have plenty of time (retired) ;)

[panda88]

It’s lovely to see your progress!
I can’t explain how I didn’t notice those broken details by my own...
probably because I always tried to make it work late nighttime in low light conditions all the time to avoid waking up kids?!?

[fvdw]

I....
I can’t explain how I didn’t notice those broken details by my own...
probably because I always tried to make it work late nighttime in low light conditions all the time to avoid waking up kids?!?

probably but it is difficult to see.
When no disk is connected it looks like 12V, 5V and 3.3V is present on the connector, however if you connect something to it 5V and 3.3V drops fast (seems not able to deliver enough current anymore (burned out transitor)

Lets wait on the small power board and see if it works ( I am positive) :mrgreen:

[fvdw]

Its alive :punk :bananadance

I chose another approach as the mini power supply was not strong enough.
Some investigation on the internet learned that modern hard disk only need 5 and 12 V supply. Only a few require 3.3V. I personally never have seen a HDD that needed 3.3 V.
So thought why not use a 12V/5V external power supply instead of the original 12V supply. I have an old power supply from a philips spd8020 nas that has as output 5V and 12 V of resp 2.5A and 1.5A. Probably more then enough for two hard disk and main board. I connected it directly to the disks and also main board. And it works. Now the disk spins up and is recognized

Code: Select all

    0.000000] CPU: VIVT data cache, VIVT instruction cache
[    0.000000] Memory policy: Data cache writeback
[    0.000000] Memory: 249884K/262144K available (5950K kernel code, 220K rwdata, 1596K rodata, 1933K init, 233K bss, 12260K reserved)
[    0.000000]       .data : 0xc094c000 - 0xc0983100   ( 221 kB)
[   15.469961] libata version 3.00 loaded.
[   16.571339] ata1: SATA max UDMA/133 abar m512@0xe0010000 port 0xe0010100 irq 9
[   16.579043] sata_mv sata_mv.0: version 1.28
[   16.579093] sata_mv sata_mv.0: cannot get optional clkdev
[   16.584600] sata_mv sata_mv.0: slots 32 ports 2
[   16.591283] scsi1 : sata_mv
[   16.594466] scsi2 : sata_mv
[   16.597551] ata2: SATA max UDMA/133 irq 21
[   16.601734] ata3: SATA max UDMA/133 irq 21
[   16.921418] ata1: SATA link down (SStatus 0 SControl 300)

[   17.110508] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl F300)  <----here the sata link comes up !
[   17.151532] ata2.00: ATA-8: Hitachi HDP725050GLA360, GM4OA52A, max UDMA/133

[   17.158521] ata2.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 31/32)
[   17.238836] ata2.00: configured for UDMA/133
[   17.272443] device-name= sata_mv
[   17.648805] ata3: SATA link down (SStatus 0 SControl F300)



There is one point, if you connect the power then the disk immediately will spin up even if no firmware is loaded.
That is not necessary a problem as normally a nas is constantly running. Still need to check if the disk spin down function, it probably will be the case as that is controlled via firmware of the disk.

The standalone kernel runs and also the kernel need to check that out details, but we have progress

Below some pictures

2bignas-italy-6.jpg

2bignas-italy-7.jpg

2bignas-italy-8.jpg

2bignas-italy-9.jpg