olympia

Members
  • Posts

    458
  • Joined

  • Last visited

Everything posted by olympia

  1. Sounds very promising. Ajax based progress indicator is more, than I expected. (Is there any chance that you could add an ftp browser for it in the future?)
  2. Wow, bubbaQ. What type of file tranfer and protocols are you planning to support with this feaute?
  3. Yeah, I found 2 of these too, but if I unsderstand well, these are not clients, which can managed remotely, but "online" clients. You have to be on with the browser during the download and can't leave it alone. Correct me if I am wrong.
  4. As I mentioned me neither. I did a little research to find something, but no luck. This is too bad. I am wondering how it is possible that this is not "invented" yet.
  5. Would it possible to include a web managed ftp client in BubbaRaid? Unfortunatley I am not aware if there any soluition exists for this?! My goal would be to let the box downloading via ftp in its own and have the ability to easily manage the downloads. Thank you!
  6. You should check if you set "Update library on startup" and/ or "Always update library in background" in XBMC. (settings/video settings/library).
  7. bubbaQ, you were mentioning accessing files on unRAID via samba shares. Would it be faster than the built in user shares? Thank you and keep up your motivation!
  8. Gorgeous! Could you please include some lower inactivity sets as well? (eg 20-30-45 minutes) Thank you!
  9. bubbaQ What is the feature set of this "first incarnation"? are there already any built in apps?
  10. I was the guy with the more weeks samsung struggling, which ended up selling the drive. Well, I have to say sorry and ask for an excuse from samsung. That was true, that after replacing the samsung with a WD10EACS, there was no spin down issue in my test bed any more. But than when I set up my final unRAID storage with 2 WD10EACS (one for parity) and several other drives, my spin down issues started to appear again. Even in case of WD10EACS. And yes, it is true that they always spin down after a few hours (minimum 4), but it is not how it suppose to work. The only drive, which always spun down with the built in method in my setup is a SATA Samsung 500GB and a Maxtor 200GB drive. HD103UJ, WD10EACS, Samsung 750GB, WD 400GB RE2 all has spin down issues in my setup. They spin down randomly. Every bootup, an other drive going to sleep in time, the others ara just hours later. But there were several cases, when all of my drives spun down in time, after a reboot. I was not able to find any logic in it. So I am pretty sure that it is something with the built in health check in the drives (some smart selftest) which are only built into the newer drives. Or maybe something with unRAID. But it is definitely not Samsung. Sorry for this again. (I payed a lot of money for this lesson). Nevertheless, at the end, all my spin down issues has been solved by unraid notify script (featured with an OS controlled spin down timer), thanks to brainbone!
  11. Although unraid-notify script solved all my issues with spun down, I am very much interested in this as well.
  12. Last two question: - Isn't the frequent (1 minute by default) smartctl check generate overload? Is it affect performance during heavy file transfer? - If I don't want to receive status messages, only alerts, than do I need to leave NotifyDelay empty?
  13. Thanks Joe, I guessed that! And brainbone, thank you very much for this mod! This is something which seems to solve the spin down issues I always had, as a result it was controlled by only the disks' firmware, and I was never able to fully debug. Just one question: can be consider is at a safe solution? For example what happens with the data still in cache, not yet written to the disk, but there is a forced spin down. Is this data flushed somehow to the disk? Or I just misunderstand something, and this kind of situation cannot happen.
  14. I think I am able to modify the script according to the suggested method by Joe L, but maybe this 10th field should be used in general. Do I remember well, that wordpad can be used for editing, with proper unix ending?
  15. smartctl -d ata -A /dev/X output root@Tower:~# smartctl -d ata -A /dev/sdd smartctl version 5.36 [i486-slackware-linux-gnu] Copyright (C) 2002-6 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF READ SMART DATA SECTION === SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 100 100 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0007 100 100 015 Pre-fail Always - 7232 4 Start_Stop_Count 0x0032 099 099 000 Old_age Always - 1332 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 2 7 Seek_Error_Rate 0x000f 253 253 051 Pre-fail Always - 0 8 Seek_Time_Performance 0x0025 253 253 015 Pre-fail Offline - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 2543 10 Spin_Retry_Count 0x0033 253 253 051 Pre-fail Always - 0 11 Calibration_Retry_Count 0x0012 253 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 721 13 Read_Soft_Error_Rate 0x000e 100 100 000 Old_age Always - 79115055 187 Unknown_Attribute 0x0032 253 253 000 Old_age Always - 0 188 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 29 190 Unknown_Attribute 0x0022 071 049 000 Old_age Always - 29 194 Temperature_Celsius 0x0022 151 085 000 Old_age Always - 29 195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always - 79115055 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 2 197 Current_Pending_Sector 0x0012 253 253 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 253 253 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x000a 253 100 000 Old_age Always - 0 201 Soft_Read_Error_Rate 0x000a 100 100 000 Old_age Always - 0 202 TA_Increase_Count 0x0032 253 253 000 Old_age Always - 0 The email output (without mdcmd): his message is a status update for unRAID Tower ----------------------------------------------------------------- Server Name: Tower Status: Disk 2 Overheat! 151°C (DiskId: ata-SAMSUNG_HD501LJ) Date: Sun Sep 21 14:31:23 GMT 2008 Disk Temperature Status ----------------------------------------------------------------- Parity Disk [sdc]: Spun-Down (DiskId: ata-WDC_WD10EACS-00D6B0) Disk 1 [sdb]: Spun-Down (DiskId: ata-WDC_WD10EACS-00D6B0) Disk 2 [sdd]: 151°C (DiskId: ata-SAMSUNG_HD501LJ) Disk 3 [sde]: Spun-Down (DiskId: ata-WDC_WD4000YS-01MPB1) Disk 4 [sdf]: Spun-Down (DiskId: ata-WDC_WD4000YS-01MPB1) Disk SMART Health Status ----------------------------------------------------------------- Parity Disk Spun-Down (DiskId: ata-WDC_WD10EACS-00D6B0) Disk 1 Spun-Down (DiskId: ata-WDC_WD10EACS-00D6B0) Disk 2 PASSED (DiskId: ata-SAMSUNG_HD501LJ) Disk 3 Spun-Down (DiskId: ata-WDC_WD4000YS-01MPB1) Disk 4 Spun-Down (DiskId: ata-WDC_WD4000YS-01MPB1
  16. Great, in the end it seems that all my spin down issues are gone (cross my fingers). But something is not OK with the temperatures. I get mail notifications about disk overheats, and all my disks are above 100 Celsius, which is obviously not the case (morevover, the relation is wrong as well, as my samsung drive is the coolest): This message is a status update for unRAID Tower ----------------------------------------------------------------- Server Name: Tower Status: Parity Disk Overheat! 116°C (DiskId: ata-WDC_WD10EACS-00D6B0) Status: Disk 1 Overheat! 116°C (DiskId: ata-WDC_WD10EACS-00D6B0) Status: Disk 2 Overheat! 151°C (DiskId: ata-SAMSUNG_HD501LJ) Status: Disk 3 Overheat! 109°C (DiskId: ata-WDC_WD4000YS-01MPB1) Status: Disk 4 Overheat! 107°C (DiskId: ata-WDC_WD4000YS-01MPB1) Date: Sun Sep 21 13:58:09 GMT 2008 Is there anything I colud misconfigured, which cause this?
  17. Wow, is this script still able controlling spin down timer on a per disk basis? I don't mean different spin down timers for each disks, but what happens if I use one disk continously? Is other disks are going to sleep in the meanwhile?
  18. Is the performance going to be better with SMP?
  19. Well, unfortunatelly I don't have an own pic from the front, but it is this case: http://www.gigabyte.com.tw/Products/Chassis/Products_Spec.aspx?ProductID=2482 The drive bay was completely dremmeled out, together with the aluminium front of the case, because of the airflow. After that, a custom drivebay has been made and installed, which can hold 6 disks. I am not sure if they can be recognized, but there is 2 12cm fan attached from the front side.
  20. This is how mine is looks now. Small factor and anti vibration is in main focus.