sacretagent
-
Posts
943 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by sacretagent
-
-
My First Build
Inside the thing: Font and Back
Front and Top
Side and front while in my desk running
Case is a NZTX, which has 2 times 4 bays good for 8 drives (with Fans)
Only 7 drives there for the moment as I have broken one of the plastics to hold the drive, I ordered 2 new ones
Added one 3 * 5.25” to 4 hotswap bay (no clue who makes them but it was the cheapest I found in Pantip Plaza)
Motherboard is an ASUS P5B-Plus Vista edition
CPU: E6550 core 2 duo
3 GB Corsair DDR2 800
6 onboard 3gbs sata ports through an intel ICH8 (I think) (parity on port 6)
2 X Adaptec 2 port PCI-X adapters (1220)
1 X JBM micro sata port (has the cache drive)
1 X Esata port on the JBM Micro too … ordered on Ebay an Esata to sata cable to get that one missing drive attached
8 x 1 TB EADS/EACS/EARS WD GREEN
2 x Hitatchi 7200 rpm 1 TB (1 = parity drive )
1 x 500 GB Samsung (Cache Drive )
PSU = Cooler Master 550 W
Whole thing is running Unraid Pro version 5 Beta 2
Puppy is now ready to get filled with data … with my end of the year bonus, am I going to start to put 2 TB drives in the thing (Start with Exchange of the parity drive and 1 Data Drive )
Still have 2 other computers with an Intel raid 5 running but can not change those for Linux as family uses them
Pretty happy with my setup ... can still add one more adaptec if necessay LOL... will need another case then though
did my best to keep the wiring nice... but i am not an expert as some of you guys
-
Thx for the help Joe.L
the rebuild tree solved the issue
ended up with a lost+found folder though
can not access that folder from the gui though
can access it from putty ... only files and folders with a bunch of numbers as name in there
is it safe to just rm -rf lost+found ?
the parity led is still green after the file system check ... so i can just go ahead and add the new drive ?
-
Thanks both for the info
i ran reiserfscheck and it found a lot of problems
it said i had to run --rebuild-tree to solve the issues
running that now...
if i am correct i will probably end up with a lost+found folder on that drive
will my parity still be intact ? or do i need to run first a parity check (with our without correction through unmenu or just from the normal menu?)
i have a new EADS 1TB disk that i want to add after this is done .....
in the hollidays the plan is to change the parity drive to a 2 TB and then add a few 2 TB drives
any suggestions on a good drive ? i have 2 hitachi's in the box and they seem to run fine .... only slightly hotter then the WD's... although they broke a few times my Intel raid 5 on one of my 2 other computers with intel raid 5 of 6 x 1 TB disks each ...all EADS and EACS (now) ... never had problems with these... i had one failed on me after about 3 years which i tried to replace by the EARS but boy did that also give problems ... i checked the ears a few times with smart and he passes every time so i think he is not bad ... but still he seems to cause nothing else then problems... if he screws up one more time then i will use him as a download disk ... (pity though to use such a large disk for that)
anyway i like unraid and i am planning to build a big box soon (20 drives) so i can eliminate the intel raid 5 setups so that these disks will not have to spin all day ....
-
hi all
I am having a problem and i guess it is related to those damn EARS 4K drives
i added one to my existing array filled it up to 800 gb and from then on i have nothing else then troubles
i have SHFS going up to 100% of processor usage the moment i try to access the share
and i get these in my logs
Dec 17 21:34:50 p5bplus kernel: REISERFS warning: reiserfs-5082 is_leaf: free space seems wrong: level=1, nr_items=7, free_space=1936 rdkey Dec 17 21:34:50 p5bplus kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 51760081. Fsck? Dec 17 21:34:50 p5bplus kernel: REISERFS warning: reiserfs-5082 is_leaf: free space seems wrong: level=1, nr_items=7, free_space=1936 rdkey Dec 17 21:34:50 p5bplus kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 51760081. Fsck? Dec 17 21:34:50 p5bplus kernel: REISERFS warning: reiserfs-5082 is_leaf: free space seems wrong: level=1, nr_items=7, free_space=1936 rdkey Dec 17 21:34:50 p5bplus kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 51760081. Fsck? Dec 17 21:34:50 p5bplus kernel: REISERFS warning: reiserfs-5082 is_leaf: free space seems wrong: level=1, nr_items=7, free_space=1936 rdkey Dec 17 21:34:50 p5bplus kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 51760081. Fsck? Dec 17 21:34:50 p5bplus kernel: REISERFS warning: reiserfs-5082 is_leaf: free space seems wrong: level=1, nr_items=7, free_space=1936 rdkey Dec 17 21:34:50 p5bplus kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 51760081. Fsck? Dec 17 21:34:50 p5bplus kernel: REISERFS warning: reiserfs-5082 is_leaf: free space seems wrong: level=1, nr_items=7, free_space=1936 rdkey Dec 17 21:34:50 p5bplus kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 51760081. Fsck? Dec 17 21:34:50 p5bplus kernel: REISERFS warning: reiserfs-5082 is_leaf: free space seems wrong: level=1, nr_items=7, free_space=1936 rdkey Dec 17 21:34:50 p5bplus kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 51760081. Fsck? Dec 17 21:34:50 p5bplus kernel: REISERFS warning: reiserfs-5082 is_leaf: free space seems wrong: level=1, nr_items=7, free_space=1936 rdkey Dec 17 21:34:50 p5bplus kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 51760081. Fsck? Dec 17 21:34:50 p5bplus kernel: REISERFS warning: reiserfs-5082 is_leaf: free space seems wrong: level=1, nr_items=7, free_space=1936 rdkey Dec 17 21:34:50 p5bplus kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 51760081. Fsck? Dec 17 21:34:50 p5bplus kernel: REISERFS warning: reiserfs-5082 is_leaf: free space seems wrong: level=1, nr_items=7, free_space=1936 rdkey Dec 17 21:34:50 p5bplus kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 51760081. Fsck? Dec 17 21:34:50 p5bplus kernel: REISERFS warning: reiserfs-5082 is_leaf: free space seems wrong: level=1, nr_items=7, free_space=1936 rdkey Dec 17 21:34:50 p5bplus kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 51760081. Fsck? Dec 17 21:34:50 p5bplus kernel: REISERFS warning: reiserfs-5082 is_leaf: free space seems wrong: level=1, nr_items=7, free_space=1936 rdkey Dec 17 21:34:50 p5bplus kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 51760081. Fsck? Dec 17 21:34:50 p5bplus kernel: REISERFS warning: reiserfs-5082 is_leaf: free space seems wrong: level=1, nr_items=7, free_space=1936 rdkey Dec 17 21:34:50 p5bplus kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 51760081. Fsck?
i have some experience with linux and i have read a lot already but i can not really find a reason for above in the logs
i tried to do a filecheck on the disk md4 (which is the EARS 1 GB drive )
but ended up with more problems (disk was disabled by unraid)
so i cleared the disk again and let the array rebuild on the same disk again but the problem still persists
so i would like to know if there is something i can do to save my data ?
and how can i get this damn disk to work with unraid ?
would adding the plug on the disk help with my problem ?
please let me know if there is anything else what you need to troubleshoot or what i can do more ?
-
hi
unraid 5 beta 2 running
installed unmenu and everything works except from the package manager
every time i go to the package manager .. i get the screen with no packages and i got this in syslog
Dec 13 22:48:35 p5bplus unmenu[1559]: mkdir: cannot create directory `/boot/packages\r/': Invalid argument Dec 13 22:48:35 p5bplus unmenu[1559]: mv: cannot move `/boot/unmenu/airvideo-unmenu-package.conf' to `/boot/packages\r/': Not a directory Dec 13 22:48:35 p5bplus unmenu[1559]: mv: cannot move `/boot/unmenu/apcupsd-unmenu-package.conf' to `/boot/packages\r/': Not a directory Dec 13 22:48:35 p5bplus unmenu[1559]: mv: cannot move `/boot/unmenu/apcupsd3-unmenu-package.conf' to `/boot/packages\r/': Not a directory Dec 13 22:48:35 p5bplus unmenu[1559]: mv: cannot move `/boot/unmenu/bwm-ng-unmenu-package.conf' to `/boot/packages\r/': Not a directory Dec 13 22:48:35 p5bplus unmenu[1559]: mv: cannot move `/boot/unmenu/compiler-unmenu-package.conf' to `/boot/packages\r/': Not a directory Dec 13 22:48:35 p5bplus unmenu[1559]: mv: cannot move `/boot/unmenu/cpio-unmenu-package.conf' to `/boot/packages\r/': Not a directory Dec 13 22:48:35 p5bplus unmenu[1559]: mv: cannot move `/boot/unmenu/cxxlibs-unmenu-package.conf' to `/boot/packages\r/': Not a directory Dec 13 22:48:35 p5bplus unmenu[1559]: mv: cannot move `/boot/unmenu/dmidecode-unmenu-package.conf' to `/boot/packages\r/': Not a directory Dec 13 22:48:35 p5bplus unmenu[1559]: mv: cannot move `/boot/unmenu/ds_store_cleanup-unmenu-package.conf' to `/boot/packages\r/': Not a directory Dec 13 22:48:35 p5bplus unmenu[1559]: mv: cannot move `/boot/unmenu/encfs-unmenu-package.conf' to `/boot/packages\r/': Not a directory Dec 13 22:48:35 p5bplus unmenu[1559]: mv: cannot move `/boot/unmenu/file-unmenu-package.conf' to `/boot/packages\r/': Not a directory Dec 13 22:48:35 p5bplus unmenu[1559]: mv: cannot move `/boot/unmenu/hdparm-9.27-unmenu-package.conf' to `/boot/packages\r/': Not a directory Dec 13 22:48:35 p5bplus unmenu[1559]: mv: cannot move `/boot/unmenu/htop-unmenu-package.conf' to `/boot/packages\r/': Not a directory Dec 13 22:48:35 p5bplus unmenu[1559]: mv: cannot move `/boot/unmenu/iftop-unmenu-package.conf' to `/boot/packages\r/': Not a directory Dec 13 22:48:35 p5bplus unmenu[1559]: mv: cannot move `/boot/unmenu/inotify-tools-unmenu-package.conf' to `/boot/packages\r/': Not a directory Dec 13 22:48:35 p5bplus unmenu[1559]: mv: cannot move `/boot/unmenu/istat-unmenu-package.conf' to `/boot/packages\r/': Not a directory Dec 13 22:48:35 p5bplus unmenu[1559]: mv: cannot move `/boot/unmenu/jre-unmenu-package.conf' to `/boot/packages\r/': Not a directory Dec 13 22:48:35 p5bplus unmenu[1559]: mv: cannot move `/boot/unmenu/lighttpd-unmenu-package.conf' to `/boot/packages\r/': Not a directory Dec 13 22:48:35 p5bplus unmenu[1559]: mv: cannot move `/boot/unmenu/lsof-unmenu-package.conf' to `/boot/packages\r/': Not a directory Dec 13 22:48:35 p5bplus unmenu[1559]: mv: cannot move `/boot/unmenu/mail-ssmtp-unmenu-package.conf' to `/boot/packages\r/': Not a directory Dec 13 22:48:35 p5bplus unmenu[1559]: mv: cannot move `/boot/unmenu/mail_status-unmenu-package.conf' to `/boot/packages\r/': Not a directory Dec 13 22:48:35 p5bplus unmenu[1559]: mv: cannot move `/boot/unmenu/md5deep-unmenu-package.conf' to `/boot/packages\r/': Not a directory Dec 13 22:48:35 p5bplus unmenu[1559]: mv: cannot move `/boot/unmenu/midnight_commander-unmenu-package.conf' to `/boot/packages\r/': Not a directory Dec 13 22:48:35 p5bplus unmenu[1559]: mv: cannot move `/boot/unmenu/monthly-parity-unmenu-package.conf' to `/boot/packages\r/': Not a directory Dec 13 22:48:35 p5bplus unmenu[1559]: mv: cannot move `/boot/unmenu/mysql-unmenu-package.conf' to `/boot/packages\r/': Not a directory Dec 13 22:48:35 p5bplus unmenu[1559]: mv: cannot move `/boot/unmenu/ntfs-3g-2010.3.6-unmenu-package.conf' to `/boot/packages\r/': Not a directory Dec 13 22:48:35 p5bplus unmenu[1559]: mv: cannot move `/boot/unmenu/openssh-unmenu-package.conf' to `/boot/packages\r/': Not a directory Dec 13 22:48:35 p5bplus unmenu[1559]: mv: cannot move `/boot/unmenu/openssl-unmenu-package.conf' to `/boot/packages\r/': Not a directory Dec 13 22:48:35 p5bplus unmenu[1559]: mv: cannot move `/boot/unmenu/p910nd-unmenu-package.conf' to `/boot/packages\r/': Not a directory Dec 13 22:48:35 p5bplus unmenu[1559]: mv: cannot move `/boot/unmenu/pbzip2-unmenu-package.conf' to `/boot/packages\r/': Not a directory Dec 13 22:48:35 p5bplus unmenu[1559]: mv: cannot move `/boot/unmenu/pciutils-unmenu-package.conf' to `/boot/packages\r/': Not a directory Dec 13 22:48:35 p5bplus unmenu[1559]: mv: cannot move `/boot/unmenu/perl-unmenu-package.conf' to `/boot/packages\r/': Not a directory Dec 13 22:48:35 p5bplus unmenu[1559]: mv: cannot move `/boot/unmenu/php-unmenu-package.conf' to `/boot/packages\r/': Not a directory Dec 13 22:48:35 p5bplus unmenu[1559]: mv: cannot move `/boot/unmenu/powerdown-overtemp-unmenu-package.conf' to `/boot/packages\r/': Not a directory Dec 13 22:48:35 p5bplus unmenu[1559]: mv: cannot move `/boot/unmenu/powerdown_ctlaltdel-unmenu-package.conf' to `/boot/packages\r/': Not a directory Dec 13 22:48:35 p5bplus unmenu[1559]: mv: cannot move `/boot/unmenu/proftp-unmenu-package.conf' to `/boot/packages\r/': Not a directory Dec 13 22:48:35 p5bplus unmenu[1559]: mv: cannot move `/boot/unmenu/reiserfsck-3.6.21-unmenu-package.conf' to `/boot/packages\r/': Not a directory Dec 13 22:48:35 p5bplus unmenu[1559]: mv: cannot move `/boot/unmenu/rsync-unmenu-package.conf' to `/boot/packages\r/': Not a directory Dec 13 22:48:35 p5bplus unmenu[1559]: mv: cannot move `/boot/unmenu/ruby-unmenu-package.conf' to `/boot/packages\r/': Not a directory Dec 13 22:48:35 p5bplus unmenu[1559]: mv: cannot move `/boot/unmenu/screen-unmenu-package.conf' to `/boot/packages\r/': Not a directory Dec 13 22:48:35 p5bplus unmenu[1559]: mv: cannot move `/boot/unmenu/smartctl-unmenu-package.conf' to `/boot/packages\r/': Not a directory Dec 13 22:48:35 p5bplus unmenu[1559]: mv: cannot move `/boot/unmenu/socat-unmenu-package.conf' to `/boot/packages\r/': Not a directory Dec 13 22:48:35 p5bplus unmenu[1559]: mv: cannot move `/boot/unmenu/svn-unmenu-package.conf' to `/boot/packages\r/': Not a directory Dec 13 22:48:35 p5bplus unmenu[1559]: mv: cannot move `/boot/unmenu/transmission-unmenu-package.conf' to `/boot/packages\r/': Not a directory Dec 13 22:48:35 p5bplus unmenu[1559]: mv: cannot move `/boot/unmenu/unraid-swapfile-unmenu-package.conf' to `/boot/packages\r/': Not a directory Dec 13 22:48:35 p5bplus unmenu[1559]: mv: cannot move `/boot/unmenu/unraid-web-unmenu-package.conf' to `/boot/packages\r/': Not a directory Dec 13 22:48:35 p5bplus unmenu[1559]: mv: cannot move `/boot/unmenu/unrar-unmenu-package.conf' to `/boot/packages\r/': Not a directory Dec 13 22:48:35 p5bplus unmenu[1559]: mv: cannot move `/boot/unmenu/vim-unmenu-package.conf' to `/boot/packages\r/': Not a directory Dec 13 22:48:35 p5bplus unmenu[1559]: mv: cannot move `/boot/unmenu/zip-unmenu-package.conf' to `/boot/packages\r/': Not a directory
I thought to be smart and created a /boot/packages dir from telnet and moved all package.conf files into that dir but then i still end up with this in the syslog
Dec 13 23:02:23 p5bplus unmenu[1559]: mkdir: cannot create directory `/boot/packages\r/': Invalid argument Dec 13 23:06:54 p5bplus unmenu[1559]: mkdir: cannot create directory `/boot/packages\r/': Invalid argument Dec 13 23:11:41 p5bplus last message repeated 3 times Dec 13 23:15:44 p5bplus unmenu[1559]: mkdir: cannot create directory `/boot/packages\r/': Invalid argument
so now i am stumped ....
guess it is a problem with the script somewhere
did a search on the forums and on google to see what mkdir \r does but didn't figure it out
so hopefully one of you know the solution to this ?
-
just wanted to put this to your attention
started out with the original 3 disk setup
added now 2 disks and both show up Filesystem unkown
everything works though as it is supposed to do... just a small esthetic issue i think
i attached screenshot
running unraid 5.02
-
I'm having this same issue using Beta 2.
Preclear the drive just to make sure. Assign the drive as cache, format it. All writes go directly to the array and not the cache drive.
I made sure all shares are setup to use the cache drive.
Am I missing something?
Was it fixed in beta 2?
Same ISsue here
cache drive not been used by unraid 5.2
he even spins down and sits there doing nothing
will try the share folder trick that was mentioned above
but if this is necessary shouldn't the system have made these folders ?
Pimp Your Rig
in Unraid Compulsive Design
Posted
OOPS ... didn't realise they were that big ... was 01:30 AM when i uploaded them ... reduced the pixels by half