Buffalo Forums

My TeraStation 3000 shows a notification that the system is running in degraded mode due to the degradation of one or more arrays. I only have 1 RAID5 array (Array1) and my 4 disks are part of the the Array. When I check the RAID Array List and click on Array1 it lists my 4 disks but their status are all listed as Normal. Also none of the LED lights on my disks are red indicating failure.

Is there a reason why my RAID Array is in degraded mode when the 4 disks are reported as normal?

Setup email notification and it should let you know which disk is at fault.

Will do and report back.

I got email notification working, however it doesn't list any faulty disk. I should've said that I'm using LVM in my setup. This is the full contents of the email I got from the TeraStation:

QuoteActivity Report


[TeraStation Information]
TeraStation Name: Tomb
LAN 1 MAC Address: XX:XX:XX:XX:XX:XX
Time: 2017/07/20 00:00:02
IP Address: 192.168.1.214
Settings: http://192.168.1.214/
Running Time: 16:59:10


[Drive Use]
LVM (backup): 978180740/1048064000 kB (usage: 94%)
LVM (share): 361330608/1779610624 kB (usage: 21%)

[RAID Status]
The RAID array is in degraded mode.

For the detailed information of the error message and corrective actions, refer to the following URL.
http://buffalo.jp/support_s/guide2/manual/path/help/index.html?ref=100&model=ts3400d&lang=en

Any ideas?

Log onto the admin page -> Press Ctrl+Alt+Shift+b, save the file -> Unzip -> Var -> Is there a log called "HDDerror"?

If so then send me a copy of the contents.

Thanks a lot for your assistance with this. Got the logs.tgz file, untar, navigated to var/log but there's no HDDerror file. Here's the full file listing:

.
├── AnalyzeLog.txt
├── _nongiped.txt
├── _nullfile.txt
├── _over10mb.txt
├── _raidinfo.txt
├── apache
├── backup.log
├── backup.log.1.gz
├── backup.log.2.gz
├── backup.log.3.gz
├── backup.log.4.gz
├── cores
│   ├── nmbd
│   └── smbd
├── cron
├── cron.1.gz
├── cron.2.gz
├── cron.3.gz
├── cron.4.gz
├── dlnaserver.log
├── dlnaserver.log.1.gz
├── dlnaserver.log.10.gz
├── dlnaserver.log.2.gz
├── dlnaserver.log.3.gz
├── dlnaserver.log.4.gz
├── dlnaserver.log.5.gz
├── dlnaserver.log.6.gz
├── dlnaserver.log.7.gz
├── dlnaserver.log.8.gz
├── dlnaserver.log.9.gz
├── file.smb
├── hotplug
├── ietd.log
├── lastlog
├── lighttpd
├── lighttpd.webui.access.log
├── lighttpd.webui.access.log.1.gz
├── lighttpd.webui.access.log.2.gz
├── lighttpd.webui.access.log.3.gz
├── lighttpd.webui.access.log.4.gz
├── lighttpd.webui.error.log
├── linkstation.log
├── linkstation.log.1.gz
├── linkstation.log.2.gz
├── linkstation.log_all.txt
├── log.nmbd
├── log.nmbd.1.gz
├── log.nmbd.2.gz
├── log.nmbd.3.gz
├── log.smbd
├── log.smbd.1.gz
├── log.smbd.2.gz
├── log.smbd.3.gz
├── log.smbd.4.gz
├── messages
├── messages.1.gz
├── messages.10.gz
├── messages.2.gz
├── messages.3.gz
├── messages.4.gz
├── messages.5.gz
├── messages.6.gz
├── messages.7.gz
├── messages.8.gz
├── messages.9.gz
├── messages_all.txt
├── mysql
├── nasapid.log
├── nasapid.log.1.gz
├── onlineupdate.log
├── raidsync
├── replication.log
├── sa
├── samba
├── tmp.log
└── xferlog

9 directories, 67 files


There is no disk error so, backup the data, make sure your firmware is up to date and reset the unit via the admin page (it doesn't effect the data)