Jump to content

leu4life

Members
  • Content Count

    40
  • Joined

  • Last visited

Community Reputation

0 Neutral

About leu4life

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Wow! Not sure what exactly fixed it, but this is what i did and in turn it got fixed. First i googled how to format hdd from the CL. Ended up finding this page. http://ubuntuforums.org/showthread.php?t=267869 - I read through it and ran the command to see if the ssd was actually mounted or not and in fact it was and just didn't say it was in the unassigned devices portion of unraid. i then proceeded to unmount the drive and then delete the partition from the CL. At this point the drive was still showing as it was before so i decided to remove the unassigned device plugin and restart array. After array reboot i could now see the ssd as unformatted so i formatted it as XFS this time instead of BTRFS and it actually mounted!!!!! i then decided to add the script. so far so good. Hope this helps someone else. Although like i said not sure what fixed it, but just glad its now working and a great plugin to boot! thanks!
  2. #!/bin/bash PATH=/usr/local/sbin:/usr/sbin:/sbin:/usr/local/bin:/usr/bin:/bin ## Available variables: # AVAIL : available space # USED : used space # SIZE : partition size # SERIAL : disk serial number # ACTION : if mounting, ADD; if unmounting, REMOVE # MOUNTPOINT : where the partition is mounted # FSTYPE : partition filesystem # LABEL : partition label # DEVICE : partition device, e.g /dev/sda1 # OWNER : "udev" if executed by UDEV, otherwise "user" case $ACTION in 'ADD' ) // do your stuff here /usr/local/emhttp/plugins/dynamix.vm.manager/event/started /usr/local/emhttp/plugins/dynamix.docker.manager/event/started ;; 'REMOVE' ) // do your stuff here /usr/local/emhttp/plugins/dynamix.vm.manager/event/stopping_svcs /usr/local/emhttp/plugins/dynamix.docker.manager/event/stopping_svcs ;; esac So i guess this is the script i am supposed to use, but still the drive won't mount. Maybe it's not the script after all ?. I used to have snap plugin and I know it is now old, but that had documentation and actually worked for me. Any suggestions before i take the plunge back to snap?
  3. So i am trying to mount an ssd to use with my VM on UNRAID v6. I understand i have to do something with the script, but it is very unclear on how to do so. the videos are vague and can't find any documentation. I have been searching for a long time and there isn't really anything out there. Just using the default script doesn't work. I got it to format to BTRFS, but really don't care which FS i use as long as i am able to use it. I only did that because currently my VM is on my cache drive with the FS of BTRFS and was just going to copy it over to external SSD once got mounted. I click mount on either the part 1 or the disk and it won't mount and either with UNRAID started or stopped. pleez help. thanks
  4. just thinking....could i start fresh without losing data? like keep certain files from usb? i don't know if that would be feasable in this situation?
  5. so i pulled disk 7 and disk 9 out and ran seagate tools for dos on both of them. they both passed tests and smart tests on a different computer i used. What do i do at this point? focus first on the red balled disk7 or the orange unformatted disk9? i know the array was good before both these drives suddenly went south so i am not worried about parity being wrong or anything like that. Should i take the red balled disk7 out of the array, start it, stop it, and then readd disk7 and hopefully it will rebuild disk 9 once that is green again? Or should i just wait until i get a new sata controller? I'm just assuming its that since i never seen any of the errors on boot and takes forever to boot now. thanks,
  6. duly noted. i don't know what i was thinking. i will not run reiserfsck command like that again. Ran reiserfsck the correct way and all disks were free of corruption except disk 7 and disk9. no suprises there. The text went a little like this....picture of actual message attached along with smart reports. The problem has occured looks like a hardware problem. if you have bad blocks, we advise you to get a new hard drive...etc disk7.txt disk9.txt
  7. just started running --check now. guess i should've started with /dev/md1. Like i said its been running pretty good and really haven't had to do much like this. Unraid is unlike alot that i deal with. Good thing for these forums and people like you. Was there any other errors like memory? Should i get a different port multiplier? was thinking about this one on the list of working ones. SYBA SI-PEX40071..
  8. yeah i haven't run anything. i was waiting back on the verdict of what the problem could be. my server is currently off.
  9. since sda is usb and sdb is parity reiserfsck --check /dev/sdc.......... all the way up to sdk
  10. I'm glad you say that about disk7 because thats the Red Nas drive i really love. It is interesting you say that. I went to run a reiserfsck on all but my parity drive and all of them said FAILED TO OPEN FILESYSTEM and recommended i run --rebuild-sb. I think it could be my port multiplying cards. If i do get rid of them to one of the ones on the known good list how do i fix this or do you think it will be fine once i get rid of the port multipliers? note- Forgot to mention earlier these are the 2 port muliplier cards i am using SYBA SY-PCI40037 SATA II (3.0Gb/s) 1:5 (5x1) Port Multiplier PCI Mounting Card .
  11. unraid pro 5.0.5 - 4gb memory - 2.93 ghz processor - mobo = Asus P5G41T-M LX PLUS So I've been using unraid since 2011 until probably couple months ago flawlessly. Didn't have to touch it. Just would keep humming and no shutdown. Since couple months ago keep getting red ball / orange ball drives. I'm a computer tech so getting drives is not a prob. Now my 2tb RED NAS drive is red balled and just got it not too long ago. It can't be bad so i think its something else. On bootup i noted my flash drive was corrupted. fixed it but still getting lot of weird errors i have never seen before like { DRDY ERR } and looks like memory errors??? Little further investigation says my 2 port multiplier cards may be causing silent corruption. Maybe this is why this is happening? If so i will just get a better port multiplier, but would have to be 8 port since there is only 4 on my motherboard. Errors never seen before: Aug 26 18:28:41 Tower kernel: ata6.00: status: { DRDY ERR } Aug 26 18:28:41 Tower kernel: ata6.00: error: { ABRT } Aug 26 18:28:41 Tower kernel: ata6.00: hard resetting link Aug 26 18:28:41 Tower kernel: ata6.00: SATA link up 3.0 Gbps (SStatus 123 SControl 310) Aug 26 18:28:41 Tower kernel: ata6.00: configured for UDMA/133 Aug 26 18:28:41 Tower kernel: ata6: EH complete Aug 26 18:28:41 Tower kernel: ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Aug 26 18:28:41 Tower kernel: ata6.00: failed command: READ DMA Aug 26 18:28:41 Tower kernel: ata6.00: cmd c8/00:08:48:00:00/00:00:00:00:00/e0 tag 0 dma 4096 syslog.zip
  12. Wow! You're right! i ran --rebuild-tree option again and this time it fixed all corruption. I ran --check on all drives and had no corruption except on disk7 again. Told me to run the --rebuild-tree option. I ran the --check option one more time after and no corruptions! my music directory is back and working! thank you all!
  13. alright so i replaced that 320gb disk with a 500gb after preclearing it. Everything back up and running with parity valid. Still getting errors reading music directory and its still empty. I guess I could go to each individual drive and copy each music folder to a usb hard drive or something, but wouldn't i be back in the same situation if i just recreated a folder again called music? attached current syslog syslog.zip
  14. okay i will try that and report back. just will be a little bit to pre-clear. thanks,
  15. Its funny you say that about that disk. I just checked the status in unmenu and the temp is off the charts (pic attached)? smart hdd test passed, but should i replace anyway? i do have another disk i could use. what is the current pending sector value for? Also noticed in logs keeps saying alot of this about files. Tower shfs/user: shfs_readdir: readdir_r: /mnt/disk7/Music (2) No such file or directory temp.zip