Buffalo Forums

Products => Storage => Topic started by: Icarus on November 25, 2020, 03:21:09 PM

Title: Cannot access previous SHARED_STUFF directory
Post by: Icarus on November 25, 2020, 03:21:09 PM
Hi all

Hope everyone one is coping well in these trying times!

Here is my problem.

I'm running Win10

My LS-WXL/R1 started to play up and not allow me access to it.
its 1TB raid 0

Long story short I re-installed the firmware, 1.74 and now I can see the drive on my network and in NAs navi, I can even see the shared folder and its top level listing, but I cannot get into any of those listed directories.

I can create a new shared folder via the web admin page and then I can access that 100% via windows file manager, dragging and dropping files into it with no problem, but I cannot get into the original Shared folder where all my important files are.

I do have a backup, but it is a month behind so I would like to get into that folder again.

I have deleted all the users and made new ones in the web admin, along with the same name and password I use to logon to my pc, still no access

The error I get says that I do not have access to that directory.

How can I get into there once more?
I'm guessing its a security level thing?
I'm logged into windows as admin etc.

Any suggestions?
Thanks

EDIT:  I had to also re-install Win10 and have activated SMB1 but still no access to the stuff in the Shared Stuff directory.

Title: Re: Cannot access previous SHARED_STUFF directory
Post by: oxygen8 on November 26, 2020, 03:30:17 AM
1) open ssh
http://oxygen8.bplaced.net/SSH_mit_2_Klicks.html

2) login as superuser root

3) read the directory, you need
example

ls -lha /mnt/array1/share

Can you see your data?
Title: Re: Cannot access previous SHARED_STUFF directory
Post by: Icarus on November 26, 2020, 11:04:24 AM
Hi Oxygen8

Yes, I can see my data using that program!

How can I access it via Windows?

Thanks for your help! :)

EDIT:  The structure of this NAS is: Shared-Stuff/shared-stuff/*various directories*

I can see listed in windows Shared-Stuff/shared-stuff/*list of directories*  But I cannot go any deeper into the listings

Okay, i've downloaded ACPcommander and reset root PW to what it was.
Then I downloaded bitvise and have logged onto the Linkstation and have managed to transfer some files from the linkstation to a local drive!
But there are still some directories that I cannot get into, such as the Documents one, though I have been able to rename it.
Title: Re: Cannot access previous SHARED_STUFF directory
Post by: oxygen8 on November 26, 2020, 02:14:47 PM
"that I cannot get into"

logged in as root it is not possible to lock a directory
but it is possible to have demaged folder

copy all you need from an unvisible folder to a folder you can see with windows


after that test your diskhardware

smartctl -d marvell -a /dev/sda

Title: Re: Cannot access previous SHARED_STUFF directory
Post by: Icarus on November 26, 2020, 04:58:05 PM
I have tested the hardware with that command line and it looks to have passed:

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x82)   Offline data collection activity
               was completed without error.
               Auto Offline Data Collection: Enabled.
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:        (13500) seconds.
Offline data collection
capabilities:           (0x7b) SMART execute Offline immediate.
               Auto Offline data collection on/off support.
               Suspend Offline collection upon new
               command.
               Offline surface scan supported.
               Self-test supported.
               Conveyance Self-test supported.
               Selective Self-test supported.
SMART capabilit

I have grabbed as much data off the drive as I can, but the directory that I really want to get into is still not opening up :(
Title: Re: Cannot access previous SHARED_STUFF directory
Post by: oxygen8 on November 27, 2020, 06:58:09 AM
Your posted output is not enough

i need this lines

196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0012   098   098   000    Old_age   Always       -       81
198 Offline_Uncorrectable   0x0030   100   100   000    Old_age   Offline      -       0


i do not know a way to block root from a directory

please post your answer
(use your directory)

ls -lha /mnt/array1/...

Title: Re: Cannot access previous SHARED_STUFF directory
Post by: Icarus on November 27, 2020, 06:18:55 PM
I've got into my directory

ls -lha /mnt/array1/Shared-Stuff

And then ran the cmd

smartctl -d marvell -a /dev/sda

This is all in ACP Commander

But I get the same result back as I posted before and nothing containg line numbers as in your example.
I am a complete noob withLinux cmd line stuff and have limited DOS cmd line experiance, so im sure im doing something wrong!
Title: Re: Cannot access previous SHARED_STUFF directory
Post by: oxygen8 on November 28, 2020, 08:46:40 AM
you have to connect with putty
now you can see the full output
Title: Re: Cannot access previous SHARED_STUFF directory
Post by: Icarus on November 28, 2020, 05:26:17 PM
Ahh, I see, PUTTY!

I will give that a go and report back :)

Thank you!
Title: Re: Cannot access previous SHARED_STUFF directory
Post by: Icarus on November 29, 2020, 03:26:03 AM
I cannot logon to the NAS via Putty.

I connect to the NAS and start to logon as Admin, I can see the CMD line curser move as I type this.

Then it asks for the password, when I type this the CMD line curser does not move? Press enter and it exits with unexpected termination of session error.

I can logon to the NAS with PuttyFTP though?

The NAS has all protocols enabled and I have even turned on SSH via aacp Commander just to make sure.

Here is the error log from Putty:

2020-11-29 09:23:05   Looking up host "192.168.0.3" for SSH connection
2020-11-29 09:23:05   Connecting to 192.168.0.3 port 22
2020-11-29 09:23:05   We claim version: SSH-2.0-PuTTY_Release_0.74
2020-11-29 09:23:05   Remote version: SSH-2.0-OpenSSH_3.7.1p2
2020-11-29 09:23:05   We believe remote version has SSH-2 channel request bug
2020-11-29 09:23:05   Using SSH protocol version 2
2020-11-29 09:23:05   No GSSAPI security context available
2020-11-29 09:23:05   Doing Diffie-Hellman group exchange
2020-11-29 09:23:05   Doing Diffie-Hellman key exchange using 3191-bit modulus and hash SHA-1 (unaccelerated) with a server-supplied group
2020-11-29 09:23:07   Host key fingerprint is:
2020-11-29 09:23:07   ssh-rsa 1024 17:60:bb:44:2f:36:d8:df:6b:98:fb:63:7f:52:a7:a1
2020-11-29 09:23:07   Initialised AES-256 SDCTR (AES-NI accelerated) outbound encryption
2020-11-29 09:23:07   Initialised HMAC-SHA-1 (unaccelerated) outbound MAC algorithm
2020-11-29 09:23:07   Initialised AES-256 SDCTR (AES-NI accelerated) inbound encryption
2020-11-29 09:23:07   Initialised HMAC-SHA-1 (unaccelerated) inbound MAC algorithm

Title: Re: Cannot access previous SHARED_STUFF directory
Post by: oxygen8 on November 29, 2020, 04:45:02 AM
try admin
not Admin
Title: Re: Cannot access previous SHARED_STUFF directory
Post by: Icarus on November 29, 2020, 09:34:03 AM
Sorry, typo on my part, I was trying admin

admin and guest are the only accounts on the NAS and guest has no password.
Title: Re: Cannot access previous SHARED_STUFF directory
Post by: oxygen8 on November 30, 2020, 12:08:57 AM
sorry, im am using qnap now

on buffalo you have to login as root
Title: Re: Cannot access previous SHARED_STUFF directory
Post by: Icarus on November 30, 2020, 12:16:37 PM
And we are in!

Here is the report I got running that cmd line:

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       -       0
  3 Spin_Up_Time            0x0027   144   123   021    Pre-fail  Always       -       3791
  4 Start_Stop_Count        0x0032   097   097   000    Old_age   Always       -       3550
  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   049   049   000    Old_age   Always       -       37515
10 Spin_Retry_Count        0x0032   100   100   000    Old_age   Always       -       0
11 Calibration_Retry_Count 0x0032   100   100   000    Old_age   Always       -       0
12 Power_Cycle_Count       0x0032   097   097   000    Old_age   Always       -       3550
192 Power-Off_Retract_Count 0x0032   191   191   000    Old_age   Always       -       7099
193 Load_Cycle_Count        0x0032   134   134   000    Old_age   Always       -       199808
194 Temperature_Celsius     0x0022   115   101   000    Old_age   Always       -       28
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      -       0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]


SMART Selective self-test log data structure revision number 1
SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

Thanks
Title: Re: Cannot access previous SHARED_STUFF directory
Post by: oxygen8 on December 02, 2020, 01:38:59 AM
the disk looks good

you can make a internal selftest to be sure
smartctl -t long /dev/sda
next day you can read out the result


now post the real output and your command to read the directory

check the file permissions and attributes

ls -lha /your directory
Title: Re: Cannot access previous SHARED_STUFF directory
Post by: Icarus on December 02, 2020, 09:44:12 AM
root@Shared-stuff:~# smartctl --test=long /dev/sda
smartctl version 5.37 [arm-none-linux-gnueabi] Copyright (C) 2002-6 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

Long (extended) offline self test failed [unsupported scsi opcode]

Arrggg, what am I doing wrong?
Title: Re: Cannot access previous SHARED_STUFF directory
Post by: oxygen8 on December 04, 2020, 02:01:35 AM
smartctl -d marvell -t long /dev/sda
Title: Re: Cannot access previous SHARED_STUFF directory
Post by: Icarus on December 04, 2020, 01:58:47 PM
Thank you!

Test is under way, 154 mins to go.

Once again, thank you for your assistance with this.
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: 130 (show)
Files included: 27 - 1055KB. (show)
Memory used: 810KB.
Tokens: post-login.
Queries used: 10.

[Show Queries]