vic1707

Members
  • Content Count

    32
  • Joined

  • Last visited

Community Reputation

0 Neutral

About vic1707

  • Rank
    Junior Member
  1. carte réseau realtek et i3 2120 donc mort à jamais ou mort jusqu'à mise à jour ? (le nas est un ancien hp élite 7300 série mt)
  2. tout remarche, j'ai finalament "repare" le nas malgre le message kifépeur et c'est passe j'ai tout recup; malheureusement pas moyen d'installer dsm 6.2.1 en 918+ mon serveur n'apparait pas sur le reseau (visiblement pb courant)
  3. The reinstall works, i can get on the connection page but i can't login with my account, the admin and no password doen't work because admin seems to be disable. find.synology didn't prompt me to configure....
  4. Thank you for your answer. The importance of the data makes me ask the question: I do not think anything as long as I do not click on delete or something like that? You'll laugh, or not believe me so much it's big: 2to disk is my backup disk and I literally format it 8h before the crash of the dsm to change exfat to ntfs on the backup disk and i said to myself "I have time I will put back the backup tomorrow"
  5. So I would like to know if I miss something with Ubuntu? If I install a new DSM on another hard drive and I reconnect the three disks of my volume 1, will it be detected? should I just install a new DSM without worrying about the message that scared me? I just need to recover the data on the raid i don't care of the cofiguration or the systems files.
  6. Hi, First thanks to all of the dev for Xpenology. Secondly sorry for my English, i'm French (i can't find an answer on the french hub), and finally thanks in advance for helping me. So 3 days ago my nas was suddently unaccessible from the net (the gui from synology, plex or jdownloader via docker). I posted about it and the answer was that dsm had made an update and the charger was getting stuck. They said I had to update the loader: I tried it but my NAS was not displayed on the network (and of course unavailable on find.synology). So I tried to reinstall my first charger. Finally, the NAS was displayed with the Repair option. after a reboot, find.synology said i had to reinstall dsm and under this one it was mentioned: "We detected that your current ds3617xs hard drives were removed from a previous ds3617xs and installing a new one dsm is required before continuing "(thanks googletranslate). I was very scared of this and the guy who tried to help me suggest to access the player via Ubuntu. after that i boot on a live ubuntu, install mdadm and lvm2. root@ubuntu:~# mdadm -Asf && vgchange -ay mdadm: /dev/md0 has been started with 3 drives (out of 12). mdadm: /dev/md/2 has been started with 3 drives. mdadm: /dev/md/3 has been started with 3 drives. root@ubuntu:~# fdisk -l | grep /dev/sd Disk /dev/sda: 149.1 GiB, 160041885696 bytes, 312581808 sectors /dev/sda1 2048 4982527 4980480 2.4G fd Linux raid autodetect /dev/sda2 4982528 9176831 4194304 2G fd Linux raid autodetect /dev/sda3 9437184 312376991 302939808 144.5G fd Linux raid autodetect Disk /dev/sdb: 232.9 GiB, 250000000000 bytes, 488281250 sectors /dev/sdb1 2048 4982527 4980480 2.4G fd Linux raid autodetect /dev/sdb2 4982528 9176831 4194304 2G fd Linux raid autodetect /dev/sdb3 9437184 488076447 478639264 228.2G fd Linux raid autodetect Disk /dev/sdc: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors /dev/sdc1 2048 4982527 4980480 2.4G fd Linux raid autodetect /dev/sdc2 4982528 9176831 4194304 2G fd Linux raid autodetect /dev/sdc3 9437184 1953320351 1943883168 926.9G fd Linux raid autodetect Disk /dev/sdd: 465.8 GiB, 500107862016 bytes, 976773168 sectors /dev/sdd1 2048 4982527 4980480 2.4G fd Linux raid autodetect /dev/sdd2 4982528 9176831 4194304 2G fd Linux raid autodetect /dev/sdd3 9437184 976568351 967131168 461.2G fd Linux raid autodetect Disk /dev/sde: 149.1 GiB, 160041885696 bytes, 312581808 sectors /dev/sde1 2048 4982527 4980480 2.4G fd Linux raid autodetect /dev/sde2 4982528 9176831 4194304 2G fd Linux raid autodetect /dev/sde3 9437184 312376991 302939808 144.5G fd Linux raid autodetect Disk /dev/sdf: 232.9 GiB, 250000000000 bytes, 488281250 sectors /dev/sdf1 2048 4982527 4980480 2.4G fd Linux raid autodetect /dev/sdf2 4982528 9176831 4194304 2G fd Linux raid autodetect /dev/sdf3 9437184 488076447 478639264 228.2G fd Linux raid autodetect Disk /dev/sdg: 7.6 GiB, 8178892800 bytes, 15974400 sectors /dev/sdg1 * 2048 15974399 15972352 7.6G c W95 FAT32 (LBA) Disk /dev/sdh: 1.8 TiB, 2000365289472 bytes, 3906963456 sectors /dev/sdh1 256 3906959804 3906959549 1.8T b W95 FAT32 I see this, drives g and h are the live ubuntu and an external hard drive. after this i have access to /dev/md0 wich seems to be the system partition, and access to /dev/md/3 which is my second volume partition. /dev/md/2 is unaccessible on the files app with this message : Error mounting /dev/md2 at /media/ubuntu/2019.01.08-17:38:26v15217: wrong fs type, badsuperblok on /dev/md2, missing codepage or helper program, or other error so i tryed the others commands to mount it ( drives b,c and d are my first raid with volume1 and system partition) the only partitons of these drives with superblocks are the second ones. root@ubuntu:~# mdadm -Ee0.swap /dev/sdb2 /dev/sdc2 /dev/sdd2 /dev/sdb2: Magic : a92b4efc Version : 0.90.00 UUID : 616f70ec:fe0b3da8:8d2eb468:7e40dd84 Creation Time : Tue Jan 8 17:03:35 2019 Raid Level : raid1 Used Dev Size : 2097088 (2047.94 MiB 2147.42 MB) Array Size : 2097088 (2047.94 MiB 2147.42 MB) Raid Devices : 12 Total Devices : 6 Preferred Minor : 1 Update Time : Mon Jan 21 18:44:35 2019 State : clean Active Devices : 6 Working Devices : 6 Failed Devices : 6 Spare Devices : 0 Checksum : ccb07e32 - correct Events : 162 Number Major Minor RaidDevice State this 5 8 18 5 active sync /dev/sdb2 0 0 8 34 0 active sync /dev/sdc2 1 1 8 66 1 active sync /dev/sde2 2 2 8 50 2 active sync /dev/sdd2 3 3 8 2 3 active sync /dev/sda2 4 4 8 82 4 active sync /dev/sdf2 5 5 8 18 5 active sync /dev/sdb2 6 6 0 0 6 faulty removed 7 7 0 0 7 faulty removed 8 8 0 0 8 faulty removed 9 9 0 0 9 faulty removed 10 10 0 0 10 faulty removed 11 11 0 0 11 faulty removed /dev/sdc2: Magic : a92b4efc Version : 0.90.00 UUID : 616f70ec:fe0b3da8:8d2eb468:7e40dd84 Creation Time : Tue Jan 8 17:03:35 2019 Raid Level : raid1 Used Dev Size : 2097088 (2047.94 MiB 2147.42 MB) Array Size : 2097088 (2047.94 MiB 2147.42 MB) Raid Devices : 12 Total Devices : 6 Preferred Minor : 1 Update Time : Mon Jan 21 18:44:35 2019 State : clean Active Devices : 6 Working Devices : 6 Failed Devices : 6 Spare Devices : 0 Checksum : ccb07e4c - correct Events : 162 Number Major Minor RaidDevice State this 2 8 50 2 active sync /dev/sdd2 0 0 8 34 0 active sync /dev/sdc2 1 1 8 66 1 active sync /dev/sde2 2 2 8 50 2 active sync /dev/sdd2 3 3 8 2 3 active sync /dev/sda2 4 4 8 82 4 active sync /dev/sdf2 5 5 8 18 5 active sync /dev/sdb2 6 6 0 0 6 faulty removed 7 7 0 0 7 faulty removed 8 8 0 0 8 faulty removed 9 9 0 0 9 faulty removed 10 10 0 0 10 faulty removed 11 11 0 0 11 faulty removed /dev/sdd2: Magic : a92b4efc Version : 0.90.00 UUID : 616f70ec:fe0b3da8:8d2eb468:7e40dd84 Creation Time : Tue Jan 8 17:03:35 2019 Raid Level : raid1 Used Dev Size : 2097088 (2047.94 MiB 2147.42 MB) Array Size : 2097088 (2047.94 MiB 2147.42 MB) Raid Devices : 12 Total Devices : 6 Preferred Minor : 1 Update Time : Mon Jan 21 18:44:35 2019 State : clean Active Devices : 6 Working Devices : 6 Failed Devices : 6 Spare Devices : 0 Checksum : ccb07e38 - correct Events : 162 Number Major Minor RaidDevice State this 0 8 34 0 active sync /dev/sdc2 0 0 8 34 0 active sync /dev/sdc2 1 1 8 66 1 active sync /dev/sde2 2 2 8 50 2 active sync /dev/sdd2 3 3 8 2 3 active sync /dev/sda2 4 4 8 82 4 active sync /dev/sdf2 5 5 8 18 5 active sync /dev/sdb2 6 6 0 0 6 faulty removed 7 7 0 0 7 faulty removed 8 8 0 0 8 faulty removed 9 9 0 0 9 faulty removed 10 10 0 0 10 faulty removed 11 11 0 0 11 faulty removed root@ubuntu:~# mdadm -AU byteorder /dev/md0 /dev/sdb2 /dev/sdc2 /dev/sdd2 mdadm: /dev/sdb2 is busy - skipping mdadm: /dev/sdc2 is busy - skipping mdadm: /dev/sdd2 is busy - skipping root@ubuntu:~# then i get this. I really don't know what to do to recover those data. Please help me!
  7. root@ubuntu:~# mdadm -Ee0.swap /dev/sdb2 /dev/sdc2 /dev/sdd2 /dev/sdb2: Magic : a92b4efc Version : 0.90.00 UUID : 616f70ec:fe0b3da8:8d2eb468:7e40dd84 Creation Time : Tue Jan 8 17:03:35 2019 Raid Level : raid1 Used Dev Size : 2097088 (2047.94 MiB 2147.42 MB) Array Size : 2097088 (2047.94 MiB 2147.42 MB) Raid Devices : 12 Total Devices : 6 Preferred Minor : 1 Update Time : Mon Jan 21 18:44:35 2019 State : clean Active Devices : 6 Working Devices : 6 Failed Devices : 6 Spare Devices : 0 Checksum : ccb07e32 - correct Events : 162 Number Major Minor RaidDevice State this 5 8 18 5 active sync /dev/sdb2 0 0 8 34 0 active sync /dev/sdc2 1 1 8 66 1 active sync /dev/sde2 2 2 8 50 2 active sync /dev/sdd2 3 3 8 2 3 active sync /dev/sda2 4 4 8 82 4 active sync /dev/sdf2 5 5 8 18 5 active sync /dev/sdb2 6 6 0 0 6 faulty removed 7 7 0 0 7 faulty removed 8 8 0 0 8 faulty removed 9 9 0 0 9 faulty removed 10 10 0 0 10 faulty removed 11 11 0 0 11 faulty removed /dev/sdc2: Magic : a92b4efc Version : 0.90.00 UUID : 616f70ec:fe0b3da8:8d2eb468:7e40dd84 Creation Time : Tue Jan 8 17:03:35 2019 Raid Level : raid1 Used Dev Size : 2097088 (2047.94 MiB 2147.42 MB) Array Size : 2097088 (2047.94 MiB 2147.42 MB) Raid Devices : 12 Total Devices : 6 Preferred Minor : 1 Update Time : Mon Jan 21 18:44:35 2019 State : clean Active Devices : 6 Working Devices : 6 Failed Devices : 6 Spare Devices : 0 Checksum : ccb07e4c - correct Events : 162 Number Major Minor RaidDevice State this 2 8 50 2 active sync /dev/sdd2 0 0 8 34 0 active sync /dev/sdc2 1 1 8 66 1 active sync /dev/sde2 2 2 8 50 2 active sync /dev/sdd2 3 3 8 2 3 active sync /dev/sda2 4 4 8 82 4 active sync /dev/sdf2 5 5 8 18 5 active sync /dev/sdb2 6 6 0 0 6 faulty removed 7 7 0 0 7 faulty removed 8 8 0 0 8 faulty removed 9 9 0 0 9 faulty removed 10 10 0 0 10 faulty removed 11 11 0 0 11 faulty removed /dev/sdd2: Magic : a92b4efc Version : 0.90.00 UUID : 616f70ec:fe0b3da8:8d2eb468:7e40dd84 Creation Time : Tue Jan 8 17:03:35 2019 Raid Level : raid1 Used Dev Size : 2097088 (2047.94 MiB 2147.42 MB) Array Size : 2097088 (2047.94 MiB 2147.42 MB) Raid Devices : 12 Total Devices : 6 Preferred Minor : 1 Update Time : Mon Jan 21 18:44:35 2019 State : clean Active Devices : 6 Working Devices : 6 Failed Devices : 6 Spare Devices : 0 Checksum : ccb07e38 - correct Events : 162 Number Major Minor RaidDevice State this 0 8 34 0 active sync /dev/sdc2 0 0 8 34 0 active sync /dev/sdc2 1 1 8 66 1 active sync /dev/sde2 2 2 8 50 2 active sync /dev/sdd2 3 3 8 2 3 active sync /dev/sda2 4 4 8 82 4 active sync /dev/sdf2 5 5 8 18 5 active sync /dev/sdb2 6 6 0 0 6 faulty removed 7 7 0 0 7 faulty removed 8 8 0 0 8 faulty removed 9 9 0 0 9 faulty removed 10 10 0 0 10 faulty removed 11 11 0 0 11 faulty removed root@ubuntu:~# mdadm -AU byteorder /dev/md0 /dev/sdb2 /dev/sdc2 /dev/sdd2 mdadm: /dev/sdb2 is busy - skipping mdadm: /dev/sdc2 is busy - skipping mdadm: /dev/sdd2 is busy - skipping root@ubuntu:~# voila ce que j'ai une fois les bonnes commandes entrées
  8. j'ai le droit a cette erreur pour md2 une fois le "mdadm -Asf && vgchange -ay" executé; Error mounting /dev/md2 at /media/ubuntu/2019.01.08-17:38:26v15217: wrong fs type, badsuperblok on /dev/md2, missing codepage or helper program, or other error
  9. au final je n'ai acces qu'a /dev/md0 donc la config; /dev/md/3 qui contient une petite partie de mes données mais impossible d'acceder à /dev/md/2 qui contient 80% des data. le volume md/2 semble monté car apparait dnas "other devices" sur le gestionnaire de fichiers mais affiche une erreur que je n'ai malheureusement pas noté mais que je pourrais te transmettre ce soir. En attendant si quelqu'un a une idée...
  10. je me suis rendu compte de mon erreur, il manquais /dev/md0. root@ubuntu:~# mdadm -Ee0.swap /dev/sdb2 /dev/sdc2 /dev/sdd2 /dev/sdb2: Magic : a92b4efc Version : 0.90.00 UUID : 616f70ec:fe0b3da8:8d2eb468:7e40dd84 Creation Time : Tue Jan 8 17:03:35 2019 Raid Level : raid1 Used Dev Size : 2097088 (2047.94 MiB 2147.42 MB) Array Size : 2097088 (2047.94 MiB 2147.42 MB) Raid Devices : 12 Total Devices : 6 Preferred Minor : 1 Update Time : Mon Jan 21 18:44:35 2019 State : clean Active Devices : 6 Working Devices : 6 Failed Devices : 6 Spare Devices : 0 Checksum : ccb07e32 - correct Events : 162 Number Major Minor RaidDevice State this 5 8 18 5 active sync /dev/sdb2 0 0 8 34 0 active sync /dev/sdc2 1 1 8 66 1 active sync /dev/sde2 2 2 8 50 2 active sync /dev/sdd2 3 3 8 2 3 active sync /dev/sda2 4 4 8 82 4 active sync /dev/sdf2 5 5 8 18 5 active sync /dev/sdb2 6 6 0 0 6 faulty removed 7 7 0 0 7 faulty removed 8 8 0 0 8 faulty removed 9 9 0 0 9 faulty removed 10 10 0 0 10 faulty removed 11 11 0 0 11 faulty removed /dev/sdc2: Magic : a92b4efc Version : 0.90.00 UUID : 616f70ec:fe0b3da8:8d2eb468:7e40dd84 Creation Time : Tue Jan 8 17:03:35 2019 Raid Level : raid1 Used Dev Size : 2097088 (2047.94 MiB 2147.42 MB) Array Size : 2097088 (2047.94 MiB 2147.42 MB) Raid Devices : 12 Total Devices : 6 Preferred Minor : 1 Update Time : Mon Jan 21 18:44:35 2019 State : clean Active Devices : 6 Working Devices : 6 Failed Devices : 6 Spare Devices : 0 Checksum : ccb07e4c - correct Events : 162 Number Major Minor RaidDevice State this 2 8 50 2 active sync /dev/sdd2 0 0 8 34 0 active sync /dev/sdc2 1 1 8 66 1 active sync /dev/sde2 2 2 8 50 2 active sync /dev/sdd2 3 3 8 2 3 active sync /dev/sda2 4 4 8 82 4 active sync /dev/sdf2 5 5 8 18 5 active sync /dev/sdb2 6 6 0 0 6 faulty removed 7 7 0 0 7 faulty removed 8 8 0 0 8 faulty removed 9 9 0 0 9 faulty removed 10 10 0 0 10 faulty removed 11 11 0 0 11 faulty removed /dev/sdd2: Magic : a92b4efc Version : 0.90.00 UUID : 616f70ec:fe0b3da8:8d2eb468:7e40dd84 Creation Time : Tue Jan 8 17:03:35 2019 Raid Level : raid1 Used Dev Size : 2097088 (2047.94 MiB 2147.42 MB) Array Size : 2097088 (2047.94 MiB 2147.42 MB) Raid Devices : 12 Total Devices : 6 Preferred Minor : 1 Update Time : Mon Jan 21 18:44:35 2019 State : clean Active Devices : 6 Working Devices : 6 Failed Devices : 6 Spare Devices : 0 Checksum : ccb07e38 - correct Events : 162 Number Major Minor RaidDevice State this 0 8 34 0 active sync /dev/sdc2 0 0 8 34 0 active sync /dev/sdc2 1 1 8 66 1 active sync /dev/sde2 2 2 8 50 2 active sync /dev/sdd2 3 3 8 2 3 active sync /dev/sda2 4 4 8 82 4 active sync /dev/sdf2 5 5 8 18 5 active sync /dev/sdb2 6 6 0 0 6 faulty removed 7 7 0 0 7 faulty removed 8 8 0 0 8 faulty removed 9 9 0 0 9 faulty removed 10 10 0 0 10 faulty removed 11 11 0 0 11 faulty removed root@ubuntu:~# mdadm -AU byteorder /dev/md0 /dev/sdb2 /dev/sdc2 /dev/sdd2 mdadm: /dev/sdb2 is busy - skipping mdadm: /dev/sdc2 is busy - skipping mdadm: /dev/sdd2 is busy - skipping mais maintenant j'ai ca et je bloque une idée?
  11. avec gparted j'ai trouvé que les disk concerné etait vraissembleblement b,c,d grace au label dans gparted. les seuls superblock trouvable sont en 2 root@ubuntu:~# mdadm -AU byteorder /dev/sdb2 /dev/sdc2 /dev/sdd2 mdadm: device /dev/sdb2 exists but is not an md array. mais voila ce que j'obtient peut importe l'ordre de b,c,d.
  12. je précise que seul 6 disques sont branché, deux de 250Go, deux en 160Go, un 1to et un de 500Go Edit : autant pour moi je suis un abruti, un hdd externe de 2To et Ubuntu est sur une clé de 8Go ce qui explique les deux disques "en trop"
  13. root@ubuntu:~# mdadm -Asf && vgchange -ay mdadm: /dev/md0 has been started with 3 drives (out of 12). mdadm: /dev/md/2 has been started with 3 drives. mdadm: /dev/md/3 has been started with 3 drives. la j'ai acces au systeme md0, ainsi qu'a md3 mais pas md2. root@ubuntu:~# fdisk -l | grep /dev/sd Disk /dev/sda: 149.1 GiB, 160041885696 bytes, 312581808 sectors /dev/sda1 2048 4982527 4980480 2.4G fd Linux raid autodetect /dev/sda2 4982528 9176831 4194304 2G fd Linux raid autodetect /dev/sda3 9437184 312376991 302939808 144.5G fd Linux raid autodetect Disk /dev/sdb: 232.9 GiB, 250000000000 bytes, 488281250 sectors /dev/sdb1 2048 4982527 4980480 2.4G fd Linux raid autodetect /dev/sdb2 4982528 9176831 4194304 2G fd Linux raid autodetect /dev/sdb3 9437184 488076447 478639264 228.2G fd Linux raid autodetect Disk /dev/sdc: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors /dev/sdc1 2048 4982527 4980480 2.4G fd Linux raid autodetect /dev/sdc2 4982528 9176831 4194304 2G fd Linux raid autodetect /dev/sdc3 9437184 1953320351 1943883168 926.9G fd Linux raid autodetect Disk /dev/sdd: 465.8 GiB, 500107862016 bytes, 976773168 sectors /dev/sdd1 2048 4982527 4980480 2.4G fd Linux raid autodetect /dev/sdd2 4982528 9176831 4194304 2G fd Linux raid autodetect /dev/sdd3 9437184 976568351 967131168 461.2G fd Linux raid autodetect Disk /dev/sde: 149.1 GiB, 160041885696 bytes, 312581808 sectors /dev/sde1 2048 4982527 4980480 2.4G fd Linux raid autodetect /dev/sde2 4982528 9176831 4194304 2G fd Linux raid autodetect /dev/sde3 9437184 312376991 302939808 144.5G fd Linux raid autodetect Disk /dev/sdf: 232.9 GiB, 250000000000 bytes, 488281250 sectors /dev/sdf1 2048 4982527 4980480 2.4G fd Linux raid autodetect /dev/sdf2 4982528 9176831 4194304 2G fd Linux raid autodetect /dev/sdf3 9437184 488076447 478639264 228.2G fd Linux raid autodetect Disk /dev/sdg: 7.6 GiB, 8178892800 bytes, 15974400 sectors /dev/sdg1 * 2048 15974399 15972352 7.6G c W95 FAT32 (LBA) Disk /dev/sdh: 1.8 TiB, 2000365289472 bytes, 3906963456 sectors /dev/sdh1 256 3906959804 3906959549 1.8T b W95 FAT32 Ensuite j'ai le droit à ca. mais la incapable de dire qui est qui. je sais que le dd de 1to et de 500go font partie du volume 1 ainsi qu'un de 250 mais lequel? J'ai tenté de branché seulement le volume 1 mais rien ne vas je me dis donc que je dois tout brancher. Une idée apres ca de la commande a entrer (plus precisement des volumes a integrer)?