jimpa

Hi all! SHR-2 Crashed 3 failed HDD, please help, only 2 disks report crashed in red color but I have still 2 disks initiated but I can't use "Manage" button to repair. I have SHR-2 with 2 failing disk but I see that I got 3 disks with problems..... How can I get back my data. in Putty the MD2 seems quiet ok I just need 80-90% of the data back because is so much. I need someone that knows this in detail and ask also for more data if needed from me. It seems that I need assistance due to mange button can't be used (it greyed) even I have 2 disks available for mending the volume. Anyway I need help to fix the volume. It seems that \md2 is the raid that has the info back as I need. Check the picture. I need one more disk up and running to get the volume intact again. That is the help I need. https://unsee.cc/b006d547/ root@NASSE:/usr# cat /proc/mdstat Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] [raidF1] md2 : active raid6 sdk5[0] sdg5[21] sdj5[16] sdi5[15] sdb5[20] sdf5[18] sdd5[11] sdc5[10] sdh5[22] sda5[8] sdr5[7] sdq5[23] sdp5[4] sde5[24] sdm5[2] 31178806272 blocks super 1.2 level 6, 64k chunk, algorithm 2 [18/15] [U_UUUU_UUUUU_UUUUU] Please reply fast but with accurate information.

I had power problem inside chassi. I just check all and change hexcode to 22 disks then all is fine.

I had power problem inside chassi. I just check all and change hexcode to 22 disks then all is fine.

Is there no chance in the world to get more than a total of 12 INTERNAL SATA disks up and running in this last code: DSM_DS3615xs_5592 + Update3. Have 16 SATA disks installed andbooted on USB stick and installed....but only see 12 internal disks the rest..is not visual. Even after my knowledge all year 2014 to edit hexcodes I add to have 22 disks but still only showing 12...only difference I get is that the usb stick get higher number and that Disk manager Overview says 11 slots free. Do I really need to mount my internal drives through the back and connect them to external ESATA ports?

I have now worked with the 4.3 releases since new year and I have almost got all working. BUT...for all of you. There is for me no secured way to expand the volume in Raid 6 SHR-2 when using 14 or more disks. When I added a 2TB disk extra to my volume so it will be 14 disks in the volume I got it into the volume but it do not have the possibility to expand the volume inside the DSM. I had same problem a couple of weeks ago also doing the same but added 2 disks at the same time. Then I tried following all guides to manually expand the volume and it did worked to expand the volume but the volume was crashed somehow and could not write to the volume all files read only. I had to backup all data again and made a totally new installation. Now again I am at the same situation and added 1 disk and that worked ok but cant be expanding the volume in DSM. Now is my question if anyone have used more than 14 disks in a volume. If so...I am pretty sure it worked to create it and have all capabilities to use the data environment as when you created it, but the problem is that IF a disk crashes you will be able to fix the volume due to expanding not working with so many disks. Even if you typed in 16 as amount of disk in the synoinfo.conf files. Do anyone have got a working system with 14 disks and tried to replaced one disk? If not then I suggest that I would be for sure super happy if this wonderful system could be added to work with lot of more disks. I guess to start building it on another kernel for the larger Synology stations. I even pay for it. thanks all for all contributing of info and questions that helped me a lot these months....but I have now to start making backup again but I did not move over so much data this time so I will start over again with fewer disks so I get this system up and running and start over when I got response on this question. any tip or trick is wormly appreciated.

I have now worked with the 4.3 releases since new year and I have almost got all working. BUT...for all of you. There is for me no secured way to expand the volume in Raid 6 SHR-2 when using 14 or more disks. When I added a 2TB disk extra to my volume so it will be 14 disks in the volume I got it into the volume but it do not have the possibility to expand the volume inside the DSM. I had same problem a couple of weeks ago also doing the same but added 2 disks at the same time. Then I tried following all guides to manually expand the volume and it did worked to expand the volume but the volume was crashed somehow and could not write to the volume all files read only. I had to backup all data again and made a totally new installation. Now again I am at the same situation and added 1 disk and that worked ok but cant be expanding the volume in DSM. Now is my question if anyone have used more than 14 disks in a volume. If so...I am pretty sure it worked to create it and have all capabilities to use the data environment as when you created it, but the problem is that IF a disk crashes you will be able to fix the volume due to expanding not working with so many disks. Even if you typed in 16 as amount of disk in the synoinfo.conf files. Do anyone have got a working system with 14 disks and tried to replaced one disk??? If not then I suggest that I would be for sure super happy if this wonderful system could be added to work with lot of more disks. I guess to start building it on another kernel for the larger Synology stations. I even pay for it. thanks all for all contributing of info and questions that helped me a lot these months....but I have now to start making backup again but I did not move over so much data this time so I will start over again with fewer disks so I get this system up and running and start over when I got response on this question. any tip or trick is wormly appreciated.

Yes I do the copy and backup all before making a huge storage again and test a few things it get live again.

I migrated to the DSM 5.0-4418 today due to other problems but could not fix so that the HBA SAS disk were found. Volume crash. So I returned back to DSM 4.3-3827 and the volume was back as normal again puhh..... I wait until someone tells me that DSM 5.0 works 100% with the major SAS cards and functions. thanks for a good work all that do the builds

After resizing according to the procedure above and even after reboot the system says crashed. Pictures cant be uploaded I do not know why.... Is there anything I can fix this with? I can still reach all data. The Volume is status: Crashed....any tip how to fix this error and get it go away? At this point I have started the data scrubbing and it will take a long time. but that is the only thing I can do before I get more tips. Ok. noone dare to answer...I do now backup all data and make a totally new installation and copy all data back in a fresh environment then it will be perfect and no messing around and test any more. The DSM 5.0 I wait to install due to to early ....for XPEnology version.

Find the solution yesterday....it was easy I needed to totally stop all processes. These are the commands to get the expanding to work....its not ready but at least working fine. Will take a few days. A brief summary of the full procedure is as follows: Be aware that my volume is named "volume_1" your name can be different. Volume Checking and Repair ========================== 1. Telnet to "Your NAS IP" using Putty. 2. Login as "root" 3. Password is same as "admin" account. 4. Turn of all tasks using: syno_poweroff_task Note: Once you perform syno_poweroff_task, it only allows to access through Telnet/SSH. 5. Make all volumes active using: vgchange -ay 6. Do a full check/repair of the file system using: fsck.ext4 -yvf -C 0 /dev/vg1/volume_1 7. Manually expand the volume using: resize2fs -fpF /dev/vg1/volume_1 8. Restart the DS software using: reboot

Nope does not work as I would like to.... lrwxrwxrwx 1 root root 37 Mar 8 09:59 syno_vg_reserved_area -> /dev/mapper/vg1-syno_vg_reserved_area lrwxrwxrwx 1 root root 24 Mar 8 09:59 volume_1 -> /dev/mapper/vg1-volume_1 Nasse> resize2fs -fpF /dev/vg1/volume_1 resize2fs 1.42.6 (21-Sep-2012) resize2fs: Device or resource busy while trying to open /dev/vg1/volume_1 Couldn't find valid filesystem superblock. Nasse> resize2fs /dev/vg1/volume_1 resize2fs 1.42.6 (21-Sep-2012) resize2fs: Device or resource busy while trying to open /dev/vg1/volume_1 Couldn't find valid filesystem superblock. Nasse>

This is the messages in the log I get when trying normally to expand from DSM 4.3. So what I want to do is to resize now by the prompt. But would like to do it the correct way. Is this the correct way to type these commands below or do I need to think about anything else? unmount -f /volume1 e2fsck -f /dev/volume_1 resize2fs /dev/volume_1 Will this work... do I dare to try?

I have read about this problem on the internet and I have kernel majorversion="4" minorversion="3" buildphase="release" buildnumber="3810" smallfixnumber="0" builddate="2013/11/06" Will this mean that I CAN resize in live mode or do I need to dismount volume or whatever and the resize....bla bla. I have no clue how to do this because its linux. But I learn a few steps every day. I would be very appreciated if someone could build a package for this issue that is absolutely needed for XPEsynology builds. I now just have this step left and need full assistance to get this resizing to work without loosing the data. Can someone of you help me out here..private mail can also be sent and later we could add the solution here. Thanks so far for all help. Sit and wait again for response.

I can attach pictures.. not even the smallest ...forum filled up? You can expand size to about 20452 GB. File system Ext4 Status: Normal Capacity: 12.60 TB Used: 12.50 TB Available: 102.24 GB Disk Group Info: Name: Disk Group 1 Allocated: 19.97 TB Unallocated: 1.81 TB Capacity: 21.79 TB Please can you send me the correct resize2fs command string using Usage: resize2fs [-d debug_flags] [-f] [-F] [-M] [-P] [-p] device [new_size] Thanks in advance. Last step now.

Perfect. I have 4.3 So if I manually rezise it should work then? What exact command should I use so it resize correctly? Hope you can help me last chapter of months of building this up. Usage: resize2fs [-d debug_flags] [-f] [-F] [-M] [-P] [-p] device [new_size]

What do you mean? Does it work with DSM 5.0 to expand EXT4 over 16tb or not? Your reply was really obscure. Waiting Before doing the big install.

This version already supports online resize above 16TB. I think there's no need to update it. But a patch is needed to enable this feature in ext4 filesystem. Ok so how do I fix my expanding proble. due to that I am not a linux person Patch...mm how can someone help me out here? Do I need to just apply beta5 and cross my fingers that all data will be intact ?

What is the easiest way to try to expand the ext4 volume like the problem described above with DSM 5? Today I have 4.3 3827 beta7. First I guess I need to get my hands on DSM5 and update ..can't even find the beta 5. Will all settings and data stil be intact? I can not loose the data. I need to try and see if the resize2fs program is updated and working with bigger volumes. /Jimpa

Yes please I am a windows user so I need help here to get a package I can apply to 4.3 3811 beta5.pat or beta7.pat installation. THANKS vasiliy_gr for a fantastic explanation of actually you having exact the same problem. I wait now for someone to help me with a package of code I can apply and in detial desribe how to fix this. I do now even know the linux commands Thanks again /Jimpa

I got a problem that I cannot expand my volume capacity. Even after adding 3 more disks and tried expand again. Only get back to this page all the time. Any hints?

I have the tip after several month of making a big system with lots of disks SHR-2. This is the best parameters added to the rebuild speed parameters. 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 esataportcfg=0x00 (0 ESATA ports) 0111 1111 1111 0000 0000 0000 0000 0000 0000 0000 0000 usbportcfg=0x7FF00000000 (11 USB ports) 0000 0000 0000 0111 1111 1111 1111 1111 1111 1111 1111 internalportcfg=0x7FFFFFFF (31 Internal ports) It works fine to reboot also several times so far with 4.3 3827 Beta7.pat Also maxdisks=20 is needed Important to edit through putty both the synoinfo.conf files then directly type reboot in console and first after that re-login through the webpage. Else the synoinfo.conf file resets to default again and again and again....etc. Really frustrating. Sometimes even get need to migrate system to reach it. But no harm found on files or any settings... So make the synoinfo.conf parameters as high as possible please. Hope to soon see a new build with these settings by default ...perhaps I can also share info how to come around the SSD problem once mounted them faulty to an existing raid ) I testing this right now but all tests take Days. Cu soon /Jimmy

Is there a way to unmount the ssd disks that has -1 degree else there will be problem to have a fucntions system and I need to backup all data first...not funny at all

Hmm... yes I assume this is the tricky thing here....I've tried these stuff but same proble. But no jumpers to change. All new drives after repair.....again goes up as SSD disks all the time....I wonder if it has something to do with that these last 4 ports is JMicron® JMB322. Do you have any drive for these chip in the code that support them...could be a hint to solve it. But then I need hlp to load these drivers if you can find them..... I have added 3 disks to the 4 ports and 2 is always SSD but 1 is ok as HDD.

The thing is now after a week testing again same problem. I have worked with the hexcoding for a long time now. I know how it mainly works. I can only get 12 disk into HDD Manageeent but my biggest issue is that the last 2 is ALWAYS SSD -1 degree. I cant get that away. It has appeared after I did go over 10 disks mounted in the system. Even if I take away one of these disks the last get named as SSD and it cant be allocated as data environment. The hexcoding is correc that I absollutely know now. So now I need to get rid of the SSD and get them as normal SATA disk as they are connected to systemboard SATA ports. Only fealing is that there is named in bios as one chip but physical 2 channels on the board guess..new drivers?

So what could be the correct code for me? I have tried many different hexcode calculations...