Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
I posted a thread last weekend looking for assistance for recovering a missing folder. I incorrectly thought my DNS 323 had changed RAID type, but that was not the case and now I better understand the problem.
I have two identical Seagate 1TB hds, configured using RAID1
Here is a recap as to what happened:
The folder that has disappeared was mounted and being accessed by my laptop. Instead of shutting down the laptop I put it in hibernate.
I also shutdown the DNS using the power button.
Coming back from work, I started up the DNS, then held down the reset button for five seconds, the main power button was flashing.
When the reset was complete, I went to access the DNS via Samba, everything appeared to be there except the one folder that was mounted earlier.
Connecting onto Telnet, I have found the missing folder in two locations and with no content.
The folders that appear fine are located in "/mnt/HD_a2/". My missing directory is located in "/mnt/HD_a4/" & "/mnt/HD_b4/"
I also ran the tool on Telnet to check the condition of the HDs & the consistency of the RAID, nothing to suggest that the RAID has degraded or that one of the HDs has failed. What is worrying is that when looking at the amount of disk space left, is only counted the memory taken by the folders that have not dissappeared.
I have also upgraded the firmware to 1.08.
I have read that I should try using e2fsck, but I have no idea what exactly this does. Could somebody PLEASE PLEASE help, I cannot believe for a second that the missing folder has been deleted/currupted or is irrecoverable - otherwise this is an awful product if folders are destroyed just by trying to reset to factory defaults.
Thanks
Offline
I don't run RAID 1, but on my machine, the main data storage areas are /mnt/HD_a2 and /mnt/HD_b2. /mnt/HD_a4 and /mnt/HD_b4 are reserved disk areas for the firmware. You're not supposed to put anything in there and you certainly should not be sharing them out. I would not be surprised if the firmware reboot code clears out HD_a4 on a reboot. I'm not sure how you got the idea it was ok to use HD_a4. The default shares certainly don't expose it.
And, I'm not even sure how you would have a B disk (/mnt/hd_b4) if in RAID 1. But I've never configured it as RAID 1, so I may be all wet.
Anyway, if I'm right and HD_a2 and HD_a4 are used the same way in RAID and non-RAID, then anything you put in HD_a4 is not for keeps.
Offline
karlrado wrote:
I don't run RAID 1, but on my machine, the main data storage areas are /mnt/HD_a2 and /mnt/HD_b2. /mnt/HD_a4 and /mnt/HD_b4 are reserved disk areas for the firmware. You're not supposed to put anything in there and you certainly should not be sharing them out. I would not be surprised if the firmware reboot code clears out HD_a4 on a reboot. I'm not sure how you got the idea it was ok to use HD_a4. The default shares certainly don't expose it.
And, I'm not even sure how you would have a B disk (/mnt/hd_b4) if in RAID 1. But I've never configured it as RAID 1, so I may be all wet.
Anyway, if I'm right and HD_a2 and HD_a4 are used the same way in RAID and non-RAID, then anything you put in HD_a4 is not for keeps.
Thanks for the insight. I never manually put anything into HD_a2 & HD_a4, the missing folder just appeared there. If you are correct about there being firmware reboot code that clears everything out, then my missing folder has been deleted just by restarting the machine Although the folder itself still appears there, so Im still clutching straws that I have no lost anything.
Offline
OK, I didn't get that the DNS somehow moved the missing (empty) directory from HD_a2 to HD_a4. Very strange.
Offline