Zyxel Forum - Herzlich Willkommen!

Aktuelle Zeit: Mo 9. Dez 2019, 19:15

Alle Zeiten sind UTC + 1 Stunde


Die Suche ergab 63 Treffer
Diese Ergebnisse durchsuchen:

Autor Nachricht

 Forum: NAS Geräte - FW5 Geräte / NAS devices - FW5 devices   Thema: Putting external hard drives to sleep

Verfasst: Sa 7. Dez 2019, 14:54 

Antworten: 7
Zugriffe: 29


stainless hat geschrieben:
Do you have some sort of donations? Since you helped me out twice now i would like to buy you a coffee / beer!

You get the same answer as ariek: https://homeforum.zyxel.com/discussion/ ... mment_7314

 Forum: NAS Geräte - FW5 Geräte / NAS devices - FW5 devices   Thema: Putting external hard drives to sleep

Verfasst: Mi 4. Dez 2019, 19:54 

Antworten: 7
Zugriffe: 29


Some lines below, there is the script which does the 'actual work'. Change here

for dev in \` $ls /sys/block/ | $grep sd \`

in

for dev in sda sdb

 Forum: NAS Geräte - FW5 Geräte / NAS devices - FW5 devices   Thema: Putting external hard drives to sleep

Verfasst: Mi 4. Dez 2019, 19:32 

Antworten: 7
Zugriffe: 29


Maybe. It skips the number of disks which is handled by the firmware old style. In your case that is zero. You can hardcode that to 4 (or whatever number of disks you have) on line 206, change local nrharddisk=` some shell command ` in local nrharddisk=4 A problem could be if the usb disks are detec...

 Forum: NAS Geräte - FW5 Geräte / NAS devices - FW5 devices   Thema: Putting external hard drives to sleep

Verfasst: Di 3. Dez 2019, 11:20 

Antworten: 7
Zugriffe: 29


The firmware puts the disks into sleep, the daemon hdidle is responsible for that. But it is possible that the (sata) commands are not passed by the USB-SATA bridge. You can try to use the ' USB Disk somnifacient ' plugin for Tweaks. I remember that for someone that did something that the firmware d...

 Forum: NAS Geräte - FW5 Geräte / NAS devices - FW5 devices   Thema: Volume down after attempting repair

 Betreff des Beitrags: Re: Volume down after attempting repair
Verfasst: Do 21. Nov 2019, 20:26 

Antworten: 14
Zugriffe: 191


If a (forced) filesystemcheck doesn't show errors, the filesystem is consistent, and so there's no stability problem. That data might be some file content, but it could also be a leftover of the raid header. You can have a look inside the archive file. If you see something recognizable it's probably...

 Forum: NAS Geräte - FW5 Geräte / NAS devices - FW5 devices   Thema: Volume down after attempting repair

 Betreff des Beitrags: Re: Volume down after attempting repair
Verfasst: Do 21. Nov 2019, 19:51 

Antworten: 14
Zugriffe: 191


The first megabyte of the 3th disk isn't synced, and so contains garbage. (probably zero's). You can have a look if the other disks contain something in the first megabyte. As this is raid5, that is the first 3MiB of the array. Poor man's data analysis: dd if=/dev/md2 bs=1M count=3 | gzip >md2.gz If...

 Forum: NAS Geräte - FW5 Geräte / NAS devices - FW5 devices   Thema: Volume down after attempting repair

 Betreff des Beitrags: Re: Volume down after attempting repair
Verfasst: Do 21. Nov 2019, 17:36 

Antworten: 14
Zugriffe: 191


Possibly. Depends on what is written to that 1MiB, and if the filesystem cares. Rebuild the array with the 3 original members, and add a '--bitmap=none' to the commandline. mdadm is picky on the sequence of the arguments, and I don't know where this has to be inserted. Fortunately it will spawn a cl...

 Forum: NAS Geräte - FW5 Geräte / NAS devices - FW5 devices   Thema: Volume down after attempting repair

 Betreff des Beitrags: Re: Volume down after attempting repair
Verfasst: Do 21. Nov 2019, 14:11 

Antworten: 14
Zugriffe: 191


Did you use the 'mdadm --create' as specified? Your new array has a bitmap in the header, while your old one hadn't. That is a problem, as it shifted the data offset: Data Offset : 262144 sectors Data Offset : 264192 sectors So now the array starts 2048 sectors (=1MiB) later. No wonder it can't be m...

 Forum: NAS Geräte - FW5 Geräte / NAS devices - FW5 devices   Thema: Volume down after attempting repair

 Betreff des Beitrags: Re: Volume down after attempting repair
Verfasst: Mi 20. Nov 2019, 15:26 

Antworten: 14
Zugriffe: 191


stainless hat geschrieben:
and then tried to add it to the raid. But here i get an error message. Any ideas how to proceed?
Code:
sudo mdadm --manage /dev/md2 --add /dev/sdb1
mdadm: /dev/sdb1 not large enough to join array

That should be /dev/sdb3, I hope.

 Forum: NAS Geräte - FW5 Geräte / NAS devices - FW5 devices   Thema: Volume down after attempting repair

 Betreff des Beitrags: Re: Volume down after attempting repair
Verfasst: Mi 20. Nov 2019, 10:29 

Antworten: 14
Zugriffe: 191


OK, the history information is this: /dev/sda3: Creation Time : Tue Nov 24 23:18:19 2015 Update Time : Thu Nov 14 16:31:43 2019 Device Role : Active device 3 /dev/sdb3: Creation Time : Tue Nov 24 23:18:19 2015 Update Time : Mon Nov 11 18:02:11 2019 Device Role : Active device 2 /dev/sdd3: Creation T...
Sortiere nach:  
Seite 1 von 7 [ Die Suche ergab 63 Treffer ]


Alle Zeiten sind UTC + 1 Stunde


Gehe zu:  
cron
Powered by phpBB® Forum Software © phpBB Group
Deutsche Übersetzung durch phpBB.de