Recent Posts

Pages: 1 ... 8 9 [10]
91
Storage / Re: Cannot change IP address on LS-X2.0TL
« Last post by sdpetersd on April 20, 2019, 10:17:58 pm »
I was unable to open the web link (settings) since my new IP was 192.168.1.x & my drive still thought it was on 192.168.0.x.  I could never get the web page to display.  Thanks for the info.


Finally resolved!!
Went to a friends home that was using ip, 192.168.0.1 configuration.  Setup drive & was able to access.  Set IP as 192.168.1.210 (Static) and performed a shutdown from the web link.  Brought back home, connected to my new router (192.168.1.1) and drive was able to connect!
92
Storage / Re: Cannot change IP address on LS-X2.0TL
« Last post by 1000001101000 on April 20, 2019, 08:40:59 am »
Checkout page 31 of the ls-xl manual for the procedure to shutdown the device without pulling out the power cable:
http://manual.buffalo.jp/buf-doc/35020118-02_EN.pdf

93
Storage / Re: LS220DE - Replacing Drive in RAID1
« Last post by 1000001101000 on April 20, 2019, 08:34:13 am »

If you just clone the drive using dd you'll end up with a 4tb drive with a 3tb partition table on it. Most systems won't have a problem with it but in my experience these devices won't boot off a drive with a gpt partition table with an odd size like that. I assume this is due to how the boot loader (uboot) works. Assuming you boot from the other drive it would probably still come up. If your drive cloner automatically corrects the partition table (or you do manually) it would probably boot just fine.

Either way I believe this would leave you with a 4tb drive with 1tb of blank space at the end which may or may not be bootable by the device but would probably work with the existing raid arrays.

If as part of that process you also resized the data partition you'd end up ~3tb raid array within a ~4tb partition (or basically the same place as adding the drive blank and having the firmware add it to the existing array).   

I wouldn't recommend actually doing this, there are multiple opportunities in the process (at least while using the stock firmware) to have the system appear to function normally but quietly leave one of the drives in an unbootable state that only get's noticed when you try to replace the second drive.

94
Storage / Re: LS220DE - Replacing Drive in RAID1
« Last post by Pettigrew95 on April 19, 2019, 11:24:35 pm »
Then it should apply to any share on the NAS.

I have a question, what would happen if I took the smaller 3 TB drive out of the NAS after powering it down first, then cloned the 3TB drive to a 4TB drive using a drive cloner, then put that cloned 4 TB drive into the NAS and powered it back up?
95
Storage / Re: Cannot change IP address on LS-X2.0TL
« Last post by sdpetersd on April 19, 2019, 08:54:31 pm »
Since there is no 'power' button on the LS-XL646, the only way to power is off is just to pull the power wire.  Every time I do this the "NAS Navigator2 screen shows the same configuration:
IP Address: 192.168.0.225
SubnetMask: 255.255.255.0
Default Gateway: 192.168.0.1
MAC Address....
Firmware: 1.74
Selecting Properties, IP Address tab, then selecting "Use DHCP" & "Renew IP address", it displays:
"No response from drive."
It does not matter how many times I unplug and power back up the unit, it always re-displays the same information.

Even attempting to set a static IP & changing the netmask to either 255.255.255.0 OR 255.255.0.0, does not make any change & always comes back with:
"No response from drive."

I then connected the LS-XL646 directly to my computer (first using a crossover cable and then a straight cable) but my computer does not even see it.  I have noticed that without a cable & selecting Refresh, the LS-XL646 disappears from the NAS Navigator2 screen but then using EITHER cable and performing a refresh with either cable, the NAS Navigator2 screen does see that the LS-XL646 is there but responds with:
Could not set system clock.
Could not change the IP address of LS-XL646.
Sincerely,
96
Storage / Re: f/w 1.72 problems on TS-XEL/R5
« Last post by oxygen8 on April 19, 2019, 10:20:17 am »
enable telnet or ssh
connect with putty
analyse the output from
Code: [Select]
top
Code: [Select]
Mem: 235328K used, 13204K free, 0K shrd, 2772K buff, 187140K cached
CPU:   2% usr   6% sys   0% nice  91% idle   0% io   0% irq   0% softirq
Load average: 0.01 0.02 0.05
  PID  PPID USER     STAT   VSZ %MEM %CPU COMMAND
 2618     1 root     S     2904   1%   1% /bin/bash /usr/local/sbin/diskmon_exec.sh start
  435 24614 root     S     7252   3%   0% sshd: root@pts/0
    3     2 root     SW       0   0%   0% [ksoftirqd/0]
 3375     1 root     S    51188  21%   0% /opt/bin/transmission-daemon -g /mnt/disk1/share/.config/transmission-daemon
 1838     1 root     S    27024  11%   0% /usr/bin/python /usr/local/sbin/BuffaloXMLRPCServer.pyc --skip-auth
 2938     1 root     S    18148   7%   0% /usr/local/BootServer/rarpd
 6759 24568 root     S    17860   7%   0% /usr/local/sbin/smbd -D
24574 24568 root     S    13764   6%   0% /usr/local/sbin/smbd -D
24568     1 root     S    13756   6%   0% /usr/local/sbin/smbd -D
97
Storage / Re: Duplicate and triplicate entries in music database
« Last post by scofficial on April 19, 2019, 07:32:55 am »
Hey,
I am also facing same issue Duplicate and triplicate entries.
Any help will be appreciated.
Best Regards.
98
Storage / f/w 1.72 problems on TS-XEL/R5
« Last post by Mehanik on April 19, 2019, 05:49:07 am »
Hello
This latest 1.72 firmware update has strange issues:
1) Dramatically slowing down LAN speed with BitTorrent enabled. No any torrents added, no any transmissions active. Just enabling BitTorrent causing problem. Transfer rate over LAN goes down from ~30 MB/s то 2-3 MB/s (SMB). How to fix it?
2) Very strange CPU load in System Log. It is rising up or going down, percent by percent during long period of time. During last month it is downing from 100%, 99%, 98%, 97%.... 68% as for today.  Why it is so?
Nothing unusual in usage. Nothing has been changed. But on f/w 1.66 there were no such problems.


Last days sample:
Code: [Select]
Apr 17 20:30:02 NAS1 nas_status.sh: loadavg= 0.24 0.08 0.02 : CPU Utilization= 71%
Apr 17 21:00:02 NAS1 nas_status.sh: loadavg= 0.00 0.00 0.00 : CPU Utilization= 71%
Apr 17 21:30:01 NAS1 nas_status.sh: loadavg= 0.00 0.00 0.00 : CPU Utilization= 71%
Apr 17 22:00:01 NAS1 nas_status.sh: loadavg= 0.00 0.00 0.00 : CPU Utilization= 71%
Apr 17 22:15:19 NAS1 linkstation: log saved to NAND(cron)
Apr 17 22:30:01 NAS1 nas_status.sh: loadavg= 0.00 0.01 0.00 : CPU Utilization= 71%
Apr 17 23:00:01 NAS1 nas_status.sh: loadavg= 0.00 0.01 0.00 : CPU Utilization= 71%
Apr 17 23:30:02 NAS1 nas_status.sh: loadavg= 0.02 0.02 0.00 : CPU Utilization= 71%
Apr 18 00:00:01 NAS1 nas_status.sh: loadavg= 0.00 0.00 0.00 : CPU Utilization= 71%
Apr 18 00:15:08 NAS1 linkstation: [Success] Sync to ntp server
Apr 18 00:30:01 NAS1 nas_status.sh: loadavg= 0.05 0.02 0.00 : CPU Utilization= 71%
Apr 18 01:00:02 NAS1 nas_status.sh: loadavg= 0.00 0.00 0.00 : CPU Utilization= 71%
Apr 18 01:30:01 NAS1 nas_status.sh: loadavg= 0.00 0.01 0.00 : CPU Utilization= 71%
Apr 18 02:00:01 NAS1 nas_status.sh: loadavg= 0.00 0.00 0.00 : CPU Utilization= 71%
Apr 18 02:30:01 NAS1 nas_status.sh: loadavg= 0.00 0.00 0.00 : CPU Utilization= 71%
Apr 18 03:00:01 NAS1 nas_status.sh: loadavg= 0.00 0.00 0.00 : CPU Utilization= 71%
Apr 18 03:30:01 NAS1 nas_status.sh: loadavg= 0.00 0.00 0.00 : CPU Utilization= 71%
Apr 18 04:00:01 NAS1 nas_status.sh: loadavg= 0.00 0.02 0.00 : CPU Utilization= 71%
Apr 18 04:30:01 NAS1 nas_status.sh: loadavg= 0.00 0.00 0.00 : CPU Utilization= 71%
Apr 18 04:49:02 NAS1 S40B_update_notifications.sh: deleting old settings...
Apr 18 04:49:02 NAS1 last message repeated 2 times
Apr 18 04:49:02 NAS1 S40B_update_notifications.sh: checking and registering to cron...
Apr 18 04:49:02 NAS1 S40B_update_notifications.sh: old xml file found. deleting...
Apr 18 04:49:04 NAS1 S40B_update_notifications.sh: starting f/w cheking process ...
Apr 18 04:49:06 NAS1 S40B_update_notifications.sh: step1 result=0
Apr 18 04:49:06 NAS1 S40B_update_notifications.sh: version_is_latest
Apr 18 04:49:06 NAS1 S40B_update_notifications.sh: deleting from lcd...
Apr 18 05:00:01 NAS1 nas_status.sh: loadavg= 0.00 0.00 0.00 : CPU Utilization= 70%
Apr 18 05:30:01 NAS1 nas_status.sh: loadavg= 0.00 0.01 0.00 : CPU Utilization= 70%
Apr 18 06:00:01 NAS1 nas_status.sh: loadavg= 0.00 0.00 0.00 : CPU Utilization= 70%
Apr 18 06:30:01 NAS1 nas_status.sh: loadavg= 0.00 0.00 0.00 : CPU Utilization= 70%
Apr 18 07:00:01 NAS1 nas_status.sh: loadavg= 0.02 0.01 0.00 : CPU Utilization= 70%
Apr 18 07:30:01 NAS1 nas_status.sh: loadavg= 0.00 0.00 0.00 : CPU Utilization= 70%
Apr 18 08:00:01 NAS1 nas_status.sh: loadavg= 0.00 0.00 0.00 : CPU Utilization= 70%
Apr 18 08:30:02 NAS1 nas_status.sh: loadavg= 0.00 0.00 0.00 : CPU Utilization= 70%
Apr 18 09:00:01 NAS1 nas_status.sh: loadavg= 0.02 0.01 0.00 : CPU Utilization= 70%
Apr 18 09:30:01 NAS1 nas_status.sh: loadavg= 0.01 0.03 0.00 : CPU Utilization= 70%
Apr 18 10:00:01 NAS1 nas_status.sh: loadavg= 0.02 0.02 0.00 : CPU Utilization= 70%
Apr 18 10:30:01 NAS1 nas_status.sh: loadavg= 0.00 0.02 0.00 : CPU Utilization= 70%
Apr 18 11:00:01 NAS1 nas_status.sh: loadavg= 0.00 0.00 0.00 : CPU Utilization= 70%
Apr 18 11:30:01 NAS1 nas_status.sh: loadavg= 0.00 0.00 0.00 : CPU Utilization= 70%
Apr 18 12:00:01 NAS1 nas_status.sh: loadavg= 0.02 0.02 0.00 : CPU Utilization= 70%
Apr 18 12:30:01 NAS1 nas_status.sh: loadavg= 0.01 0.01 0.00 : CPU Utilization= 70%
Apr 18 13:00:02 NAS1 nas_status.sh: loadavg= 0.09 0.04 0.01 : CPU Utilization= 70%
Apr 18 13:30:01 NAS1 nas_status.sh: loadavg= 0.00 0.00 0.00 : CPU Utilization= 70%
Apr 18 14:00:01 NAS1 nas_status.sh: loadavg= 0.00 0.00 0.00 : CPU Utilization= 70%
Apr 18 14:30:01 NAS1 nas_status.sh: loadavg= 0.04 0.01 0.00 : CPU Utilization= 70%
Apr 18 15:00:01 NAS1 nas_status.sh: loadavg= 0.00 0.00 0.00 : CPU Utilization= 70%
Apr 18 15:30:02 NAS1 nas_status.sh: loadavg= 0.00 0.00 0.00 : CPU Utilization= 70%
Apr 18 16:00:01 NAS1 nas_status.sh: loadavg= 0.10 0.05 0.01 : CPU Utilization= 70%
Apr 18 16:30:01 NAS1 nas_status.sh: loadavg= 0.00 0.02 0.00 : CPU Utilization= 70%
Apr 18 17:00:01 NAS1 nas_status.sh: loadavg= 0.00 0.01 0.00 : CPU Utilization= 70%
Apr 18 17:30:02 NAS1 nas_status.sh: loadavg= 0.00 0.00 0.00 : CPU Utilization= 69%
Apr 18 18:00:01 NAS1 nas_status.sh: loadavg= 0.00 0.00 0.00 : CPU Utilization= 69%
Apr 18 18:30:01 NAS1 nas_status.sh: loadavg= 0.08 0.05 0.01 : CPU Utilization= 69%
Apr 18 19:00:01 NAS1 nas_status.sh: loadavg= 0.09 0.04 0.01 : CPU Utilization= 69%
Apr 18 19:30:01 NAS1 nas_status.sh: loadavg= 0.00 0.00 0.00 : CPU Utilization= 69%
Apr 18 20:00:02 NAS1 nas_status.sh: loadavg= 1.13 0.89 0.41 : CPU Utilization= 69%
Apr 18 20:30:01 NAS1 nas_status.sh: loadavg= 0.00 0.00 0.12 : CPU Utilization= 69%
Apr 18 21:00:01 NAS1 nas_status.sh: loadavg= 0.01 0.01 0.00 : CPU Utilization= 69%
Apr 18 21:30:01 NAS1 nas_status.sh: loadavg= 0.00 0.03 0.00 : CPU Utilization= 69%
Apr 18 22:00:01 NAS1 nas_status.sh: loadavg= 0.00 0.01 0.00 : CPU Utilization= 69%
Apr 18 22:20:20 NAS1 linkstation: log saved to NAND(cron)
Apr 18 22:30:01 NAS1 nas_status.sh: loadavg= 0.00 0.04 0.04 : CPU Utilization= 69%
Apr 18 23:00:02 NAS1 nas_status.sh: loadavg= 0.00 0.03 0.00 : CPU Utilization= 69%
Apr 18 23:30:01 NAS1 nas_status.sh: loadavg= 0.00 0.02 0.00 : CPU Utilization= 69%
Apr 19 00:00:01 NAS1 nas_status.sh: loadavg= 0.00 0.01 0.00 : CPU Utilization= 69%
Apr 19 00:15:08 NAS1 linkstation: [Success] Sync to ntp server
Apr 19 00:28:01 NAS1 S40B_update_notifications.sh: deleting old settings...
Apr 19 00:28:01 NAS1 last message repeated 2 times
Apr 19 00:28:01 NAS1 S40B_update_notifications.sh: checking and registering to cron...
Apr 19 00:28:02 NAS1 S40B_update_notifications.sh: old xml file found. deleting...
Apr 19 00:28:03 NAS1 S40B_update_notifications.sh: starting f/w cheking process ...
Apr 19 00:28:05 NAS1 S40B_update_notifications.sh: step1 result=0
Apr 19 00:28:05 NAS1 S40B_update_notifications.sh: version_is_latest
Apr 19 00:28:06 NAS1 S40B_update_notifications.sh: deleting from lcd...
Apr 19 00:30:01 NAS1 nas_status.sh: loadavg= 0.03 0.03 0.00 : CPU Utilization= 69%
Apr 19 01:00:01 NAS1 nas_status.sh: loadavg= 0.00 0.00 0.00 : CPU Utilization= 69%
Apr 19 01:30:01 NAS1 nas_status.sh: loadavg= 0.00 0.01 0.00 : CPU Utilization= 69%
Apr 19 02:00:01 NAS1 nas_status.sh: loadavg= 0.00 0.00 0.00 : CPU Utilization= 69%
Apr 19 02:30:02 NAS1 nas_status.sh: loadavg= 0.00 0.00 0.00 : CPU Utilization= 69%
Apr 19 03:00:01 NAS1 nas_status.sh: loadavg= 0.00 0.00 0.00 : CPU Utilization= 69%
Apr 19 03:30:01 NAS1 nas_status.sh: loadavg= 0.00 0.00 0.00 : CPU Utilization= 69%
Apr 19 04:00:01 NAS1 nas_status.sh: loadavg= 0.00 0.00 0.00 : CPU Utilization= 69%
Apr 19 04:30:01 NAS1 nas_status.sh: loadavg= 0.03 0.01 0.00 : CPU Utilization= 69%
Apr 19 05:00:02 NAS1 nas_status.sh: loadavg= 0.00 0.01 0.00 : CPU Utilization= 69%
Apr 19 05:30:01 NAS1 nas_status.sh: loadavg= 0.00 0.00 0.00 : CPU Utilization= 69%
Apr 19 06:00:01 NAS1 nas_status.sh: loadavg= 0.05 0.02 0.00 : CPU Utilization= 69%
Apr 19 06:30:01 NAS1 nas_status.sh: loadavg= 0.00 0.02 0.00 : CPU Utilization= 69%
Apr 19 07:00:02 NAS1 nas_status.sh: loadavg= 0.00 0.00 0.00 : CPU Utilization= 68%
Apr 19 07:30:01 NAS1 nas_status.sh: loadavg= 0.00 0.00 0.00 : CPU Utilization= 68%
Apr 19 08:00:01 NAS1 nas_status.sh: loadavg= 0.00 0.00 0.00 : CPU Utilization= 68%
Apr 19 08:30:01 NAS1 nas_status.sh: loadavg= 0.06 0.04 0.00 : CPU Utilization= 68%
Apr 19 09:00:01 NAS1 nas_status.sh: loadavg= 0.06 0.02 0.00 : CPU Utilization= 68%
Apr 19 09:30:02 NAS1 nas_status.sh: loadavg= 0.00 0.00 0.00 : CPU Utilization= 68%
Apr 19 10:00:01 NAS1 nas_status.sh: loadavg= 0.10 0.03 0.01 : CPU Utilization= 68%
Apr 19 10:30:01 NAS1 nas_status.sh: loadavg= 0.04 0.03 0.00 : CPU Utilization= 68%
Apr 19 11:00:01 NAS1 nas_status.sh: loadavg= 0.01 0.01 0.00 : CPU Utilization= 68%
Apr 19 11:30:02 NAS1 nas_status.sh: loadavg= 0.01 0.01 0.00 : CPU Utilization= 68%
Apr 19 12:00:01 NAS1 nas_status.sh: loadavg= 0.18 0.08 0.02 : CPU Utilization= 68%
Apr 19 12:30:01 NAS1 nas_status.sh: loadavg= 0.00 0.00 0.00 : CPU Utilization= 68%
Apr 19 13:00:01 NAS1 nas_status.sh: loadavg= 0.00 0.00 0.00 : CPU Utilization= 68%
Apr 19 13:30:01 NAS1 nas_status.sh: loadavg= 0.00 0.02 0.00 : CPU Utilization= 68%
Apr 19 14:00:01 NAS1 nas_status.sh: loadavg= 0.16 0.10 0.03 : CPU Utilization= 68%
Apr 19 14:30:02 NAS1 nas_status.sh: loadavg= 0.02 0.02 0.00 : CPU Utilization= 68%
99
Storage / Re: Cannot change IP address on LS-X2.0TL
« Last post by 1000001101000 on April 18, 2019, 09:34:52 pm »
If you are using dhcp on the device you should get a new ip address if you power it off then on again.

If you configured a static ip you could:
change your netmask from 255.255.255.0 to 255.255.0.0 then try accessing itís web interface to change it. If you still canít access it you can try connecting it directly to your pc.
100
Storage / Cannot change IP address on LS-X2.0TL
« Last post by sdpetersd on April 18, 2019, 08:56:33 pm »
I changed Routers (from 192.168.0.1 to 192.168.1.1) but now cannot access LS-XL646 LinkNavigator.  I have rebooted the router, Win10 computer & LinkNavigator but the IP address displayed in "NAS Navigator2" always remains as "192.168.0.225" (my original IP address with the previous router).  Each time I 'refresh', I keep getting the same message:
Could not set system clock.
Could not change the IP address of LS-XL646.

I have checked the network cables
Any suggestions would be greatly appreciated.
Sincerely,
Pages: 1 ... 8 9 [10]