Recent Posts

Pages: [1] 2 3 ... 10

Storage / Old solutions to The local device is is already in use. not working

« Last post by nick0559 on May 01, 2024, 03:14:35 PM »

HI all,

I have a TS1400D, it has been working fine until recently, it is still working fine for all computers on the network except my primary laptop (Win 10) which now gives the dreaded "NAS an error occurred while reconnecting to \\NAS MicrosoftWindows Network: The local device is is already in use. The connection has not been restored" error. The NAS is working for all other PCs on the network (Linux and Win 10 and 11 all functioning) and the laptop sees other storage devices on the network but not the TS1400D. The laptop had been connecting to the TS1400D with no trouble until recently (Did Microsoft share a virus...sorry I mean update?) I have tried everything I can find on the web, SMB1 does not help (SMB1 is the most common solution), NAS Navi reinstall does nothing. NAS Navigator runs on the laptop and sees the TD1400D but will not browse any drives. TD1400D is at it's correct fixed IP address and shows no errors.

I am out of ideas. Suggestions please.

Nick

Storage / Linkstation LS-QVL9D5 - not seeing new drive

« Last post by phantomcyclist on April 29, 2024, 11:45:51 AM »

I have a LS-QVL9D5 which has been running for years in RAID5 on 4 drives. A drive failed several years ago and I replaced it and the array rebuilt automatically.

Yesterday disk 3 showed error in the Storage status window and the error code E16 showed on the front panel flashing LED. I tried rebooting to check that the error was not some tranistory glitch and now drive 2 also showed an error. I took all the disks out and reseated them in case it was the hardware conenctors at the rear of the disk trays that was the issue. On reboot, drive 2 and 3 showed an error. It seems a coincidence that two drives failed that close together!

I took all the drives out and used contact cleaner spray on the connectors and replaced them into the Linkstation. On reboot drive 2 and 3 showed errors and although drive 1 and 4 are shown as Array 1 along with the unit name. Drive 2 and 3 shown as Error with no unit name. I had a brand new hard drive of suitable size available so I opened the packet, took it out and put into the Linkstation as Drive 3.

On booting both drive 2 and drive 3 show errors so I now wonder if it is the connections at the rear of the drives that are the issue rather than the disks themselves. I was expecting some kind of message about disk 3 (the factory fresh drive) being formatted. Am I likely to be correct that it is the connection that is the issue and if soany suggestions on how to clean the contacts beep inside the chassis, or is it expected behaviour that the Linkstation is not doing anything with the new drive as there is still an issue with the Drive 2.

Any other things I can try before doing a total reset and restore?

Storage / Re: SMTP Server Setup

« Last post by fuzbuster83 on April 28, 2024, 01:32:19 PM »

Assuming I do not get any replies to the issue above, will NAS Navigator2 alert me to failed drives?

Storage / SMTP Server Setup

« Last post by fuzbuster83 on April 26, 2024, 10:10:57 PM »

I am trying to repurpose some TS1400 and TS3400 NAS's for home use. I have them all configured for use and I want to have the alerts set up like I did in the office. I registered an account with MailGun and sent myself a test message from a PowerShell Send-MailMessage command without issue.

When I try to set up the SMTP in the NAS I get a message saying that "Because of and error" the message did not send. In the system log all I see is:

Apr 26 23:09:33 BuffaloNAS12 nasapi - -1255992208 - 5388 -mailnotification - send_test_message - INFO- success

Storage / LS421DE is no longer dectecting hard drive

« Last post by locdenz on April 22, 2024, 07:54:40 AM »

Hello,

I have LS421DE was complaining about Disk 1 was failed, I followed the instructions to replace a new drive, after creating a RAID1, and running RAID scan. It failed on Disk 2. I connected all the disks directly to PC to verify, everything seems to be fine, no error or anything. Put them back in, and the NAS got into EM mode. Tried to use "LSUpdater.exe" to reinstall the firmware with Debug options (checked all options under config group), it kept saying format failed and aborted the update. I read one of the posts here and was able to telnet into the box. "lsblk" command shows no drive despite I have 2 plugged in. I have tried total 6 different drives (including 2 band new) none of them were able to detect. Does that mean something with the hardware?

Thanks,

Storage / Re: External USB drive not showing up on LinkStation SoHo 720 NAS

« Last post by Hostirad on April 20, 2024, 09:37:57 AM »

I might add that I tried an 8GB HP Thumbdrive and unpowered Western Digital 4TB My Passport Drive, and both were instantly accessible through the LinkStation.

Storage / Fan speed of LS-WXL with Debian 12

« Last post by eugrus on April 16, 2024, 07:48:57 PM »

So I've installed Debian 12 onto LS-WXL. Regards to 1000001101000 for the install image.

The fan is just running full speed all the time. The air comes out cold.

The sensors output is not informative (in terms of temperature):

Code: [Select]

# sensors
gpio_fan-isa-0000
Adapter: ISA adapter
fan1:        5000 RPM  (min =    0 RPM, max = 5000 RPM)

sensors-detect finds no sensors

Code: [Select]

# /sbin/sensors-detect
# sensors-detect version 3.6.0
# DMI data unavailable, please consider installing dmidecode 2.7
# or later for better results.
# Kernel: 6.1.85 armv5tel
# Processor: Feroceon 88FR131 rev 1 (v5l)

This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.

Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no): 
modprobe: FATAL: Module cpuid not found in directory /lib/modules/6.1.85
Failed to load module cpuid.
Silicon Integrated Systems SIS5595...                       No
VIA VT82C686 Integrated Sensors...                          No
VIA VT8231 Integrated Sensors...                            No
AMD K8 thermal sensors...                                   No
AMD Family 10h thermal sensors...                           No
AMD Family 11h thermal sensors...                           No
AMD Family 12h and 14h thermal sensors...                   No
AMD Family 15h thermal sensors...                           No
AMD Family 16h thermal sensors...                           No
AMD Family 17h thermal sensors...                           No
AMD Family 15h power sensors...                             No
AMD Family 16h power sensors...                             No
Hygon Family 18h thermal sensors...                         No
Intel digital thermal sensor...                             No
Intel AMB FB-DIMM thermal sensor...                         No
Intel 5500/5520/X58 thermal sensor...                       No
VIA C7 thermal sensor...                                    No
VIA Nano thermal sensor...                                  No

Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no): 
Sorry, no supported PCI bus adapters found.

Sorry, no sensors were detected.
Either your system has no sensors, or they are not supported, or
they are connected to an I2C or SMBus adapter that is not
supported. If you find out what chips are on your board, check
https://hwmon.wiki.kernel.org/device_support_status for driver status.

Is there a way to activate the sensors or do I have to speed down the fans manually via fancontrol or something?

Or are there actually no sensors and the stock firmware just did speed down the fan after the boot?

Storage / External USB drive not showing up on LinkStation SoHo 720 NAS

« Last post by Hostirad on April 15, 2024, 10:29:04 AM »

One reason I bought a LinkStation SoHo 720 NAS is the USB port for attaching an external drive. I had been using a Western Digital Elements 2TB external drive (WDBAAU0025HBK-01) as a shared network drive, attached to the USB port of a Linksys EA7500 router. It is set up with Samba 3.0.37. When I upgraded my router to a Linksys LN1100, I needed a new way to connect the external drive to my network because the new router does not have a USB port. Because the LinkStation SoHo 720 NAS does have two USB ports, I figured that I could simply plug the WD external drive into the rear USB port of the Linkstation. But when I tried this, I could not see the drive when connecting to the LinkStation through the web interface, Storage - USB Drives. (The primary hard drives in the LinkStation show up just fine.) I tried shutting down the LinkStation and starting it again, and the USB drive is still not visible. I disconnected the USB drive and reconnected to my old router, and it shows up as a network drive just fine. The drive is also readable when plugged directly into my Windows 11 laptop. Any ideas on making the external drive visible/accessible?

Storage / Re: Reinstalling to an out-of warranty NAS with blank drives

« Last post by eugrus on April 12, 2024, 05:55:52 AM »

Is there a ready Debian image for LS-WXL that I could just dd onto a drive before I put it into the device (and then extend the partition)? (instead of going through installation)

Storage / LS220D502 - Folders Disappearing

« Last post by tekkie27 on April 10, 2024, 10:41:55 AM »

Hello. I recently started having trouble with my LS220D502. It is set up as an SMB file share for less than ten users in an office. All of whom are using Windows 10 or 11, and Office 365. They connect to the share as a lettered drive. All computers are workgroup, no local domain, and not connected to Azure AD. We access simple Office documents.

Yesterday a folder disappeared. When I try to create a folder with the same name Windows gives me the error "The action can't be completed because the folder or a file in it is open in another program."

If I try to create a folder with the same name in the web interface, I get the error "Unknown error has occurred.internal server error"

I created the folder with a slightly different name and copied the files over from a backup.

That's when I realized the backup recently started failing on 4/5/2024 with various assertions of "Structure needs cleaning (117)"

Today a second folder has gone missing with the same symptoms.

What should I do?

EDIT:
I forgot to mention, after hours yesterday I ran a RAID scan on the RAID array. It is a RAID1 Array with two 2TB drives, with a capacity of 2TB. We are only using 64GB, 3.46%.