grandan

Finally got the lost+found folder deleted using rm -rf /mnt/disk11/lost+found/. Thanks to all for your help!!

I tried rm "lost+found" via telnet and was told the directory did not exist; do I have to specify a particular drive? If so, how do I do that?

OK, finished the tree rebuild overnight and the drive now appears to be performing normally. I do have an empty lost+found file that I can't seem to delete so I may do the reformat on top of what I've done so far if I can't figure out how to get rid of it. Trurl, thanks very much for your guidance!

OK, ran fixable and attached report resulted. Do you concur that I now run --rebuild-tree ? fix_fixable_report.txt

OK, ran reiserfsck; copy attached. Do you concur that I should run the --fix-fixable command? reiserfsck_output.txt

Sorry about post in v6. I do not need any data on the new drive.

Unraid 5.06. I had a drive go bad recently. I was having write failures. SMART showed it failing reallocated Sector Ct with 635. I could still read from the drive so I copied all my files from it to another drive that had sufficient space. Once all the files were copied to the other drive, I attempted to delete the files from the defective drive but I could not. I replaced the drive with a new one after doing preclear and unraid recognized the new drive as a replacement for the old one and copied all the files to the new drive. After the rebuild, I ran parity check and had 5 errors. Now, the new drive shows the same files that were on the old drive but I cannot delete them and I am getting errors as shown in the attached syslog. What do I do now to get the files removed from the drive and get back to normal? syslog.txt

Thanks Gary!

I recently had a motherboard failure and had to replace it. The old MB had seven SATA connections; the new MB has six SATA connections. I use two old PCI 4 port SATA controllers. My case has slots for 15 drives. So, before I had 1 parity disk and 14 data drive slots. I had a drive in the 14th disk slot before but with the new board, I left the last slot unattached to a controller. I moved the data drive that was in data slot 14 to data drive slot 11. When Unraid booted on the new board, it recognized all the data drives but the drive that is now in slot 11 (previously 14) is still identified by Unraid as disk 14. Not a big deal but I can't figure out how to get the disk number changed from 14 to 11. I have stopped the array, unassigned the drive shown as disk 14 and then selected that drive for disk 11 but it will not persist; when I restart the server, Unraid still shows it as 14. What am I missing?

As Info: My P5B..... MB failed a few days ago. I replaced it with a Gigabyte GA-75M-D3H Rev 1.2 with i3-3220 and 8GB of Kingston KHX1600C9D3K2/8GX RAM and everything seems to work just fine.

Thank you Prostuff!!

I see where Tom updated openssl for release v6 to fix heartbleed risk; does v5.05 have heartbleed exposure? If so, will it get fixed?

Since the issue only happens when I manually spin down all drives, and since I almost never do that under normal circumstances, and since most others are not experiencing this problem, I'm just gonna accept it as some sort of quirky anomaly that I can tolerate and avoid by letting the spindown timer run to completion. So I'm just moving on. Thanks again for the help!

Thanks Madbug for the tool tutorial. I ran hdparm -C and sure enough, the disk 14 is spinning after I hit the spindown all disks button. lsof command produced this: root@Tower:~# lsof | grep mnt smbd 1521 root cwd DIR 9,14 1600 2 /mnt/dis k14 smbd 1521 root 30r DIR 9,14 1600 2 /mnt/dis k14 smbd 1522 root 30r DIR 9,14 1600 2 /mnt/dis k14 smbd 1522 root 32r DIR 9,1 2584 2 /mnt/dis k1 smbd 1522 root 33r DIR 9,2 2408 2 /mnt/dis k2 smbd 1522 root 34r DIR 9,12 2808 2 /mnt/dis k12 smbd 1522 root 35r DIR 9,13 568 2 /mnt/dis k13 I have no clue what this means; please assist. Thanks!

I don't use simple features or unmenu, just Tom's stock UI; the only non-stock code on the flash drive is preclear_disk.sh. My rig is a Tom-built 15 disk unit with p5vmdo MB, 4G, dual-core. I have one other disk (#13) on the same Promise SATA card and it behaves properly?? The drive that acts weird is a WDC_WD2002FAEX-007BA0_WD-WMAY03558572 (sdg) 1953514552, drive #14; the drive that acts properly is a Samsung 1TB drive. I've rebooted and the anomaly persists. Like I say, I rarely manually spin down disks so it isn't an issue of concern but remains confounding. I did notice that other posters are also using WD drives that may be acting strange...don't have a clue whether this similarity is important.