Jump to content

(SOLVED) I can not delete files or make new folder in a unRAID share folders in Windows


airport
Go to solution Solved by JorgeB,

Recommended Posts

Dear all,

 

After run some tasks in unBalance to rearrange my folders in array disks, now I can not deleted or make new files in my unRAID.

I've tried to install Fix Common Problems Plugin, then hit Tools - Docker Safe New Permissions but it can not fix.

In MC of unRAID I can move, delete files.

But in Windows Explore, in Mac Finder I can not edit, delete that files .

So could you please show me how to fix my problems.

Thanks in advance,

 

errror unRAID 1.PNG

1mehien-diagnostics-20221105-1729.zip

Edited by airport
Link to comment
  • airport changed the title to I can not delete files or make new folder in a unRAID share folders in Windows

I am currently using 1 RAID card LSI connected with 2 cable cards (8 ports hdd) to Mainboard Supermicro X9DRi-LN4+/X9DR3-LN4+ , Version REV:1.10 American Megatrends Inc., Version 3.3 BIOS date: Wed 23 May 2018 12:00:00 AM +07 use hdd and use 1 sata port on mainboard to control 1 ssd used as Cache drive. Total I have 24 HDD in array (24 bays slot case) and 1 SSD as cache in sata port in mainboard.

Edited by airport
Link to comment

Here you are:

1. My unRAID case hdd slots

2. SSD cable as my cache disk

3. My LSI RAID card with 2 cable connect to board in front of 24 hdd slots case

4. My 2 cable from RAID card

5. Cable from RAID Card to board in front of 24 hdd slots case

 

Best regards,

 

1. My unRAID case hdd slots

 

1.jpg

 

 

2. SSD cable as my cache disk

 

2.PNG

 

3. My LSI RAID card with 2 cable connect to board in front of 24 hdd slots case

 

3.png

 

 

4. My 2 cable from RAID card

 

4.PNG

 

 

5. Cable from RAID Card to board in front of 24 hdd slots case

 

 

5.PNG

Edited by airport
Link to comment

There is 1 mini sas buit-in main board and one cable pluged to front as picture bellow.

The RAID Card have 2 mini sas and 2 cables pluged to front.

So my case have 3 mini sas cable.

Regards,

 

1. Buit-in mini sas in mainboard

 

6.PNG

 

2. Mini sas cable pluged in front (3 cables)

5.PNG

Edited by airport
Link to comment
  • Solution

OK, HBA errors are gone now, cannot say for sure having the two controllers connect was the reason but there's filesystem corruption on disk13:

 

Nov  5 21:37:19 1mehien kernel: BTRFS error (device md13): bad tree block start, want 1662170136576 have 10747556178053718809
Nov  5 21:37:19 1mehien kernel: BTRFS error (device md13): bad tree block start, want 3682759163904 have 264872832230753434
Nov  5 21:37:19 1mehien kernel: BTRFS error (device md13): bad tree block start, want 3682759163904 have 5416251924624809680
Nov  5 21:37:19 1mehien kernel: BTRFS error (device md13): bad tree block start, want 3682760933376 have 16092232063824817363
Nov  5 21:37:19 1mehien kernel: BTRFS error (device md13): bad tree block start, want 3682760933376 have 680612081581229256
Nov  5 21:37:19 1mehien kernel: BTRFS error (device md13): bad tree block start, want 3682762276864 have 16624447169037219827
Nov  5 21:37:19 1mehien kernel: BTRFS error (device md13): bad tree block start, want 3682762326016 have 431662829089564475
Nov  5 21:37:19 1mehien kernel: BTRFS error (device md13): bad tree block start, want 3682762326016 have 1271150100442318909
Nov  5 21:37:19 1mehien kernel: BTRFS error (device md13): bad tree block start, want 1662170136576 have 4703661163413750054
Nov  5 21:37:19 1mehien kernel: BTRFS: error (device md13: state A) in __btrfs_cow_block:442: errno=-5 IO failure
Nov  5 21:37:19 1mehien kernel: BTRFS info (device md13: state EA): forced readonly

 

Best bet is to backup and reformat, disks 14, 22 and 23 show some data corruption detected, you should run a scrub on all 3.

Link to comment
32 minutes ago, airport said:

By the way, can I take out the hdd13, clean all partitions and after that put it back to unRAID to restore data from parity disk? Because disk 13 is 10TB so if I move data to other it'll take a very long time.

Probably not.    It all depends on exactly how the corruption occurred, and therefore whether parity was updated to include this corruption.

  • Like 1
Link to comment
2 minutes ago, itimpi said:

Probably not.    It all depends on exactly how the corruption occurred, and therefore whether parity was updated to include this corruption.

Thank you for your answer.

I'll show you the result after moved data.

And would you please show me how to to run scrub on disk 14,22,23 to fix data corruption detected.

Link to comment
8 minutes ago, JorgeB said:

On the main GUI page click on the disk and then scroll down to the scrub section.

Yes, Sir.

Disk 22, disk 23 is scrub with speed rate about 160MB/s but disk 14 it can not run as other. I run scrub in disk 14 so quick (about 3s) and show no errors, I don't know what happen with that disk

Link to comment

Pulling the disk won't fix anything since the emulated disk will have the same problem:

 

Nov  6 17:25:09 1mehien kernel: BTRFS info (device md13: state EA): forced readonly

 

P.S. disk14 is also showing issues now:

Nov  6 17:13:46 1mehien kernel: BTRFS info (device md14: state EA): forced readonly

 

21 hours ago, JorgeB said:

Best bet is to backup and reformat

For both now.

  • Like 1
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...