deva1983

Members
  • Posts

    30
  • Joined

  • Last visited

Everything posted by deva1983

  1. I'm also interested in getting this solved/hidden ...
  2. Hi, I already knew about photorec, but on the info page it states:
  3. I added (and shared) an internal disk with ext3 FS. However, the drive is mounted RO. Why is that ? How can I change it to rw ? Thanks !
  4. Sorry to bump this thread ... Is there any other thing I can try to retrieve some of the data, or should I consider it a total loss ?
  5. md1 log attached. Anything else I can try ? syslog.txt
  6. Hi, I want to preclear a used WD10EADS on unraid 4.7. Should I be using the -A or -a option ? Gr, Deva Edit: no jumper installed
  7. Is there anything else I can try, or have I ran out of options ?
  8. rebuild md1. stop/start array. I guess I am fsck'ed ?
  9. Hi, Did a rebuild-sd and a check. Check failed on the disk I think is the parity disk Afterwards I stopped the array and reboot. Syslog attached. Drives still are shown as unformatted. syslog.txt
  10. Ok. So I'll do a --rebuild-sb on the 2 2TB disks. How do I get rid of the invalid configuration, because I need to have /dev/mdX available. I presume the array has to be down
  11. Well, the complete story: I started with 2 disks, then early last week I purchased an extra SATA controller and disk (1GB). Installed both, cleared the disk and added it to the array. Everything OK. However, yesterday I was experiencing slow read speeds (8 MB/s compaired to 30 the week before), so I suspected the new controller gave conflicts. I removed the controller (and disk), which (in ESXI) also changed the address of my other (onboard) controller ... Re-passed-through the onboard controller, re-assigned the disks in unraid and started the array with 1 disk missing (the one of 1TB). However, the slow speeds remained, so I reseated the PCIx SATA controller and disk. The address of the onboard controller changed again, so I had to re-assign them both again to unRAID. Then the shit hit the fan, and it detected unformatted disks (which might have occurred after a parity sync (which I aborted quickly)?)... Now it looks like it confused the previous parity disk with disk1...
  12. Thanks for all your help you ! As I searched the forums, I also noticed that i missed the REISER part in the dd. I'm pretty sure (99%) which is the parity disk (as I took the fastest drive), but what if I am mistaken ? A rebuild-sb would destroy the parity I suppose ? Is there any way to make sure which is the parity disk ? I'll try your instructions tonight. Thanks again !
  13. I believe disk sdd and sda to by my data disks (sda being empty). dd sda: dd sdd sdc ('presumed' parity) fdisk sda: fdisk sdd fdisk sdc ('presumed' parity)
  14. BTW, if I unassign the parity disk, and assign the disks it 'expects' to disk1 and 2, I get 2 unformatted drives. EDIT: removed disks and inserted in another PC, but was unable to mount all 3 of them :'( syslog.txt