ok so past few days here is what i have done. went from v4.5 to 4.7 so i can upgrade to 5.0 had problems dg to 4.6 took care of problem was an hpa issue. upgrade to 4.7 everything went ok. then went to 5.0 everything else seemed fine i noticed one disk was not sdX but hdX rather so i went into bios and changed all my settings to achi rather than the ide stuff..that changed the drive to sdX...shortly after that was having trouble connecting to webGUI eventually it connected and said parity is valid. i looked at my monitor connected to UnRaid server and it said "cut: write errror: broken pipe" i rebooted server took a little while to connect to webGUI even though i was able to physically log into server. error gone but now i cannot connect to my share folders i get the windows cannot access it and that i do not have permission. as i sit here and look at my server monitor i see

 

"udevadm settle -timeout of 180 seconds reached, the event gueue contails:/sys/devices/pc10000:00/0000:00:11.0/host1/target1: 0:0/1:0:0:/block/sdb/(931)

 

udevadm settle -timeout of 180 seconds reached, the event gueue contails:/sys/devices/pc10000:00/0000:00:11.0/host3/target3: 0:0/3:0:0:/block/sdd/(937)"

 

no clue what this means.../: thanks for taking your time to look.

 

*update* ok i can see my server under networks on my windows machine and i can see all my share folders but i cant connect to them thats when i get the above error message bout permission

syslog.zip

Wondering if maybe i should use the New Config utility to reset the array disk configuration?? will i lose my stuff? anyone got any ideas why i can see my share folders but cant access them? do you think that is even related to the error messages i was getting?

**update** can access user shares but cant write new info to them

The log shows a lot of errors with ata2=sdb=disk1 and ata4=sdd=disk3. Do these drives share a power splitter?

parity and disk 1 are on same power line and disk 2 and disk 3 are on same power line. none are on a 3rd party splitter if thats what you mean

I would check and reseat the cabling to disk1 and disk3.

ok ill give that a try thanks

ok messing with my power cables did not work. but i ended up running that check disk thing http://lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems on my disc3 drive not on 1 although maybe i should.? its working now i can write to my user shares. so perhaps ill leave everything as is for a while haha. thanks again ill mark this as solved and hopefully this post can go into the internet and i wont have to deal with it again..

 

p.s. i dont want 2 stars..strip me of my rank! ha