Recent Posts

Pages: 1 [2] 3 4 ... 10
11
Storage / Re: Buffalo WS-WV4.0TL/R1 Windows Server 2012 R2 / 2016 help
« Last post by Kane88 on January 20, 2020, 07:17:37 am »
Success!  Thank you so much, that did the trick. :)
I checked all the boxes in debug mode for update + config, including update boot (my usual method, as the drives were wiped), and it worked.
I've got the Buffalo web console up now, and it looks just like their older one for the TS-XEL.

Here is the product page for this one if you want it for your notes or web articles, the firmware update worked with your MAX_DISK_NUM=2 tweak.
http://www.buffalo-asia.com/forbusiness/business_nas/tswss/ws-wvl_r1-ap/

A question on the java stuff:

(I see now where I first went wrong- I was running that command in the acp commander windows gui.  I thought it was a linux command, not ms/windows.  Oops!)

I put acp_commander.jar in the jre library folder:
And still, for whatever reason, it could not run your command.

C:\>java -jar acp_commander.jar -t 192.168.0.106 -c "echo MAX_DISK_NUM=2 >> /etc/nas_feature"
Error: Unable to access jarfile acp_commander.jar

You mentioned the path, so I checked it.  java.exe is definitely in the path
PATH=C:\Program Files (x86)\Common Files\Oracle\Java\javapath;<rest of path...>
It only has that path, no libraries or other java paths are in it.

I wound up having doing it this way, and it worked w/windows firewall disabled.
C:\>cd "C:\Program Files (x86)\Java\jre1.8.0_231\lib"
C:\Program Files (x86)\Java\jre1.8.0_231\lib>java -jar acp_commander.jar -t 192.168.0.106 -c "echo MAX_DISK_NUM=2 >> /etc/nas_feature"
OK (ACP_STATE_OK)
C:\Program Files (x86)\Java\jre1.8.0_231\lib>

How's that going to play out doing the debian install stuff for the other post on the TS-XEL?  Am I going to have to add something else to my path to make things easier for that project? 

----

firmware steps followed:
1. make the boot iso w/systemrescuecd- need to document this process. 
2. boot EM mode via USB
3. run MAX_DISK_NUM 2 command
4. flash with tsupdater
5. unit is at factory defaults, ready for config and use

----

Other observations, nothing to do with the firmware load:

SMART
This WS-WV unit supports SMART, the Buffalo OS on the TS-XEL doesn't.  I assume the other units in this Intel d510 series - also support SMART.

At some point,  I am hoping someone can help me to write a script (maybe even automate it) to where we can run smartctl, and have it save to a text file.  Some other Buffalo units I've seen support SMART, but either do not report the smart data in the web console (TS 3400), or if they do, there's not enough detail in it (TS 5400).

I wind up using the windows acp commander gui manually to run these guys...

smartctl -a /dev/sda
smartctl -A /dev/sda
smartctl -a /dev/sdb
smartctl -A /dev/sdb
smartctl -a /dev/sdc
smartctl -A /dev/sdc
smartctl -a /dev/sdd
smartctl -A /dev/sdd

The idea is to have these commands run every 4 hours, or at some regular interval.

One monitoring report emailed every 24hrs, really isn't enough monitoring.  Plus, the report the nas sends- has little detail in it. 

I had a failed disk last month that just about knocked out a whole raid 0 array in a 3400 series, and I didn't realize it- until 2 weeks after the failure began.  (Who's going to log in and check email, when they are busy?!)  The seagate drive in question, jumped from 400+ bad sectors, to almost 15000 in like 2 days!!!!  Having a regularly updated SMART log to check, would be beneficial.  Buffalo needs to up their game in the monitoring dept, no question.

sample info from /dev/sda on this modified WS-WV unit:
running
smartctl -a /dev/sda
smartctl -A /dev/sda


smartctl -a /dev/sda <tells us our disk model, serial, firmware version, etc>
ACP Commander v1.5.6.0 started
Sending discovery request...
Found new LinkStation 192.168.0.106
Authenticate EnOneCmd... OK
Authenticate with admin pw... OK
smartctl version 5.37 [x86_64-unknown-linux-gnu] Copyright (C) 2002-6 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF INFORMATION SECTION ===
Device Model:     ST2000DM001-9YN164
Serial Number:    XXXXXXXX
Firmware Version: CC9D
User Capacity:    2,000,398,934,016 bytes
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   8
ATA Standard is:  Not recognized. Minor revision code: 0x29
Local Time is:    Mon Jan 20 18:27:15 2020 JST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
See vendor-specific Attribute list for marginal Attributes.

General SMART Values:
Offline data collection status:  (0x00)   Offline data collection activity
               was never started.
               Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0)   The previous self-test routine completed
               without error or no self-test has ever
               been run.
Total time to complete Offline
data collection:        ( 575) seconds.
Offline data collection
capabilities:           (0x13) SMART execute Offline immediate.
               Auto Offline data collection on/off support.
               Suspend Offline collection upon new
               command.
               No Offline surface scan supported.
               Self-test supported.
               No Conveyance Self-test supported.
               No Selectiv

smartctl -A /dev/sda <gives us an accurate reallocated sector count, power on hours, power on/off cycles, and more>
Authenticate EnOneCmd... OK
Authenticate with admin pw... OK
smartctl version 5.37 [x86_64-unknown-linux-gnu] Copyright (C) 2002-6 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF READ SMART DATA SECTION ===
SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   116   099   006    Pre-fail  Always       -       104382496
  3 Spin_Up_Time            0x0003   095   094   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   099   099   020    Old_age   Always       -       1165
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   072   057   030    Pre-fail  Always       -       17248962564
  9 Power_On_Hours          0x0032   086   086   000    Old_age   Always       -       12951
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       372
183 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       0
184 Unknown_Attribute       0x0032   100   100   099    Old_age   Always       -       0
187 Unknown_Attribute       0x0032   097   097   000    Old_age   Always       -       3
188 Unknown_Attribute       0x0032   100   099


----

other observations:

I do notice that my seagate drives are a little beepy (not the typical crunchy r/w sound) on the bootup with this buffalo os.
That wasn't the case when using the Windows 2008 R2 os.

Too bad Buffalo has not updated their os for this series to be on par with the 3400 and 5400 series interface.
It's limited to SMB 1.x, whereas the Win 2008 Storage Server R2 had SMB 2.1 :(
Big read/write speed drop from 100MB/sec in Win 2008 R2 to 30MB/sec, typical of this buffalo os :(

I hope buffalo continues to security patch this series, it's better than being in an unsupported microsoft os for now anyway.

SMB 1.x can be added to Windows (though it is insecure).  I have it added on an 'acceptable risk' machine.

C:\>net use Z: \\TS-WVHLB80\share
System error 384 has occurred.

You can't connect to the file share because it's not secure. This share requires the obsolete SMB1 protocol, which is unsafe and could expose your system to attack.
Your system requires SMB2 or higher. For more info on resolving this issue, see: https://go.microsoft.com/fwlink/?linkid=852747



The only other option I see so far on the windows side, is to go with the Windows 2012 R2 or 2016 upgrades, but lose the buffalo management software and their apps in the process.  I don't know what the buffalo preinstalled software really is even needed for, except for iSCSI users, NAS monitoring, and to control the NAS display.

----

Thanks again for your help.
12
Storage / Re: Buffalo WS-WV4.0TL/R1 Windows Server 2012 R2 / 2016 help
« Last post by 1000001101000 on January 19, 2020, 09:49:37 pm »
You just need java on your PC. It should add java to your path so that typing java works but you may need to logout/reboot/open new shell depending on setup. If you can find where java is you can run ot directly too.
13
Storage / Re: Buffalo WS-WV4.0TL/R1 Windows Server 2012 R2 / 2016 help
« Last post by Kane88 on January 19, 2020, 09:44:11 pm »
Ok, I ran ACP commander on my windows pc, java is installed on the pc.
then I did your command as
java -jar acp_commander.jar -t 192.168.0.106 -c "echo MAX_DISK_NUM=2 >> /etc/nas_feature"

console is showing
TS-QVHL-EMB80 login: sh: java: command not found

and when i login to console with admin/password and then run it, i get
-sh: java: command not found

does java and/or acp commander need to be installed or copied into this EM session somehow?
If so, I don't know how to do that.
14
Storage / Re: Buffalo WS-WV4.0TL/R1 Windows Server 2012 R2 / 2016 help
« Last post by 1000001101000 on January 19, 2020, 09:22:38 pm »
You run it from your pc, it uses the same protocol that the firmware updater does.

In EM mode the username/password is admin/password though you won’t needed it.
15
Storage / Re: Buffalo WS-WV4.0TL/R1 Windows Server 2012 R2 / 2016 help
« Last post by Kane88 on January 19, 2020, 09:19:07 pm »
That is great news.  Glad it worked! Ok, I'll give it a shot.

But before I do, I'm going to need a login.  When the EM USB ISO finishes booting, it eventually goes to a login prompt.

Also, am I running ACP commander on the EM console?  Or am I running ACP commander from my windows pc?

Thanks.

16
Storage / Re: Buffalo WS-WV4.0TL/R1 Windows Server 2012 R2 / 2016 help
« Last post by 1000001101000 on January 19, 2020, 08:14:58 pm »
I was able to install with only two disks by setting the MAX_DISK_NUM to 2. Here is how you can accomplish that:

1. Boot into EM mode again with both drives blank
2. Download ACP Commander from https://github.com/1000001101000/acp-commander
3. install java if you don't already have it installed
4. Run the following command:
Code: [Select]
java -jar acp_commander.jar -t <device ip address> -c "echo MAX_DISK_NUM=2 >> /etc/nas_feature"5. Run the install again with all the debug options set except Update BOOT

Let me know if that helps.

17
Storage / Re: TS-X4.0TL/R5 LCD display not working
« Last post by 1000001101000 on January 19, 2020, 02:25:28 pm »
The github page has a wiki with installation instructions etc.
https://github.com/1000001101000/Debian_on_Buffalo/wiki

They are similar in that they are ARMv5 devices which allows them to use the same firmware (just with different kernels). They did the same thing with linkstation firmware for devices of that same time period.


18
Storage / Re: TS-X4.0TL/R5 LCD display not working
« Last post by Kane88 on January 19, 2020, 01:50:44 pm »
I should probably mention, in the other thread you referred to trying a TS-XEL and this thread referred to a TS-XL. I added support for both at around the same time (though they have pretty different hardware).

I've got more details about the hardware if you're interested:

https://buffalonas.miraheze.org/wiki/Terastation_TS-XL
https://buffalonas.miraheze.org/wiki/Terastation_TS-XEL
Thanks, I didn't know.  I'm glad you said that.
Buffalo's firmware is labelled as TS-X series and works for both the TS-X and TS-XE.  So I assumed they had similar hardware.

The ones I have are the TS-XE4.0TL/R5 etc.  The front port slots are covered on these.

I'll read up on the TS-XEL steps, and see if I can get your debian loaded on it.

Edit:
Just wanted to check if these are the right instructions...  it took some searching to get there.  Thanks :)
https://github.com/1000001101000/Debian_on_Buffalo/wiki/Preparing-Device-for-Debian-Install
19
Storage / Re: LS-WVL gets in a boot loop after every update
« Last post by Rinkel80 on January 19, 2020, 11:58:25 am »
The machine is running. I tracked down the old hard drive.  I asked the owner of the disk if he still had the disk. He has. So this evening I drove to his place to fetch the disk. Lucky me he didn't wipe it.

So I booted the machine without any problems from bay two. I installed the WD in bay one. Formatted and let the nas boot alone. I now get messages that disk 2 is missing. But I don't care. The Buffalo will be a backup machine. So if it crashes then that's not a problem. I should make a image of the old bootdisk. So when I have a problem I can just put the image back on the disk.
20
Storage / Re: TS-X4.0TL/R5 LCD display not working
« Last post by 1000001101000 on January 19, 2020, 11:54:42 am »
I should probably mention, in the other thread you referred to trying a TS-XEL and this thread referred to a TS-XL. I added support for both at around the same time (though they have pretty different hardware).

I've got more details about the hardware if you're interested:

https://buffalonas.miraheze.org/wiki/Terastation_TS-XL
https://buffalonas.miraheze.org/wiki/Terastation_TS-XEL
Pages: 1 [2] 3 4 ... 10