plugout.net

Hello,
First of all, thnks you for doing an outstanding job on this FW+support, have been enjoying it for years !
However, I have lost access to my NAS this morning and cannot figure out what the problem is.

- The NAS shows up in my connected devices on my router and gets its correct IP (reserved on the router)
- DDNS works and public IP gets correctly updated
- I am able to login to the web admin interface fine

However,
- I can't login to ftp (permission denied)
- I can't access my shares from the network (mac/pc)
- I can't access anything on Webdav anymore (worked fine yesterday)
- I see the web-explorer and firefly servers show up as "not installed" (both worked fine yesterday), and I get an error 203 when trying to install them back on.
- Can't SSH (server refused to allocate pty).

Here is a screenshot from the "system info" page. Something looks awfully wrong regarding available/free space and the web-explorer server...
Can you please point me in the right direction to regain access ?

Seems something has filled your disk.
Do you have ssh access?

If so give command

Code: Select all

df -h

This will show used and free size of all mounted partitions.
Probably not only data partition is full but maybe also the system partition which may explain the server issues

Also the smart disk command in disk setup may give info if we face here a disk with problems (bad sectors)

Unfortunately I have lost SSH access as well.

There is no reason for anything to have filled up my Disk, it was 75% free last night.

Here is the result from the SMART page, this is about all the info I can gather - can you make anything of it ?

Code: Select all


=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
Please note the following marginal Attributes:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
190 Airflow_Temperature_Cel 0x0022   046   037   045    Old_age   Always   In_the_past 54 (Min/Max 54/55 #4022)

=== START OF READ SMART DATA SECTION ===
Short self-test routine
Extended self-test routine
   SN = Sector Number Register [HEX]
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed: read failure       90%     19925         2933074472

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Barracuda 7200.14 (AF)
Device Model:     ST3000DM001-1CH166
Serial Number:    W1F21FLE
LU WWN Device Id: 5 000c50 05dfcf00e
Firmware Version: CC24
User Capacity:    3,000,592,982,016 bytes [3.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    7200 rpm
Form Factor:      3.5 inches
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS T13/1699-D revision 4
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Thu Apr 11 17:45:32 2019 CEST
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:      ( 121)   The previous self-test completed having
               the read element of the test failed.
Total time to complete Offline
data collection:       (  584) seconds.
Offline data collection
capabilities:           (0x73) 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.
               Conveyance Self-test supported.
               Selective Self-test supported.
SMART capabilities:            (0x0003)   Saves SMART data before entering
               power-saving mode.
               Supports SMART auto save timer.
Error logging capability:        (0x01)   Error logging supported.
               General Purpose Logging supported.
Short self-test routine
recommended polling time:     (   1) minutes.
Extended self-test routine
recommended polling time:     ( 342) minutes.
Conveyance self-test routine
recommended polling time:     (   2) minutes.
SCT capabilities:           (0x3085)   SCT Status supported.

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   097   093   006    Pre-fail  Always       -       132089574
  3 Spin_Up_Time            0x0003   095   093   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   074   074   020    Old_age   Always       -       27303
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       8
  7 Seek_Error_Rate         0x000f   064   055   030    Pre-fail  Always       -       17190579603
  9 Power_On_Hours          0x0032   078   078   000    Old_age   Always       -       19925
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   092   092   020    Old_age   Always       -       8633
183 Runtime_Bad_Block       0x0032   098   098   000    Old_age   Always       -       2
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   094   094   000    Old_age   Always       -       6
188 Command_Timeout         0x0032   099   093   000    Old_age   Always       -       1 15 17
189 High_Fly_Writes         0x003a   099   099   000    Old_age   Always       -       1
190 Airflow_Temperature_Cel 0x0022   045   037   045    Old_age   Always   FAILING_NOW 55 (Min/Max 54/55 #4022)
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       0
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       123
193 Load_Cycle_Count        0x0032   055   055   000    Old_age   Always       -       90455
194 Temperature_Celsius     0x0022   055   063   000    Old_age   Always       -       55 (128 0 0 0 0)
197 Current_Pending_Sector  0x0012   089   089   000    Old_age   Always       -       1896
198 Offline_Uncorrectable   0x0010   089   089   000    Old_age   Offline      -       1896
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       2509h+04m+23.352s
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       18686165234
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       7124445676

SMART Error Log Version: 1
ATA Error Count: 6 (device log contains only the most recent five errors)
   CR = Command Register [HEX]
   FR = Features Register [HEX]
   SC = Sector Count Register [HEX]
   SN = Sector Number Register [HEX]
   CL = Cylinder Low Register [HEX]
   CH = Cylinder High Register [HEX]
   DH = Device/Head Register [HEX]
   DC = Device Command Register [HEX]
   ER = Error register [HEX]
   ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 6 occurred at disk power-on lifetime: 19925 hours (830 days + 5 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 08 ff ff ff 4f 00      00:00:42.573  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00      00:00:42.573  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00      00:00:42.573  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00      00:00:42.573  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00      00:00:42.573  READ FPDMA QUEUED

Error 5 occurred at disk power-on lifetime: 19923 hours (830 days + 3 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 08 ff ff ff 4f 00      00:00:47.636  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00      00:00:47.636  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00      00:00:47.636  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00      00:00:47.636  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00      00:00:47.636  READ FPDMA QUEUED

Error 4 occurred at disk power-on lifetime: 19923 hours (830 days + 3 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f  Error: WP at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 00 e0 78 38 00 40 00      00:00:45.931  WRITE FPDMA QUEUED
  61 00 08 98 29 07 40 00      00:00:45.931  WRITE FPDMA QUEUED
  61 00 08 90 29 07 40 00      00:00:45.931  WRITE FPDMA QUEUED
  60 00 08 ff ff ff 4f 00      00:00:43.120  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00      00:00:43.120  READ FPDMA QUEUED

Error 3 occurred at disk power-on lifetime: 19922 hours (830 days + 2 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 08 ff ff ff 4f 00      00:00:42.443  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00      00:00:42.443  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00      00:00:42.443  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00      00:00:42.443  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00      00:00:42.443  READ FPDMA QUEUED

Error 2 occurred at disk power-on lifetime: 19922 hours (830 days + 2 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 08 ff ff ff 4f 00      00:00:42.492  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00      00:00:42.492  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00      00:00:42.492  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00      00:00:42.492  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00      00:00:42.492  READ FPDMA QUEUED

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed: read failure       90%     19925         2933074472

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.

Oops sorry, I do have SSH I was connecting on the wrong port number.

Here is the result from the "df -h" command :

Code: Select all

login as: root
root@192.168.10.224's password:
root@SEB-EXT:/ # df -h
Filesystem                Size        Used     Available    Use%    Mounted on
/dev/sda1               226.2M    148.3M     65.3M     69%      /
/dev/sda5               739.9M      1.5M    730.7M       0%      /rw_fs
tmpfs                     4.9M       112.0K      4.8M       2%       /rw_fs/tmp/usr/var
/dev/root               226.2M    141.7M     71.9M      66%      /lacie-boot

Am I missing partitions? There was close to 500GB of data in my shared folders...

Clearly the disk has read errors. Also the data partition seems not mounted (sda8). That explains why the two servers do not start and shared folders are not available. What does the command

Code: Select all

mount

Give as output?
And if sda8 is not mounted try this command and post output

Code: Select all

mount /dev/sda8 /share/1000

Thank you very much for taking the time to (try to) help me out.

1/ Here is the output of the "mount" command:

Code: Select all

root@SEB-EXT:/ # mount
/dev/sda1 on / type ext3 (rw,relatime,data=ordered)
none on /proc type proc (rw,relatime)
none on /sys type sysfs (rw,relatime)
none on /dev/pts type devpts (rw,relatime,mode=600)
/dev/sda5 on /rw_fs type ext3 (rw,noatime,data=ordered)
tmpfs on /rw_fs/tmp/usr/var type tmpfs (rw,relatime,size=5000k)
nfsd on /proc/fs/nfsd type nfsd (rw,relatime)
/dev/root on /lacie-boot type ext3 (rw,relatime,data=ordered)

2/ Here is the output for "mount /dev/sda8 /share/1000" :

Code: Select all

root@SEB-EXT:/ # mount /dev/sda8 /share/1000
mount: wrong fs type, bad option, bad superblock on /dev/sda8,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so

3/ Here is output for "dmesg | tail "
root@SEB-EXT:/ # dmesg | tail

Code: Select all

[ 5732.543685] blk_update_request: I/O error, dev sda, sector 2933074536
[ 5732.550182] sd 0:0:0:0: [sda] tag#25 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[ 5732.558451] sd 0:0:0:0: [sda] tag#25 Sense Key : 0x3 [current] [descriptor]
[ 5732.565516] sd 0:0:0:0: [sda] tag#25 ASC=0x11 ASCQ=0x4
[ 5732.570774] sd 0:0:0:0: [sda] tag#25 CDB: opcode=0x88 88 00 00 00 00 00 ae d3 2a 70 00 00 00 08 00 00
[ 5732.580001] blk_update_request: I/O error, dev sda, sector 2933074544
[ 5732.586447] JBD2: Failed to read block at offset 20790
[ 5732.591661] ata1: EH complete
[ 5732.599530] JBD2: recovery failed
[ 5732.602841] EXT4-fs (sda8): error loading journal

Doesn't look very good, does it...
Is there any way to fix it ?

So the file system is corrupted run this command

Code: Select all

e2fsck -y /dev/sda8

when it comes with questions to force rewrite answer yes

If it succeeds to repair the file system, reboot
And keep your fingers crossed

This may fix it. However a drive getting this kind of errors is to my opinion a risk. If it comes to live again I suggest you backup your data asap before it fails forever and replace the disk

omg it worked !
thank you so much, you are my hero

I am backing everything up now, and will replace the disk asap.

Will I have to go through the fvdw console install procedure again ?
Is there a "simple" way to clone or transfer to a new HD ?

:punk glad to hear that it brought back your disk partition.

Yes the easiest way is using the console to prepare the new disk.
What you could consider is copying the nas database on sda5 and wite that to the new disk.That would then keep your settings. You could do this using fvdw-sl console after the installer finished its jobs.
However the shared folders, which are on sda8 will need to be created again unless you are able to make an image of sda8 and store it for example on an disk attached via usb. This is a risk as sda8 may contain bad sectors.
Probably it is faster and more safe to do a fresh install using the default database, recreate the shared folders and copy back your data using your backup.

fantastic. will do.
thanx again !