jbesclapez

Members
  • Content Count

    174
  • Joined

  • Last visited

Community Reputation

0 Neutral

About jbesclapez

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi Bearcat, Yes I did OPEN the drive and moved an head. The other drive is not even responding. Maybe a board issue. NO idea. I was doing a new back up of the file but could not recover the overall... That is why i decided to open the noisy drive.... I am going to ddrescue the drive on another computer using clonezilla.... and work on the image...
  2. OMG!!!! It was a RAID1 I all guided you to the wrong thing. I am really sorry. AS you can see on the cat /proc/mdstat (so pissed of with myself) However, by kind of luck i recovered some data. The synobox was sitting on the side of my desk... (you wont believe that) and my cat came in. Then my son came in and scared the cat, who pushed the syno to the ground. The second disks started to make some noise....RRRR.... I opened it... to move back the head of the drive. Now my syno is not making noise but it is discovered as a NOT INSTALLED. However, i can s
  3. Thanks IG-88 (again, and again I opened the box yesterday and could not hear the second disk spinning. I need to investigate on how to make it spin again. The only thing it did was unplug the power cord, while DSM was on...
  4. Hi there, I have an old DS2017+ that is running on DSM3.1 and my volume just crashed. I was using this NAS as a back up of my already broken XPEnology. I need to recover those data. It happened when I unplugged the power cord by accident... Even if i was not writting thinds on the NAS. I do not see the other drive I think... Please help Thanks BackUpStation> cat /proc/mdstat Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] md2 : active raid1 sdb5[1](E) 385977472 blocks super 1.2 [2/1] [_E] md1 : act
  5. Hello Flyride, It took me some time to do the DD Raw back up of the drives. I had to redo it 2 times!! I also did a back up of the raw image. I also installed a VM machine with Ubuntu on it and I created a shared folder that can access the DD image from Ubuntu. Now I think I am ready to do the e2fsck you mentioned. I was also thinking that, we totally never worked with the 4th drive. We never touched it... maybe we should try something with it? Can you guide me on the e2fsck command like you did before? Thanks
  6. Flyride, I just got myself a 10Tb drive delivered. I am now using Clonezilla to make a raw image of the drives... I think it might take 1 to 2 days. I will keep you posted on this! I cant wait for the week end ;-)
  7. IG-88 and Flyride, I totally agree with both of you guys! First I will clone my drive - I just got myself a 10Tb drive and a USB 3.1 docking sata station. That should do the job right in terms of hardware. I will do some research in the coming days on how to clone my array onto DSK or IMG files. I will then compress those and put them on the 8Tb drive. I will use the 10Tb to do my research/tests. Once again, remember I realised this morning that my most precious data is saved. I am not trying to recover the rest, but if it fails I will be kind of fine - mainly frustrated
  8. Supermounter, what I could do also is to create a VM and put DSM on it and then attach the real disks to it no? However, I will wait for Flyride!
  9. I see things a bit differently. I think I have everything to loose. I think everything can be forecasted and planned. There is no maybe. I was simply really stupid to use the GUI yesterday! And as Flyride said, it should have been avoided if I did not miread/got confused. I am not ready to change anything without having at least a RAW backup of the disks. I am waiting for my guru to reply
  10. Hi Supermounter! With all due respect, I do not really see the point in that as the array is arlready seen by my DSM if you look at the print screens. The filesystem will not recover on its own...
  11. Good morning Flyride! I had a tough night to be honest, I was thinking of my mistake. All this comes from a big misundertanding from my side ! I did some reading like you recommended and I also contacted a FORENSIC to ask for a quote with all the details you gave me. Then I did more reading to see what i could do. Now I need your opinion, as once again, I might misundertand things I was thinking of doing a RAW copy of the drives and then some analysis. I will have to buy a new drive - but anyway I was thinking of upgrading my NAS as it is pretty old, so the d
  12. I cant believe it! we were so close and yet now so far! I totally ******* up by using GUI! I will do some reading and give it a bit of time. I need to look at my other back ups to see what I lost exactly, but I am not ready to go to Forensic as it is too expensive I think! Thanks for your time , I will come back to you!
  13. root@DiskStation:~# mount -t ext4 -v -o ro,noload,sb=644972544 /dev/vg1000/lv /volume1 mount: wrong fs type, bad option, bad superblock on /dev/vg1000/lv, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so. root@DiskStation:~# dmesg | tail [ 3740.204044] hub 7-0:1.0: port 2 disabled by hub (EMI?), re-enabling... [ 3740.210578] usb 7-2: USB disconnect, device number 4 [ 3740.695011] usb 7-2: new low-speed USB device number 5 using uhci_hcd [ 3740.881327] Got empty serial number. Generate serial number fr
  14. Flyride, I am not touching an USB. I am not touching the server basically. I do not really understand what you ask me to do with the msg on the mount operation?