Buffalo Forums

Products => Storage => Topic started by: LincolnAbe on April 23, 2016, 08:24:59 AM

Title: How to repair hd errors by an fsck type command?
Post by: LincolnAbe on April 23, 2016, 08:24:59 AM
I have some moderately severe HD errors in my 2TB LS-CHL LinkStation, which stops some files from being read. The red error lamp flashes (as I can see) two long and a short, which as I've understood means hd error & back up data & replace unit.

Before buying a new NAS device I would like to do fsck (scandisk/chkdsk) repair from my MacOSX to mark sectors that are bad on the hd. I've tried using the web based config panel at 192.168.1.2 at System > Storage > Check Disk. The problem is, every time the check tilts and stops after a few minutes when the browser gives the error message: "Failed to operate disk. Please resubmit after restart".

After logging in again and restarting the unit, the blue solid LED are on, but only until the next time I happen to read a corrupted file, when red LED starts flashing again. Thus, whatever the Check Disk function does, it's not fixing the problem.

I would like to try to repair the hd by using a terminal type command, such as fsck from my MacOSX. Is there a possibility and how do you do this?
Title: Re: How to repair hd errors by an fsck type command?
Post by: Eastmarch on April 24, 2016, 11:19:38 AM
The Linux filesystem does this automagically. If it isn't readable now, then the file is likely lost, short of professional data recovery.

We have a relationship with DriveSavers that involves a discount, and they will do a completely free assessment, including all shipping if the files are not backed up or recreatable.

DriveSavers (http://www.drivesaversdatarecovery.com/welcome/welcome-buffalo-technology-customers/)
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: 54 (show)
Files included: 27 - 1055KB. (show)
Memory used: 719KB.
Tokens: post-login.
Queries used: 14.

[Show Queries]