Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Newbie growing pains - cant transfer data to unraid server

Featured Replies

Hi all,

 

after reading about it i decided to give it a try and try out unraid for my server. i've been using just an winxp box for the longest time in the closet with no issues.

 

i just got my new parts and put it all together, struggled getting it to boot first and what not, but i got all that sorted out thru the forums and the wiki entries, but now im at the point where im trying to copy stuff over to the server and it just keeps craping out after a period of time.

 

i connected one of my 1.5TB drives thru an eSATA enclosure to my HTPC and left the files copying when i went to work hoping it was all gonna be finished once i get back 12 hours later. to my suprise it crapped out after 700-800GB of data or so and the array was crapped out with the temp showing 0degrees and i wasnt able to do anything other then hard reset.

 

so ever since i've been playing with it and just cant get nothing going anymore. keeps crapping out after copying files over for a few minutes.

 

i figured out how to post the syslog file so here it is and a screenshot of the drive

 

the specs for the system

mobo : gigabyte GA-770TA-UD3 ( 8 sata ports including sata3 6Gb/s and USB3.0)

cpu: sempron 140

memory: OCS gold series 2GB

HD: Wd 1.5TB green series (will add more once i empty the old drives)

USB Flash: Kingston datatraveler 2 - 2GB

syslog.zip

Capture.PNG.b527ad77026e034a935f1d4b6417b0a5.PNG

Hi all,

 

after reading about it i decided to give it a try and try out unraid for my server. i've been using just an winxp box for the longest time in the closet with no issues.

 

i just got my new parts and put it all together, struggled getting it to boot first and what not, but i got all that sorted out thru the forums and the wiki entries, but now im at the point where im trying to copy stuff over to the server and it just keeps craping out after a period of time.

 

i connected one of my 1.5TB drives thru an eSATA enclosure to my HTPC and left the files copying when i went to work hoping it was all gonna be finished once i get back 12 hours later. to my suprise it crapped out after 700-800GB of data or so and the array was crapped out with the temp showing 0degrees and i wasnt able to do anything other then hard reset.

 

so ever since i've been playing with it and just cant get nothing going anymore. keeps crapping out after copying files over for a few minutes.

 

i figured out how to post the syslog file so here it is and a screenshot of the drive

 

the specs for the system

mobo : gigabyte GA-770TA-UD3 ( 8 sata ports including sata3 6Gb/s and USB3.0)

cpu: sempron 140

memory: OCS gold series 2GB

HD: Wd 1.5TB green series (will add more once i empty the old drives)

USB Flash: Kingston datatraveler 2 - 2GB

Your disk is suffering from massive "write" errors (basically it is not responding to the disk controller).

 

It could be a bad SATA cable to the disk, a bad power cable to the disk (or a loose cable of either power or data)

Or, it could be a bad drive.

 

To see if the drive is responding at all, type:

smartctl -a -d ata /dev/sda

and post the output.

Small sample of the errors in your syslog:

Mar 10 13:00:16 unRaid kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen

Mar 10 13:00:16 unRaid kernel: ata3.00: failed command: WRITE DMA EXT

Mar 10 13:00:16 unRaid kernel: ata3.00: cmd 35/00:18:9f:30:04/00:00:5e:00:00/e0 tag 0 dma 12288 out

Mar 10 13:00:16 unRaid kernel:          res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)

Mar 10 13:00:16 unRaid kernel: ata3.00: status: { DRDY }

Mar 10 13:00:16 unRaid kernel: ata3: hard resetting link

Mar 10 13:00:26 unRaid kernel: ata3: softreset failed (device not ready)

Mar 10 13:00:26 unRaid kernel: ata3: hard resetting link

Mar 10 13:00:36 unRaid kernel: ata3: softreset failed (device not ready)

Mar 10 13:00:36 unRaid kernel: ata3: hard resetting link

Mar 10 13:00:46 unRaid kernel: ata3: link is slow to respond, please be patient (ready=0)

Mar 10 13:01:11 unRaid kernel: ata3: softreset failed (device not ready)

Mar 10 13:01:11 unRaid kernel: ata3: limiting SATA link speed to 1.5 Gbps

Mar 10 13:01:11 unRaid kernel: ata3: hard resetting link

Mar 10 13:01:16 unRaid kernel:  error

Mar 10 13:01:16 unRaid kernel: handle_stripe write error: 1591816512/1, count: 1

Mar 10 13:01:16 unRaid kernel: md: disk1 write error

Mar 10 13:01:16 unRaid kernel: handle_stripe write error: 1591816520/1, count: 1

Mar 10 13:01:16 unRaid kernel: md: disk1 write error

Mar 10 13:01:16 unRaid kernel: handle_stripe write error: 1591816528/1, count: 1

Mar 10 13:01:16 unRaid kernel: md: disk1 write error

Mar 10 13:01:16 unRaid kernel: handle_stripe write error: 1591816536/1, count: 1

Mar 10 13:01:16 unRaid kernel: md: disk1 write error

Mar 10 13:01:16 unRaid kernel: handle_stripe write error: 1591816544/1, count: 1

Mar 10 13:01:16 unRaid kernel: md: disk1 write error

Mar 10 13:01:16 unRaid kernel: handle_stripe write error: 1591816552/1, count: 1

Mar 10 13:01:16 unRaid kernel: md: disk1 write error

Mar 10 13:01:16 unRaid kernel: handle_stripe write error: 1591816560/1, count: 1

Mar 10 13:01:16 unRaid kernel: md: disk1 write error

Mar 10 13:01:16 unRaid kernel: handle_stripe write error: 1591816568/1, count: 1

Mar 10 13:01:16 unRaid kernel: md: disk1 write error

  • Author

Your disk is suffering from massive "write" errors (basically it is not responding to the disk controller).

 

It could be a bad SATA cable to the disk, a bad power cable to the disk (or a loose cable of either power or data)

Or, it could be a bad drive.

 

To see if the drive is responding at all, type:

smartctl -a -d ata /dev/sda

and post the output.

Small sample of the errors in your syslog:

Mar 10 13:00:16 unRaid kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen

Mar 10 13:00:16 unRaid kernel: ata3.00: failed command: WRITE DMA EXT

Mar 10 13:00:16 unRaid kernel: ata3.00: cmd 35/00:18:9f:30:04/00:00:5e:00:00/e0 tag 0 dma 12288 out

Mar 10 13:00:16 unRaid kernel:          res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)

Mar 10 13:00:16 unRaid kernel: ata3.00: status: { DRDY }

Mar 10 13:00:16 unRaid kernel: ata3: hard resetting link

Mar 10 13:00:26 unRaid kernel: ata3: softreset failed (device not ready)

Mar 10 13:00:26 unRaid kernel: ata3: hard resetting link

Mar 10 13:00:36 unRaid kernel: ata3: softreset failed (device not ready)

Mar 10 13:00:36 unRaid kernel: ata3: hard resetting link

Mar 10 13:00:46 unRaid kernel: ata3: link is slow to respond, please be patient (ready=0)

Mar 10 13:01:11 unRaid kernel: ata3: softreset failed (device not ready)

Mar 10 13:01:11 unRaid kernel: ata3: limiting SATA link speed to 1.5 Gbps

Mar 10 13:01:11 unRaid kernel: ata3: hard resetting link

Mar 10 13:01:16 unRaid kernel:  error

Mar 10 13:01:16 unRaid kernel: handle_stripe write error: 1591816512/1, count: 1

Mar 10 13:01:16 unRaid kernel: md: disk1 write error

Mar 10 13:01:16 unRaid kernel: handle_stripe write error: 1591816520/1, count: 1

Mar 10 13:01:16 unRaid kernel: md: disk1 write error

Mar 10 13:01:16 unRaid kernel: handle_stripe write error: 1591816528/1, count: 1

Mar 10 13:01:16 unRaid kernel: md: disk1 write error

Mar 10 13:01:16 unRaid kernel: handle_stripe write error: 1591816536/1, count: 1

Mar 10 13:01:16 unRaid kernel: md: disk1 write error

Mar 10 13:01:16 unRaid kernel: handle_stripe write error: 1591816544/1, count: 1

Mar 10 13:01:16 unRaid kernel: md: disk1 write error

Mar 10 13:01:16 unRaid kernel: handle_stripe write error: 1591816552/1, count: 1

Mar 10 13:01:16 unRaid kernel: md: disk1 write error

Mar 10 13:01:16 unRaid kernel: handle_stripe write error: 1591816560/1, count: 1

Mar 10 13:01:16 unRaid kernel: md: disk1 write error

Mar 10 13:01:16 unRaid kernel: handle_stripe write error: 1591816568/1, count: 1

Mar 10 13:01:16 unRaid kernel: md: disk1 write error

 

tnx for the reply,

 

i shut the box off earlier before leaving for work and i just got back home to try out the command u suggested, but when i turned the box on the unraid menu said the hard drive was missing...so i tried switching cables, still nothing. took it out to my other box and tried running the WD boot utility and that thing can't even find the drive when it boots.

so my guess, this drive is dead, the stupid thing is not even 3 months old WD 1.5TB Caviar Green....

i have another exact same drive i was planning on putting inside there after filling up the first one, i hope the 2nd one doesnt end up the same. i'll be doing an RMA tomorrow and be waiting for a new one i guess.

 

in the mean time im gonna empty my other 1.5TB between all my computers and throw the empty drive in there... and try it all again, hope with better results lol

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.