hi
I have a Buffalo 1TB External hard for 3 months now. recently i have noticed it makes a continuous clicking noise on pc startup. today I needed a file from the drive. I tried to enter my password and connect. It accepts my password but there is no drive letter (used to be G:) on my computer letting me to connect to the device. on my windows 7 Devises and Printers , I can see HD-LXU3 is listed and all the drivers/hardware settings show the device working properly, but no luck for me to get connected.
Please help.
Have you tried reassigning the drive letter in Disk management or at least trying it on a second PC?
Yes, There is no device in the Disk Management for it. however I can see a DISK 3, unknown, not initialised of 3GB listed there which is unallocated. when I unistalled it, it removed HD-LXU3 from devices and printers list which then When I reconnected it to the USB port the driver was successfully installed and again it appeared as disk 3 as unknown in the Disk Management.
on another pc the story is similar. the driver is installed successfully but the status is 'not connected'!
please help....
Then reallocate the partition in disk management.
when I try to initialise the disk, I choose MBR, but then Virtual Disk Manager returns with error: The request could not be performed because of an I/O device error.
Hi, yes, it is faulty and they have asked me to send it to the retailer for a replacement. but I am worried that by sending back the device I am handing over all my private data to the retailer and then to Buffalo as well. I will be worried that my private files may be restored by unauthorised people. My question is would it be possible for the company to get access to my data technically, if they want to? or because it has been encoded with a password using AES-256, it is impossible to decode the data?
Has it really encoded the whole data in AES just before writing them onto the device?
Please advise....
If you encoded the whole drive with 256bit, then even a data recovery company would not be able to recover the data without the password. Besides, when product is sent back to Buffalotech, the first step we do is remove all drives and zero-wipe them. It's illegal and unethical, to allow our employees to be exposed to customer data.
Well, this is what I want to make sure. The device was condigured to have a password. I mean every time I wanted to connect to the device I had to enter my password. Now apart from the ethical issues, I wanted to know if it is possible for the company or a third party to get around this and restore data.
I've talked with DriveSavers (one of the most experienced data recovery companies in the business) and they stated they could recover 1s and 0s from an encrypted drive, but the data would be meaningless without the password.
Browser ID: smf
(is_webkit)
Templates: 1:
Printpage (default).
Sub templates: 4:
init,
print_above,
main,
print_below.
Language files: 1:
index+Modifications.english (default).
Style sheets: 0:
.
Hooks called: 90 (
showintegrate_autoload, integrate_pre_load, integrate_load_session, integrate_verify_user, integrate_pre_load_theme, integrate_user_info, integrate_load_board, integrate_board_info, integrate_pre_load_theme, integrate_allowed_to_general, integrate_simple_actions, integrate_allowed_to_general, integrate_load_theme, integrate_pre_log_stats, integrate_actions, integrate_word_censor, integrate_word_censor, integrate_pre_parsebbc, integrate_bbc_codes, integrate_bbc_print, integrate_post_parsebbc, integrate_word_censor, integrate_word_censor, integrate_pre_parsebbc, integrate_bbc_print, integrate_post_parsebbc, integrate_word_censor, integrate_word_censor, integrate_pre_parsebbc, integrate_bbc_print, integrate_post_parsebbc, integrate_word_censor, integrate_word_censor, integrate_pre_parsebbc, integrate_bbc_print, integrate_post_parsebbc, integrate_word_censor, integrate_word_censor, integrate_pre_parsebbc, integrate_bbc_print, integrate_post_parsebbc, integrate_word_censor, integrate_word_censor, integrate_pre_parsebbc, integrate_bbc_print, integrate_post_parsebbc, integrate_word_censor, integrate_word_censor, integrate_pre_parsebbc, integrate_bbc_print, integrate_post_parsebbc, integrate_word_censor, integrate_word_censor, integrate_pre_parsebbc, integrate_bbc_print, integrate_post_parsebbc, integrate_word_censor, integrate_word_censor, integrate_pre_parsebbc, integrate_bbc_print, integrate_post_parsebbc, integrate_word_censor, integrate_word_censor, integrate_pre_parsebbc, integrate_bbc_print, integrate_post_parsebbc, integrate_pre_parsebbc, integrate_smileys, integrate_smileys, integrate_post_parsebbc, integrate_pre_parsebbc, integrate_smileys, integrate_smileys, integrate_post_parsebbc, integrate_allowed_to_general, integrate_allowed_to_general, integrate_allowed_to_general, integrate_allowed_to_general, integrate_allowed_to_general, integrate_allowed_to_general, integrate_allowed_to_general, integrate_allowed_to_general, integrate_allowed_to_general, integrate_allowed_to_general, integrate_menu_buttons, integrate_current_action, integrate_theme_context, integrate_allowed_to_general, integrate_allowed_to_general, integrate_allowed_to_general)
Files included: 27 - 1055KB. (
show./index.php, ./Settings.php, (Cache)/db_last_error.php, (Sources)/QueryString.php, (Sources)/Subs.php, (Sources)/Subs-Auth.php, (Sources)/Errors.php, (Sources)/Load.php, (Sources)/Security.php, (Sources)/Subs-Compat.php, (Sources)/Subs-Db-mysql.php, (Sources)/Cache/CacheApi.php, (Sources)/Cache/CacheApiInterface.php, (Sources)/StopForumSpam.php, (Sources)/Subs-Charset.php, (Sources)/Unicode/Metadata.php, (Sources)/Unicode/QuickCheck.php, (Sources)/Session.php, (Sources)/Logging.php, (Sources)/Class-BrowserDetect.php, (Sources)/Unicode/RegularExpressions.php, (Sources)/Unicode/CaseUpper.php, (Sources)/Unicode/CaseTitle.php, (Current Theme)/languages/index.english.php, (Current Theme)/languages/Modifications.english.php, (Sources)/Printpage.php, (Current Theme)/Printpage.template.php)
Memory used: 735KB.
Tokens:
post-login.
Queries used: 10.
[Show Queries]