user14512

I can't seem to figure out if it is possible to backup my unraid server to crashplan pro or not. Is that possible or can it only be used to backup other workstations?

This update seems to have broken one of my unraid servers. After upgrading I got this message: ----[end kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0) I restarted and got this message: floppy0: no floppy controllers found VFS: Insert root floppy and press ENTER I pressed enter and got the first message again. Here's a screenshot: I updated through the GUI and it went through the first time (same as my other server). I was on beta13 before the upgrade. Any ideas on why its saying this message? I copied the upgrade over manually using a windows computer and I get the same message.

Spot on! I used the "Utils" tab and pressed "New Config" like you said and it worked perfectly. It did clear all the drive arrangements though, so it would be good to note the order you had it in before you press new config in case you need to have it in the same order so it doesn't affect any documentation you have.

I am running: unRAID Server Pro version: 5.0-beta12 I replaced one of my 750GB drives with a 3TB (pre-cleared it first) and now the array will not start. Normally something like this wouldn't be a problem since I currently do not use parity. I have tried to use parity before, but I was unsuccessful (really slow but I'm not worried about that right now). So I thought removing the 3TB i wanted to use for parity would work as a data drive (it didn't) So here is the process I went through before this occurred: 1. Physically added a 3TB drive to my current 20 drive (not including parity) server 2. Pre-cleared it 3. Added it to parity and ran a test sync (went slow so I gave up on that plan for now) 4. So I removed it from the array and just let it sit in my server and not my array (everything works for weeks) 5. Removed the 750GB drive from the array (than removed it from the server after shutting it down) 6. Physically add ANOTHER 3TB to get it started on pre-clear (I don't actually start the pre-clear yet) 7. I add the older 3TB drive (the one i tried with parity) to the spot where I removed the 750GB. 8. Now it won't let me start the array and it states "Too many wrong and/or missing disks!" This would make sense to me if I was using parity but I'm not. I've attached my syslog. Is there any way I can just clear the device information and redo the entire array? Since I'm not using parity i don't really see how that could be a problem. syslog9-12-11.txt

Please read below for context: Well, I figured it out. I moved the hard drive that was producing all the errors to another bay and the errors are no longer there and I was able to delete all the files that I wanted. I am also now able to create files on that disc as well. Thanks again for all your help! Before figuring out the problem I posted:

I already ran reiserfsck and it didn't report any errors that I could see. Here's what it said:

I don't see any that are read only but I'll post the output just to be sure: Should I just run the --fix-fixable switch or the --rebuild-tree switch on the disc that these files are located anyway?

reisefsck didn't find any problems. It seems to me its a permission problem. I tried to delete it via midnight commander and it said "Read-Only file system (30)" I believe its a permissions problem, but for some reason I can't gain permission of those files.... Any idea where I should go from here?

About half the time I access the unraid interface from firefox (not sure what IE does cause my IE is broken) its all glitched out and I have to refresh it for it to be usable. I've attached a screenshot. Does anybody know why this would be happening and if I should be worried about my unraid OS? Or is this normal for beta?

Well unmounting the disc and running that command didn't fix it Does anybody have any idea why the files can't be deleted? I've tried running "new permissions" and that didn't help either. If I don't figure it out soon I'll probably just backup the files and reformat that drive.

Yep, you were right. Now I have a different error: What am I doing wrong?

I am trying to delete several files from one of my disc (3 of 20) and for some reason after I delete them (from my computer) they dissapear instantly (it normally takes a while). Than after refreshing the page they show up again. I'm not sure what is going on. I tried running the following command via telnet but it didn't work: reiserfsck --fix-fixable /dev/sdd I found this command via a guide here: http://lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems I noticed on the command on that page it says "md1" for the disc and my is called "sdd". So I changed that part of it and it spits out this error: Does anybody have any idea's what could cause this? Thanks in advance!