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.

[SOLVED] Can't copy to array

Featured Replies

Ok heres my Problem:

 

I want to copy some Isos (around 50gb) to my array. But Windows 7 says INSTANTLY "Theres a problem accessing \\tower\Filme Make shure you are connected to the network and try again" So I spammed the "try again" button, spun up all disks, but no change.

The strange thing is that alle the time unraid is responsive, I can even browse to my shares!

 

Then I copy the file directly to a disk 3 (That's the disk unraid want to copy it because of the Allocation method most-free) and the same error on windows.

 

But now I try it to copy on another disk and hey it's copying!

 

Before I copied ~1,5TB Data on disk 3 and at copying (I was about to copy 2TB) the error message came up.

 

After reboot I noticed read and writes on that disk: 54485 reads and 49 writes.

 

The Syslog shows this and I don't know what that means:

Sep 16 15:52:20 Tower shfs/user: duplicate object: /mnt/disk6/Filme/Transformers (2007).ISO

Sep 16 15:53:37 Tower last message repeated 6 times

Sep 16 15:55:00 Tower last message repeated 6 times

Sep 16 15:56:38 Tower last message repeated 2 times

 

Why duplicate ?

 

My Share hast Split level 3

like

-disk

-sharename (Filme)

-Moviename

Allocation method: most-free

 

Network Setup: Windows 7 mashine -> WRT 54GS Linksys Router -> unRaid

 

The disk is a WD20ears unjumpered and successfully prelcear without errors.

Syslog.txt

Haven't completely looked through the syslog yet...but disk3 is identified as "hda" as an ide drive (PIO mode)

Tower kernel: Probing IDE interface ide0...

Tower kernel: pata_marvell 0000:01:00.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17

Tower kernel: pata_marvell 0000:01:00.1: setting latency timer to 64

Tower kernel: scsi0 : pata_marvell

Tower kernel: scsi1 : pata_marvell

Tower kernel: ata1: PATA max UDMA/100 cmd 0xe040 ctl 0xe030 bmdma 0xe000 irq 17

Tower kernel: ata2: PATA max UDMA/133 cmd 0xe020 ctl 0xe010 bmdma 0xe008 irq 17

Sep 16 15:40:12 Tower kernel: scsi2 : pata_marvell

Sep 16 15:40:12 Tower kernel: scsi3 : pata_marvell

Sep 16 15:40:12 Tower kernel: ata3: PATA max UDMA/100 cmd 0xd040 ctl 0xd030 bmdma 0xd000 irq 17

Sep 16 15:40:12 Tower kernel: ata4: PATA max UDMA/133 cmd 0xd020 ctl 0xd010 bmdma 0xd008 irq 17

 

Line 715: Sep 16 15:40:12 Tower kernel: hda: WDC WD20EARS-14MVWB0, ATA DISK drive

Line 716: Sep 16 15:40:12 Tower kernel: hda: host max PIO4 wanted PIO255(auto-tune) selected PIO4

Line 717: Sep 16 15:40:12 Tower kernel: hda: UDMA/100 mode selected

Line 764: Sep 16 15:40:12 Tower kernel: hda: max request size: 512KiB

Post your complete hardware as well....add-on cards etc.

  • Author

Mainboard: Asus E35M1-M AMD E350 µATX http://www.asus.com/Motherboards/AMD_CPU_on_Board/E35M1M/

SATA Controller: 2x http://www.asrock.com/mb/spec/Card.us.asp?Model=SATA3%20Card (But the HDD is on the onboard controller)

Power: 400W bequiet! Straight Power E8 80+ Bronze

RAM: 2GB Kingston ValueRAM DDR3-1066 DIMM CL7 Single

 

Parity: WD20EARS

Disk 1: WD20EARS

Disk 3: WD20EARS

Disk 6: WD1502FYPS

Disk 7: WD15EADS

unRaid Beta 12a

 

 

Also...your syslog reports: (version 5.0-beta12a)

Sep 16 18:32:18 Tower emhttp: Copyright © 2005-2011, Lime Technology, LLC

Sep 16 18:32:18 Tower emhttp: Pro key detected, GUID: 1B1C-1AB1-AA00-000000000213

Sep 16 18:32:18 Tower emhttp: get_config_idx: fopen /boot/config/flash.cfg: No such file or directory - assigning defaults

Sep 16 18:32:18 Tower emhttp: shcmd (1): udevadm settle

 

 

Mine: (version 4.7)

Aug 31 20:26:16 Tower emhttp: Copyright © 2005-2011, Lime Technology, LLC

Aug 31 20:26:16 Tower emhttp: Pro key detected, GUID: 0930-6544-A6E4-F0A0B7AC1286

Aug 31 20:26:16 Tower emhttp: shcmd (1): udevadm settle

Aug 31 20:26:16 Tower emhttp: Device inventory:

Also...your syslog reports: (version 5.0-beta12a)

Sep 16 18:32:18 Tower emhttp: Copyright © 2005-2011, Lime Technology, LLC

Sep 16 18:32:18 Tower emhttp: Pro key detected, GUID: 1B1C-1AB1-AA00-000000000213

Sep 16 18:32:18 Tower emhttp: get_config_idx: fopen /boot/config/flash.cfg: No such file or directory - assigning defaults

Sep 16 18:32:18 Tower emhttp: shcmd (1): udevadm settle

 

 

Mine: (version 4.7)

Aug 31 20:26:16 Tower emhttp: Copyright © 2005-2011, Lime Technology, LLC

Aug 31 20:26:16 Tower emhttp: Pro key detected, GUID: 0930-6544-A6E4-F0A0B7AC1286

Aug 31 20:26:16 Tower emhttp: shcmd (1): udevadm settle

Aug 31 20:26:16 Tower emhttp: Device inventory:

 

 

Run Check Disk on the flash in a Windows machine.

  • Author

Thanks for the replies. I try to check disk USB stick and check the disk filesystem of disk 3.

But I have to wait until my preclear is finished. I don't want to cancel it. So I can try it tomorrow night I hope.

  • Author

 

It reports:

 

reiserfs_open: the reiserfs superblock cannot be found on /dev/sdc.

Failed to open the filesystem.

 

If the partition table has not been changed, and the partition is

valid  and  it really  contains  a reiserfs  partition,  then the

superblock  is corrupted and you need to run this utility with

--rebuild-sb.

Not good.

  • Author

That sounds not good :( ahhh

 

How bad is it ?

first question did you run it on "md3"?

 

if not, do so and post the results.

 

also - if it is no bad superblock, post a new thread with the issue and see here for an idea where you are headed

http://lime-technology.com/forum/index.php?topic=4021

  • Author

I made a mistake....now it's successfully running:

 

Reiserfs journal '/dev/md3' in blocks [18..8211]: 0 transactions replayed

Checking internal tree.. finished

Comparing bitmaps..vpf-10640: The on-disk and the correct bitmaps differs.

Checking Semantic tree:

/Filme/28 Days Later (2002).Isovpf-10680: The file [4 2563] has the wrong block count in the StatData (7), should be (0)               /Unstoppable (2011)/BDMV/finished

3 found corruptions can be fixed when running with --fix-fixable

###########

reiserfsck finished at Sat Sep 17 13:51:55 2011

 

then I used "reiserfsck --fix-fixable /dev/md3":

 

reiserfsck --fix-fixable started at Sat Sep 17 13:53:37 2011

###########

Replaying journal: Done.

Reiserfs journal '/dev/md3' in blocks [18..8211]: 0 transactions replayed

Checking internal tree.. finished

Comparing bitmaps..vpf-10630: The on-disk and the correct bitmaps differs. Will be fixed later.

Checking Semantic tree:

/Filme/28 Days Later (2002).Isovpf-10680: The file [4 2563] has the wrong block count in the StatData (7) - corrected to (0)          /Unstoppable (2011)/BDMV/finished

No corruptions found

There are on the filesystem:

        Leaves 371469

        Internal nodes 2208

        Directories 189

        Other files 2377

        Data block pointers 375607045 (10762496 of them are zero)

        Safe links 0

###########

reiserfsck finished at Sat Sep 17 14:06:47 2011

 

 

So is erverything OK ?

 

It looks like it.  You can run a

reiserfsck --check /dev/md3

to verify.

 

The earlier attempt at reiserfsck failed because the file system is on the first partition, not the base drive device. (you gave it the wrong device name)  It also would have corrupted parity if you had the correct "raw" device, as the repair would have been made, but parity not kept in sync.

 

You were subsequently correct in running it on /dev/md3.

 

Joe L.

  • Author

I checked my USB disk on my Windows mashine and it there were some error which are fixed now.

 

Then I did another reiser check which reportet errors so I tried to fix them and it reports that:

 

 

reiserfsck --fix-fixable started at Sun Sep 18 01:19:54 2011

###########

Replaying journal: Done.

Reiserfs journal '/dev/md3' in blocks [18..8211]: 0 transactions replayed

Checking internal tree.. finished

Comparing bitmaps..vpf-10630: The on-disk and the correct bitmaps differs. Will                                                                              be fixed later.

Checking Semantic tree:

/Filme/Star Wars Episode I Die dunkle Bedrohung (1999).isovpf-10670: The file [4                                                                              2129] has the wrong size in the StatData (43233935360) - corrected to (43233939                                                                            456)

vpf-10680: The file [4 2129] has the wrong block count in the StatData (8) - cor                                                                            finished                                                                                                                                                    No corruptions found

There are on the filesystem:

        Leaves 371265

        Internal nodes 2208

        Directories 189

        Other files 2377

        Data block pointers 375400398 (10555849 of them are zero)

        Safe links 0

###########

reiserfsck finished at Sun Sep 18 01:33:06 2011

 

Is my file Star Wars Episode I ok, again ?

 

After the try to fix it I make again a reiser check and no curroptions were found :)

 

But I cannot copy to that disk :(

Syslog.txt

It looks like it.   You can run a

reiserfsck --check /dev/md3

to verify.

  • Author

It looks like it.   You can run a

reiserfsck --check /dev/md3

to verify.

 

I've done that, as mentioned without errors.

 

For now it seems, that everything works.

So checkdisk on the usb drive and reiserfck+fix made it.

[glow=red,2,300]Excellent - nice work.[/glow]

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.