Read Error At Md2 Disk1
Error is often false My Buffalo LinkStation was a doorstop Don't waste your money on a new Buffalo Linkstation, when there could be nothing wrong but a need for a firmware update. Even if you "tried that already," you may not have done it right. I learned from calling Buffalo that there's an easy, free fix, for nearly all "read errors." It turns out those are usually false errors, and that the firmware instructions can only be obtained by talking to the nice guy or gal on the phone. Here were the subtle hints that something was wrong: Sources of these messages include email (because I'm signed up for notifications) and the Buffalo NAS Navigator 2 utility. My Buffalo Linkstation could not be found on the network RAID Error Notification HDD error occurred Target array:RAID Array 1 (md2) RAID array can not be mounted. DISK Error Notification HDD error occurred Disk(s) the error occurred:"Disk 1" (sda) READ sector:3841073152 count:4 Disk writing error Continuous backup is recommended Emergency mode -- update the firmware or contact support Sometimes the orange light was flashing, sometimes the red light was flashing The Lesson: Call Buffalo First! Buffalo Linkstation Read Errors are often false, says one of their reps while on the phone with me. "Usually, once we have the customer update the firmware, they don't call back." But hey, it's not so easy to update the firmware. The instructions I found online were insufficient. Once I called Buffalo, I found the rep to be quick with more involved instructions. Then, once the firmware was updating, he gave me a case number, told me it might take about twenty minutes for the firmware update to complete, and that I should call him back if there's still a problem. My bad luck: It didn't work for me In my case, the firmware update didn't solve the problem. Now the unit was working for a while, then powering down in order to secure the data. Both hard drives were bad, says the Buffalo rep. But he said it's unusual. Notes: Mine is the LS-WX6.0TL/R1. That's the 6TB (2 x 3TB) LinkStation Duo Media Server (NAS) I don't use this f
Technology - unRAID Server Community » Legacy Support (unRAID 5 and Older) » General Support (V5 and Older) » A bad disk & unformatted drive(s) « previous next » Send this topic Print Pages: [1] 2 Go Down Author Topic: A bad disk & unformatted drive(s) (Read 2331 times) DosSpider Member Posts: 10 A bad disk & unformatted drive(s) « on: December 03, 2011, 10:12:11 AM » This may have gotten posted already, but I don't see it, sorry if it's a repost.I had a disk go bad and didn't realize it (life gotten somewhat in the way of keeping tabs on my server). I noticed when I started seeing http://www.geekaroundthehouse.com/2013/08/buffalo-linkstation-read-error-is-often.html data missing on the network shares. Looks like the server is now seeing ther other (believed to be good) disks as Unformatted. I've poked around on the forums and wiki a little bit and it seems like the server may have just had a problem mounting the reiserfs which is causing the drives to show up as unformated? Kinda hoping that there's a solution here that doesn't involve losing the data on the unformatted disks. http://lime-technology.com/forum/index.php?topic=17047.0 I see on the wiki that there maybe be a way to repair the FS? Basically just looking for some help getting pointed in the right direction on what to do. Right now the array is stopped, server is still running, all drives are still present in same configuration.Looking for what I should do first here. I don't want to do the wrong thing and lose data if I don't have to.Running build 4.5.3, posted devices screenshot and syslog.disk2 shows up as bad. First time I tried to start the array disk1 showed up as unformatted. Last time I tried to start the array disk1 and disk5 showed up as unformatted.Thanks in advance for any help or assistance with where to look for solutions. syslog-2011-12-03.txt (107.56 kB - downloaded 59 times.) Unraid Devices.png (29.6 kB, 1248x470 - viewed 195 times.) Logged Joe L. Global Moderator Hero Member Posts: 18900 Re: A bad disk & unformatted drive(s) « Reply #1 on: December 03, 2011, 11:34:48 AM » I think a powerdown and reboot is in order.The syslog does not show how the drives are being initially identified. Whatever you do, do NOT press the "Format" button. It would only complicate your issues. Logged For help: check out the wiki: http://lime-technology.com/wiki/index.php?title=UnRAID_Wiki DosSpider Member Posts: 10 Re: A bad disk & unformatted drive(s) « Re
im Standarddesign anzeigen : Ds408 Platte 1 abgestürzt manuel_bo04.05.2009, 19:32Hallo, hab folgendes Problem. Heute ist mir bei meiner DS408 die http://www.synology-forum.de/archive/index.html/t-6675.html 1 Platte angestürzt. ICh hab dann über den Manager einen Neustart ausgeführt. Jetzt blinkt immer das Blaue Licht. Aber sie startet nicht neu. Was soll ich tun? Sind die Daten weg? Warum kann sowas passieren? Danke Supaman04.05.2009, 19:43die DS kann abstürzen, wenns probleme mit dem raid gibt. das sollte zwar nicht sein, ist aber read error leider so. auch wenn man alle platten als basis volumen einrichtet, wird für das betriebesystem + die swap partition trotzdem ein raid-1 eingerichtet. wenn nichts mehr geht, bleibt dir nur noch stecker ziehen - hatte ich bei meiner DS408 dieses wochenende auch. die daten bleiben normalerweise erhalten, allerdings musst du damit rechnen, das die DS read error at wieder abstürzt... am besten alle daten der betreffenden platte sichern und auswechseln. manuel_bo04.05.2009, 19:46sorry doppelpost manuel_bo04.05.2009, 19:47Hallo, hier mal das Protokoll Information 2009/05/04 20:52:52 admin User [admin] logged in [Management] from Information 2009/05/04 20:51:01 admin User [admin] logged in [Management] from Information 2009/05/04 20:50:01 admin Windows file service was started. Information 2009/05/04 20:49:50 admin System started to boot up. Information 2009/05/04 20:29:56 admin Windows file service was stopped. Information 2009/05/04 20:29:54 admin System started counting down to reboot. Information 2009/05/04 20:29:33 admin User [admin] logged in [Management] from Information 2009/05/04 20:27:49 admin User [admin] logged in [Management] from Error 2009/05/04 20:26:03 admin Read error at md2 disk1 sector 1612484543. Error 2009/05/04 20:26:01 admin Read error at md2 disk1 sector 1612484535. Error 2009/05/04 20:26:00 admin Read error at md2 disk1 sector 1612484599. Error 2009/05/04 20:25:59 admin Read error at md2 disk1 sector 1612484591. Error 2009/05/04 20:25:58 admin Read error at md2 disk1 sector 1612484583. Error 2009/05/04 20:25:57 admin Read error at md2 disk1 s