bartvd  Freshman Member

I do get this info : [ 0.000000] Booting Linux on physical CPU 0 [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Linux version 3.2.54 (root@SDD2SVR2) (gcc version 4.8.5 20150209 (prerelease) (crosstool-NG 1.21.0) ) #1 SMP Fri Feb 21 13:32:42 CST 2020 [ 0.000000] CPU: ARMv7 Processor [412fc091] revision 1 (ARMv7),…

Sadly i get exactly the same logs on the second slot. I hear the drive starting up, but after about 2 minutes i hear a loud beep.

Hi! I get this info : ~ $ cat /proc/partitions major minor #blocks name 7 0 147456 loop0 31 0 256 mtdblock0 31 1 512 mtdblock1 31 2 256 mtdblock2 31 3 10240 mtdblock3 31 4 10240 mtdblock4 31 5 112640 mtdblock5 31 6 10240 mtdblock6 31 7 112640 mtdblock7 31 8 6144 mtdblock8 31 9 102424 mtdblock9 31 10 4464 mtdblock10 ~ $ cat…

Update, was ale to test HDD on a laptop of a mate, it is indeed broken, thanks for all the help!

Since it is also a toshiba, like my first HDD, it should not be incompatible, I am guessing that is indeed broken. It seems like it is not booting propably, therefor creating the noise. But how do i test if it is broken? I don't have a desktop where I can put it in for test.

It is the same drive as the first 1 : a 3TB Toshiba (HDWD130). The sound in my NAS is now a semi-loud biep sound, when i unplug the drive i can feel it has been turning. Does this ring a bell somewhere?

This was helpfull, however, i turned off my nas, added the 2nd HHD and restarted the NAS. The second hdd does not get recognised and I hear like a sort of clicking noise inside the NAS. Should I wait or is there something i didn't do correctly. On the NAS Storage manager, I cannot manage my internal storage, and when i…