Buffalo NAS-Central Forums

Welcome to the Linkstation Wiki community
It is currently Mon Jun 18, 2018 6:25 am

All times are UTC+01:00




Post new topic  Reply to topic  [ 9 posts ] 
Author Message
PostPosted: Sat Jun 11, 2016 6:21 pm 
Offline
Newbie

Joined: Thu Jul 12, 2007 10:08 pm
Posts: 24
I have been dealing with a data recovery issue on a 2.0TB LS-VL. Apologies if this is mentioned elsewhere, but the search function ignores i11...

I recently removed the drive, in order to effect a file undelete. Somewhere along the way, the main data partition seems to have lost its partition type.

On booting, the device now flashes one long Red flash, followed by one short red flash. Google tells me this is error i11 and that it means my drive has too many bad sectors (or similar). Upon sticking the drive in an eSATA cradle under Windows, HDD Guardian tells me the SMART stats are perfect for the drive - no sector errors, no ATA errors, no errors at all.

Using MiniTool Partition Wizard, I see the following partitions:
EXT3 977MB
Ext3 4.8GB
Unformatted 1MB
Unformatted 1MB
Linux Swap 977MB
OTHER 1848.5Gb
Unallocated 7.8GB

My data partition would appear to be the one now listed as type OTHER, with 100.0% of the drive used (hoping that's just because windows doesn't know how to read it).

My first guess would be to try and use RANISH partition manager or a Linux live CD to boot my PC and edit the partition type. THIS IS A STOCK UNMODIFIED LINKSTATION: what partition type does the data partition use from the factory - XFS or EXT3?

Can anyone confirm my recovery methodology is sound, and either suggest a windows based tool to set the partition type, or confirm a distro with the right tool.

Many thanks in advance for any help


Top
   
PostPosted: Sat Jun 11, 2016 9:36 pm 
Offline
Moderator

Joined: Mon Apr 26, 2010 10:24 am
Posts: 2730
XFS

! your partition is
Quote:
OTHER 1848.5Gb


Other means your environment is not able to handle xfs

try 4. from
http://forum.nas-hilfe.de/buffalo-technology-nas-anleitungen/blaues-blinken-datenrettung-von-einer-durch-stromausfall-nicht-mehr-ansprechbaren-ls-chlv2-t1849.html


Top
   
PostPosted: Wed Jun 15, 2016 10:49 pm 
Offline
Newbie

Joined: Thu Jul 12, 2007 10:08 pm
Posts: 24
oxygen8 wrote:


Apologies for the delay in following up. Results as follows:

With the latest version of Knoppix (7.6.1) I did not need to install the XFSprogs or smartmontools (item 6) as they were already present.

I already knew that my device was error free, but I ran the same checks (item 7)
Code:
root@Microknoppix:~# smartctl -A /dev/sdb
smartctl 6.4 2015-06-04 r4109 [x86_64-linux-4.2.6-64] (local build)
Copyright (C) 2002-15, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   200   200   051    Pre-fail  Always       -       1
  3 Spin_Up_Time            0x0027   170   169   021    Pre-fail  Always       -       6475
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       29
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   200   200   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   054   054   000    Old_age   Always       -       33679
 10 Spin_Retry_Count        0x0032   100   253   000    Old_age   Always       -       0
 11 Calibration_Retry_Count 0x0032   100   253   000    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       26
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       24
193 Load_Cycle_Count        0x0032   001   001   000    Old_age   Always       -       2461466
194 Temperature_Celsius     0x0022   113   105   000    Old_age   Always       -       37
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   200   200   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0008   200   200   000    Old_age   Offline      -       2


My device is slightly different from the one used for the german tutorial - my SDB2 is ext3 (item 8).

Hence, I ran e2fsck on SDB1:
Code:
root@Microknoppix:~# e2fsck /dev/sdb1
e2fsck 1.42.13 (17-May-2015)
/dev/sdb1 has gone 3150 days without being checked, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/sdb1: 16/62720 files (0.0% non-contiguous), 9674/250112 blocks

root@Microknoppix:~# e2fsck /dev/sdb1
e2fsck 1.42.13 (17-May-2015)
/dev/sdb1: clean, 16/62720 files, 9674/250112 blocks

as well as SDB2:
Code:
root@Microknoppix:~# e2fsck /dev/sdb2
e2fsck 1.42.13 (17-May-2015)
/dev/sdb2 has gone 1437 days without being checked, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/sdb2: 33392/312624 files (0.2% non-contiguous), 228574/1250048 blocks

root@Microknoppix:~# e2fsck /dev/sdb2
e2fsck 1.42.13 (17-May-2015)
/dev/sdb2: clean, 33392/312624 files, 228574/1250048 blocks


So, finally, to the original issue - checking the partition type and file system on SDB6:
Code:
root@Microknoppix:~# xfs_repair /dev/sdb6
Phase 1 - find and verify superblock...
        - reporting progress in intervals of 15 minutes
Phase 2 - using internal log
        - zero log...
        - scan filesystem freespace and inode maps...
        - 16:29:31: scanning filesystem freespace - 32 of 32 allocation groups done
        - found root inode chunk
Phase 3 - for each AG...
        - scan and clear agi unlinked lists...
        - 16:29:31: scanning agi unlinked lists - 32 of 32 allocation groups done
        - process known inodes and perform inode discovery...
        - agno = 0
        - agno = 15
        - agno = 30
        - agno = 31
        - agno = 1
        - agno = 2
        - agno = 16
        - agno = 17
        - agno = 18
        - agno = 19
        - agno = 20
        - agno = 21
        - agno = 22
        - agno = 23
        - agno = 24
        - agno = 25
        - agno = 26
        - agno = 27
        - agno = 28
        - agno = 29
        - agno = 3
        - agno = 4
        - agno = 5
        - agno = 6
        - agno = 7
        - agno = 8
        - agno = 9
        - agno = 10
        - agno = 11
        - agno = 12
        - agno = 13
        - agno = 14
        - 16:29:38: process known inodes and inode discovery - 40000 of 40000 inodes done
        - process newly discovered inodes...
        - 16:29:38: process newly discovered inodes - 32 of 32 allocation groups done
Phase 4 - check for duplicate blocks...
        - setting up duplicate extent list...
        - 16:29:38: setting up duplicate extent list - 32 of 32 allocation groups done
        - check for inodes claiming duplicate blocks...
        - agno = 1
        - agno = 0
        - agno = 2
        - agno = 3
        - agno = 4
        - agno = 5
        - agno = 6
        - agno = 7
        - agno = 8
        - agno = 9
        - agno = 10
        - agno = 11
        - agno = 12
        - agno = 13
        - agno = 14
        - agno = 15
        - agno = 16
        - agno = 17
        - agno = 18
        - agno = 19
        - agno = 20
        - agno = 21
        - agno = 22
        - agno = 23
        - agno = 24
        - agno = 25
        - agno = 26
        - agno = 27
        - agno = 28
        - agno = 29
        - agno = 30
        - agno = 31
        - 16:29:38: check for inodes claiming duplicate blocks - 40000 of 40000 inodes done
Phase 5 - rebuild AG headers and trees...
        - 16:29:38: rebuild AG headers and trees - 32 of 32 allocation groups done
        - reset superblock...
Phase 6 - check inode connectivity...
        - resetting contents of realtime bitmap and summary inodes
        - traversing filesystem ...
        - traversal finished ...
        - moving disconnected inodes to lost+found ...
Phase 7 - verify and correct link counts...
done


This took less than a minute - not the long time mentioned in the german URL (item 11). So I ran it again, with identical results.

Unfortunately, whilst the results seem to indicate that the drive is fine, once placed back into the LS chassis, I am still seeing the i11 error. Any other suggestions most gratefully received.


Top
   
PostPosted: Thu Jun 16, 2016 10:35 am 
Offline
Moderator

Joined: Mon Apr 26, 2010 10:24 am
Posts: 2730
Quote:
193 Load_Cycle_Count 0x0032 001 001 000 Old_age Always - 2461466


You dont have fixed the bug
http://forum.nas-hilfe.de/festplatten-und-ssd-laufwerke/western-digital-in-einer-ls-xhl-load-cycle-count-t1435.html


do not trust this drive!

__300.000 is the maximum allowed
2.461.466 is yours

now go to emmode
delete the demaged firmware

Code:
mkdir /mnt/test
mount /dev/sdb2 /mnt/test
cd /mnt/test
rm -rf *
cd ..
umount /dev/sdb2


Top
   
PostPosted: Thu Jun 16, 2016 10:43 am 
Offline
Moderator

Joined: Mon Apr 26, 2010 10:24 am
Posts: 2730
You have red blinking led

E11 fan error
your fan is to slow!


https://josephlo.wordpress.com/2011/07/17/what-do-the-errorinformation-codes-indicate-ls-wvl-ls-wxl-series/


Top
   
PostPosted: Thu Jun 16, 2016 9:07 pm 
Offline
Newbie

Joined: Thu Jul 12, 2007 10:08 pm
Posts: 24
oxygen8 wrote:
You have red blinking led
E11 fan error
your fan is to slow!


I'm getting the E06 error, not E11. I *was* getting i11... too many error codes that are too similar :)

>>>

I had already purchased a new WD Red drive to replace the green, so now I am trying to rebuild the NAS from scratch.

I followed this guide here:
http://forum.nas-hilfe.de/buffalo-techn ... -t903.html

My TFTP process works, and I see the two files served (I have used what I believe to the correct ones for a LS-VL from the 1.71 firmware download):
Code:
Starting TFTP...
alias / is mapped to O:\Temp\LS-VL\TFTP Boot Recovery\
listening On: 127.0.0.1:69
listening On: 192.168.2.232:69
listening On: 192.168.26.232:69
listening On: 192.168.11.1:69
listening On: 169.254.218.162:69
permitted clients: all
server port range: all
max blksize: 65464
defult blksize: 512
default interval: 3
overwrite existing files: No
thread pool size: 1

accepting requests..
Client 192.168.11.150:3401 O:\Temp\LS-VL\TFTP Boot Recovery\uImage.buffalo, 9298 Blocks Served
Client 192.168.11.150:2565 O:\Temp\LS-VL\TFTP Boot Recovery\initrd.buffalo, 18781 Blocks Served


As you can see, the NAS is on the network and boots from it's default IP of 192.168.11.150. Following that, it should either pick up a DHCP address (nope, checked DHCP server), or be on an autoconfiguration address (if I understand correctly).

From the TFTP boot server, you can see that I have a number of subnets configured:
127.0.0.1:69 standard loopback address - irrelevant here
192.168.2.232:69 - my main subnet, location of DHCP server which linkstation is not using
192.168.26.232:69 - the subnet the linkstation *was* on before it went nuts
192.168.11.1:69 - subnet for default linkstation IP
169.254.218.162:69 - autoconfiguration subnet with a mask of /16 (255.255.0.0)

My LSUpdater.ini file has been modified to the following:
Code:
[Application]
Title = BUFFALO LinkStation Series Updater Ver.1.71
WaitReboot = 1200
WaitFormat = 600
WaitFileSend = 600
WaitDiscover = 120

[Target]
ProductID = 0x00000011
ProductID2 = 0x00000012
ProductID3 = 0x00000013
ProductID4 = 0x00000014
ProductID5 = 0x00003006
ProductID6 = 0x00003007
ProductID7 = 0x00000015
ProductID8 = 0x00000016
ProductID9 = 0x00003008
ProductID10 = 0x00004001
ProductID11 = 0x00000017
ProductID12 = 0x00000019
ProductID13 = 0x00000020
ProductID14 = 0x00003010
Name = LinkStation

[Flags]
VersionCheck = 0
NoFormatting = 0

[Special Flags]
Debug = 1


...however, it does not see the LS-VL.

I ran NASNavigator which only sees my LS420 which is plugged into the same switch as the TFTPboot machine and the LS-VL.


I also ran this process on my laptop, with WIFI disabled, and a direct ethernet connection between the LS-VL and the laptop.
Windows Firewall is disabled, TFTPboot is allowed through the firewall just to be safe
Wired LAN Ethernet is configured with two IPs, and no default gateway:
192.168.11.1/24
169.254.11.1/16.

Same behavior - TFTPboot serves two files, but the Linkstation never shows up again after pulling the two files.
I have a wireshark capture of the TFTP process if that helps...

Any idea what is going wrong?
Thanks again!


Top
   
PostPosted: Thu Jun 16, 2016 11:00 pm 
Offline
Moderator

Joined: Mon Apr 26, 2010 10:24 am
Posts: 2730
your led must be solid blue

you can try my tftp
http://forum.nas-hilfe.de/resources/file/580


Top
   
PostPosted: Fri Jun 17, 2016 4:48 pm 
Offline
Newbie

Joined: Thu Jul 12, 2007 10:08 pm
Posts: 24
oxygen8 wrote:


Ahhh, must have had one of the files wrong. Thank you SO MUCH for all your help, I am now able to update firmware and have a newly working NAS!!

Have a great weekend!


Top
   
PostPosted: Fri Jun 17, 2016 11:31 pm 
Offline
Newbie

Joined: Thu Jul 12, 2007 10:08 pm
Posts: 24
Copied all the data to the new NAS, went to check the share, and found the dratted thing is in JAPANESE!!!!

Auugghhhhh!!!!! Thankfully I was able to guess the right button presses from reading the manual. :lol:


Top
   
Display posts from previous:  Sort by  
Post new topic  Reply to topic  [ 9 posts ] 

All times are UTC+01:00


Who is online

Users browsing this forum: No registered users and 2 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Powered by phpBB® Forum Software © phpBB Limited