NAS - Network Attached Storage ili mrezni disk

[Lewis]

A sad pitanje, sto si navalio na upgrade tako rano ?
Ne drzis se one "ako radi nediraj..." ?

[xlr]

Nemam tocan odgovor na tvoje pitanje

[c-shadow]

Pa valjda po onoj poznatoj: "Novo je bolje"

[Lewis]

A dobro, bar ce ti nestrpljivi da istestiraju za nas ostale

[xlr]

Planiram pretvoriti ovaj (preskupi) nas u storage-only stroj i prestati ga updejtati, pa sam ga updejtao da zavrsim s tim dok jos imam volje prtljati oko njega. Usput sam naucio nesto novo i ispravio stackove za ubuduce win-win?

Al da, sad dolazi na red "if it ain't broken" filozofija.

[xlr]

Uglavnom, ako vrtite Docker na DSM-u, možda da pričekate s updejtom. Domena i linkovi na kontejnere mi ne radi, proxy manager ne radi, ne mogu se ni ulogirati u nj. Naravno, sve je radilo do neki dan. Sutra kada trebam na posao tako jasno da se sve živo raspalo. Ne sjećam se da sam ovoliko puta rebootao NAS valjda otkad sam ga kupio -.-

Nema jedne žive recenzije za 7.2 koja je spomenula moguće probleme s updejtom i kontejnerima #serenitynow

[Lewis]

Nije li docker sad komplet prebacen na novi container manager?

[xlr]

Je da, ali to je i dalje sve docker engine samo novije verzije. Da bi stvar bila jos bolja, uopce ne koristim Docker app ili novi Container manager app - samo docker-compose stackovi i Portainer stackovi za testiranje kroz GUI.

Postajem prestar za ovo majkemi

[The Exiled]

NASCompares su dosta toga za DSM 7.2 detaljno pokrili, ali opet ne mogu baš svaku situaciju.

[xlr]

Vecinu toga sam pogledao i pratim njihove komentare.

Anyway, jos jedan reboot nas-a je magicno sredio problem pristupa nas-u preko custom domene, nista nisam napravio, ali pazi sad ovo! Znaci nevjerojatno.

Koristim nginx proxy manager u kontejneru i u njemu sam podesio pristup uslugama preko vlastite domene i poddomena (proxyje). To je sve radilo, nisam nista dirao mjesecima, sve cakum pakum. Cloudflare certifikat, ssl, sve sve.

Updejtao na 7.2 i odonda se vise ne mogu ulogirati u nginx sa svojim podacima, kaze "no relevant user found". ALI mogu se logirati s default loginom (admin@example.com / changeme). Kada se logiram s tim podacima, nema spremljenih proxyja. Tako logicno.

Na koju foru meni domena radi, a nginx ne prepoznaje moj account na kojem su svi ti proxyji podeseni, pa krvi digitalne mu se napijem na papirnatu slamku.

[domy_os]

Autor domy_os

Što može biti uzrok sporom čitanju sa Synology DS-420+ NAS-a? Probao sam novi kabel, direktno bez routera, drugi PC i nikako dobiti preko 30 MB/s. Kopiranje na njega ide punom brzinom, u slučaju Gb mreže oko 115 MB/s.

Ima li netko ideju?

Danas sam skužio i da mu reboot/shutdown traje skoro pola sata. Da nije nestalo struje, ne bih ni pokušao shutdown. Na kraju je struja došla prije nego se ovaj isključio. Izgleda da je ovaj DSM od nekad stabilnog OS-a postao pravo *ovno.

[tomek@vz]

Autor domy_os

Ima li netko ideju?

Danas sam skužio i da mu reboot/shutdown traje skoro pola sata. Da nije nestalo struje, ne bih ni pokušao shutdown. Na kraju je struja došla prije nego se ovaj isključio. Izgleda da je ovaj DSM od nekad stabilnog OS-a postao pravo *ovno.

Da ti mozda koji od diskova nije "pred otkazom"? Nemam iskustva sa DSM-om ali nisam jednom vidio da performanse RAID polja drasticno padnu ako je jedan od diskova (ili vise njih) pred krepavanjem.

[Lewis]

Autor domy_os

Ima li netko ideju?

Danas sam skužio i da mu reboot/shutdown traje skoro pola sata. Da nije nestalo struje, ne bih ni pokušao shutdown. Na kraju je struja došla prije nego se ovaj isključio. Izgleda da je ovaj DSM od nekad stabilnog OS-a postao pravo *ovno.

Nerma sanse da reboot traje pola sata, ako je sve uredu, kao sto tomek kaze provjeri diskove, Meni reboot na 8 diskova (DS 1817+) traje cca 2 minute i nevidim nikakva usporenja u DSMu.

Provjeri SMART/testiraj diskove (koje diskove koristis ?)

[Night]

U DSMu možeš provjeriti SMART za svaki disk zasebno, ako negdje imaš realocirani sektor taj disk je spreman za otpis, mjenjaj, rebuildaj RAID i trebalo bi biti ok.

[domy_os]

Kroz GUI je sve zeleno...





A u terminalu kaže da ne podržava SMART, ne znam tko tu koga...

root@Domy-NAS:/var/log# smartctl -a /dev/sata1
smartctl 6.5 (build date Mar  2 2021) [x86_64-linux-4.4.59+] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor:               WDC
Product:              WD8003FFBX-68B9A
Revision:             0A83
User Capacity:        8,001,563,222,016 bytes [8.00 TB]
Logical block size:   512 bytes
Physical block size:  4096 bytes
LU is fully provisioned
Rotation Rate:        7200 rpm
Form Factor:          3.5 inches
Logical Unit id:      0x5000cca0c6d34591
Serial number:        VYHBD7RM
Device type:          disk
Local Time is:        Thu Jun  1 18:01:59 2023 CEST
SMART support is:     Unavailable - device lacks SMART capability.

=== START OF READ SMART DATA SECTION ===
Current Drive Temperature:     0 C
Drive Trip Temperature:        0 C

Error Counter logging not supported


[GLTSD (Global Logging Target Save Disable) set. Enable Save with '-S on']
Device does not support Self Test logging
root@Domy-NAS:/var/log# smartctl -a /dev/sata2
smartctl 6.5 (build date Mar  2 2021) [x86_64-linux-4.4.59+] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor:               WDC
Product:              WD8003FFBX-68B9A
Revision:             0A83
User Capacity:        8,001,563,222,016 bytes [8.00 TB]
Logical block size:   512 bytes
Physical block size:  4096 bytes
LU is fully provisioned
Rotation Rate:        7200 rpm
Form Factor:          3.5 inches
Logical Unit id:      0x5000cca0c6d3485e
Serial number:        VYHBDZVM
Device type:          disk
Local Time is:        Thu Jun  1 18:02:04 2023 CEST
SMART support is:     Unavailable - device lacks SMART capability.

=== START OF READ SMART DATA SECTION ===
Current Drive Temperature:     0 C
Drive Trip Temperature:        0 C

Error Counter logging not supported


[GLTSD (Global Logging Target Save Disable) set. Enable Save with '-S on']
Device does not support Self Test logging
root@Domy-NAS:/var/log# smartctl -a /dev/sata3
smartctl 6.5 (build date Mar  2 2021) [x86_64-linux-4.4.59+] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor:               WDC
Product:              WD8003FFBX-68B9A
Revision:             0A83
User Capacity:        8,001,563,222,016 bytes [8.00 TB]
Logical block size:   512 bytes
Physical block size:  4096 bytes
LU is fully provisioned
Rotation Rate:        7200 rpm
Form Factor:          3.5 inches
Logical Unit id:      0x5000cca0c6d340dd
Serial number:        VYHBAZWM
Device type:          disk
Local Time is:        Thu Jun  1 18:02:07 2023 CEST
SMART support is:     Unavailable - device lacks SMART capability.

=== START OF READ SMART DATA SECTION ===
Current Drive Temperature:     0 C
Drive Trip Temperature:        0 C

Error Counter logging not supported


[GLTSD (Global Logging Target Save Disable) set. Enable Save with '-S on']
Device does not support Self Test logging
root@Domy-NAS:/var/log# smartctl -a /dev/sata4
smartctl 6.5 (build date Mar  2 2021) [x86_64-linux-4.4.59+] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor:               WDC
Product:              WD8003FFBX-68B9A
Revision:             0A83
User Capacity:        8,001,563,222,016 bytes [8.00 TB]
Logical block size:   512 bytes
Physical block size:  4096 bytes
LU is fully provisioned
Rotation Rate:        7200 rpm
Form Factor:          3.5 inches
Logical Unit id:      0x5000cca0c6d325a2
Serial number:        VYHB3S0M
Device type:          disk
Local Time is:        Thu Jun  1 18:02:08 2023 CEST
SMART support is:     Unavailable - device lacks SMART capability.

=== START OF READ SMART DATA SECTION ===
Current Drive Temperature:     0 C
Drive Trip Temperature:        0 C

Error Counter logging not supported


[GLTSD (Global Logging Target Save Disable) set. Enable Save with '-S on']
Device does not support Self Test logging

I evo koliko mu traje restart, ne znam ima li koji prikladniji log...

root@Domy-NAS:/var/log# grep "2023-06-01" synologydrive.log
2023-06-01T14:57:54+02:00 Domy-NAS cloud-workerd: scemd_connector/scemd_connector.c:209 System isn't ready, so cannot get scemd status.
2023-06-01T14:57:55+02:00 Domy-NAS cloud-workerd: scemd_connector/scemd_connector.c:209 System isn't ready, so cannot get scemd status.
2023-06-01T14:57:56+02:00 Domy-NAS cloud-workerd: scemd_connector/scemd_connector.c:209 System isn't ready, so cannot get scemd status.
2023-06-01T14:57:57+02:00 Domy-NAS cloud-workerd: SYSTEM:       Last message 'scemd_connector/scem' repeated 3 times, suppressed by syslog-ng on Domy-NAS
2023-06-01T14:57:57+02:00 Domy-NAS cloud-control: (25815:27456) [INFO] daemon-control.cpp(152): Stopping clientd
2023-06-01T14:57:57+02:00 Domy-NAS cloud-control: (25815:27456) [INFO] daemon-control.cpp(152): Stopping syncd
2023-06-01T14:57:57+02:00 Domy-NAS cloud-control: (25815:27456) [INFO] daemon-control.cpp(152): Stopping workerd
2023-06-01T14:57:57+02:00 Domy-NAS cloud-control: (25815:27456) [INFO] daemon-control.cpp(152): Stopping apid
2023-06-01T14:58:00+02:00 Domy-NAS syncd: scemd_connector/scemd_connector.c:209 System isn't ready, so cannot get scemd status.
2023-06-01T14:58:01+02:00 Domy-NAS cloud-control: (25815:27456) [INFO] daemon-control.cpp(152): Stopping vmtouchd
2023-06-01T14:58:01+02:00 Domy-NAS cloud-control: (25815:27456) [INFO] daemon-control.cpp(152): Stopping redis
2023-06-01T14:58:01+02:00 Domy-NAS cloud-control: (25815:27456) [INFO] daemon-control.cpp(152): Stopping authd
2023-06-01T14:58:01+02:00 Domy-NAS synodrive-redis[18324]: User requested shutdown...
2023-06-01T14:58:01+02:00 Domy-NAS synodrive-redis[18324]: Redis is now ready to exit, bye bye...
2023-06-01T15:23:07+02:00 Domy-NAS updater-svr: Start updater, database is located at '/volume1'
2023-06-01T15:23:08+02:00 Domy-NAS updater-svr: End updater, ret = 0
2023-06-01T15:23:08+02:00 Domy-NAS cloud-control: share_name_path_get.c:309 Fail to get share by path [/volume1/@synologydrive]. [0x1400 share_name_path_get.c:137]
2023-06-01T15:23:08+02:00 Domy-NAS cloud-control: (17910:78304) [INFO] sdk-cpp.cpp(1752): SYNOSharePathGet(/volume1/@synologydrive/@sync): no such share
2023-06-01T15:23:08+02:00 Domy-NAS cloud-control: (17910:78304) [ERROR] share-service.cpp(31): SYNOShareGet(): -1 Error code: 5120
2023-06-01T15:23:08+02:00 Domy-NAS cloud-control: share_name_path_get.c:309 Fail to get share by path [/volume1/@synologydrive]. [0x1400 share_name_path_get.c:137]
2023-06-01T15:23:08+02:00 Domy-NAS cloud-control: (17910:78304) [INFO] sdk-cpp.cpp(1752): SYNOSharePathGet(/volume1/@synologydrive/@sync): no such share
2023-06-01T15:23:08+02:00 Domy-NAS cloud-control: (17910:78304) [INFO] daemon-control.cpp(123): Starting vmtouchd
2023-06-01T15:23:08+02:00 Domy-NAS cloud-control: (17910:78304) [INFO] daemon-control.cpp(123): Starting redis
2023-06-01T15:23:08+02:00 Domy-NAS cloud-control: (17910:78304) [INFO] daemon-control.cpp(123): Starting authd
2023-06-01T15:23:08+02:00 Domy-NAS synodrive-redis[17941]: Server initialized
2023-06-01T15:23:09+02:00 Domy-NAS cloud-control: (17910:78304) [INFO] daemon-control.cpp(123): Starting clientd
2023-06-01T15:23:09+02:00 Domy-NAS cloud-control: (17910:78304) [INFO] daemon-control.cpp(123): Starting syncd
2023-06-01T15:23:09+02:00 Domy-NAS cloud-control: (17910:78304) [INFO] daemon-control.cpp(123): Starting workerd
2023-06-01T15:23:09+02:00 Domy-NAS cloud-control: (17910:78304) [INFO] daemon-control.cpp(123): Starting apid
2023-06-01T15:23:11+02:00 Domy-NAS cloud-control: (17910:78304) [INFO] daemon-control.cpp(140): all daemon started.

Od aplikacija ništa posebno nemam...

[Psycho]

Autor pogi

Jedno pitanje... nisam baš uspio naći jasan odgovor na Synology stranicama.

Dakle imam Synology DS216play. Mali NAS sa dva diska. Vrtim na njemu DSM 7.1.1-42962 Update 4. E sad trenutno imam konfiguraciju 2x2Tb u RAID 1 i želim preći u 2x8Tb isto RAID 1. Ja sam to nekako ovako zamislio izvesti... naravno kad nabavim nove veće diskove

1. izvadim jedan 2Tb disk i zamijenim ga novim 8Tb
2. DSM napravi svoj posao i rekonstruira RAID 1 na novo ubačeni 8Gb disk, uz ograničenje da će iskoristiti samo 2Tb jer RAID 1 se naravno podesi prema manjem disku.
3. kada DSM sve odradi, izvadim preostali 2Tb i ubacim preostali 8Tb disk. DSM opet odradi svoje i dobijem RAID 1 polje veličine 2Tb na 8Tb diskovima.
4. DSM ima mogućnosti iskoristiti veličinu diskova do kraja i na kraju dobijem 8Tb RAID 1 polje na setu 2x8Tb diskovima...

Gdje je kvaka 22? Backup nisam niti spomenuo. Napraviti cu ga, naravno, ali me zanima da li u teoriji to može proći ovako kako sam naveo bez gubitaka podataka?

EDIT: je li problem ako je riječ o SHR-u, a ne RAID-1? Zamjenu diskova di izveo ovako:

Nedavno to radio i tocno kako si ti napisao. Mjenjao 12TB diskove sa 18TB diskovima (koji nisu sluzbeno podrzani kao). Trajalo oko 4 dana. Oko dan i pol po disku da se rebuilda raid.