fnwc
-
Posts
62 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by fnwc
-
-
Hmm, I'm getting something like this:
Settings for eth0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Advertised auto-negotiation: Yes Speed: 100Mb/s Duplex: Full Port: MII PHYAD: 0 Transceiver: internal Auto-negotiation: off Supports Wake-on: pumbg Wake-on: g Current message level: 0x00000033 (51) Link detected: yes
Seems like I'm not using the full potential of my network card... does fixing this require changing a BIOS setting somewhere?
I was reading another site that suggests I use something called mii-tool to change the speed and duplex settings.
-
I hate to be a thread necromancer, but is the wdidle procedure safe to do on an active unRaid array?
-
Hmmm... not sure what happened, but now I'm getting:
Status: unRaid is OK
Date: Mon Dec 14 13:25:58 GMT+8 2009
I guess I'll figure out what's going on when I get home.
-
Hmmm I didn't realize there was a built-in powerdown script. I thought I was using the community script, but I can't be sure now. I putty'd into the server and typed "powerdown". I hadn't realized there was already an alias for this command.
Something new: I'm at work and can't see the machine log, but I started the array last night and now I'm getting these emails:
This message is a status update for unRAID Persephone
-----------------------------------------------------------------
Server Name: Persephone
Status: The unRaid array needs attention. One or more disks are disabled or invalid.
Date: Mon Dec 14 06:40:00 GMT+8 2009
Disk Temperature Status
-----------------------------------------------------------------
Parity Disk [sdd]: 34°C (DiskId: ata-WDC_WD15EADS-00S2B0_WD-WCAVY0850071)
Disk 1 [sde]: 32°C (DiskId: ata-WDC_WD15EADS-00P8B0_WD-WCAVU0126028)
Disk 2 [sdg]: 29°C (DiskId: ata-WDC_WD15EADS-00P8B0_WD-WCAVU0125530)
Disk 3 [sdh]: 34°C (DiskId: ata-WDC_WD15EADS-00S2B0_WD-WCAVY0862483)
Disk 4 [sdi]: 29°C (DiskId: ata-WDC_WD15EADS-00P8B0_WD-WCAVU0125295)
Disk 5 [sda]: 32°C (DiskId: ata-WDC_WD15EADS-00S2B0_WD-WCAVY0839015)
Disk 6 [sdb]: 33°C (DiskId: ata-WDC_WD15EADS-00S2B0_WD-WCAVY0903672)
Disk 7 [sdf]: 31°C (DiskId: ata-WDC_WD15EADS-00P8B0_WD-WMAVU0501410)
Disk SMART Health Status
-----------------------------------------------------------------
Parity Disk PASSED (DiskId: ata-WDC_WD15EADS-00S2B0_WD-WCAVY0850071)
Disk 1 PASSED (DiskId: ata-WDC_WD15EADS-00P8B0_WD-WCAVU0126028)
Disk 2 PASSED (DiskId: ata-WDC_WD15EADS-00P8B0_WD-WCAVU0125530)
Disk 3 PASSED (DiskId: ata-WDC_WD15EADS-00S2B0_WD-WCAVY0862483)
Disk 4 PASSED (DiskId: ata-WDC_WD15EADS-00P8B0_WD-WCAVU0125295)
Disk 5 PASSED (DiskId: ata-WDC_WD15EADS-00S2B0_WD-WCAVY0839015)
Disk 6 PASSED (DiskId: ata-WDC_WD15EADS-00S2B0_WD-WCAVY0903672)
Disk 7 PASSED (DiskId: ata-WDC_WD15EADS-00P8B0_WD-WMAVU0501410)
Output of /proc/mdcmd:
-----------------------------------------------------------------
cmdOper=status
cmdResult=ok
sbName=/boot/config/super.dat
sbVersion=0.95.0
sbCreated=1260797923
sbUpdated=1260798274
sbEvents=1
sbState=0
sbNumDisks=8
sbSynced=0
sbSyncErrs=0
mdVersion=0.95.0
mdState=STARTED
mdNumProtected=8
mdNumDisabled=0
mdDisabledDisk=0
mdNumInvalid=1
mdInvalidDisk=0
mdNumMissing=0
mdMissingDisk=0
mdNumNew=0
mdResync=1465138552
mdResyncPos=178788816
mdResyncPrcnt=12.2
mdResyncFinish=365.2
mdResyncSpeed=58694
diskNumber.0=0
diskName.0=
diskState.0=6
diskSize.0=1465138552
diskModel.0=WDC WD15EADS-00S2B0
diskSerial.0= WD-WCAVY0850071
diskNumReads.0=0
diskNumWrites.0=44707955
diskNumErrors.0=0
diskId.0=ata-WDC_WD15EADS-00S2B0_WD-WCAVY0850071
rdevNumber.0=0
rdevStatus.0=DISK_INVALID
rdevName.0=sdd
rdevSize.0=1465138552
rdevModel.0=WDC WD15EADS-00S2B0
rdevSerial.0= WD-WCAVY0850071
rdevId.0=ata-WDC_WD15EADS-00S2B0_WD-WCAVY0850071
diskNumber.1=1
diskName.1=md1
diskState.1=7
diskSize.1=1465138552
diskModel.1=WDC WD15EADS-00P8B0
diskSerial.1= WD-WCAVU0126028
diskNumReads.1=44706779
diskNumWrites.1=8
diskNumErrors.1=0
diskId.1=ata-WDC_WD15EADS-00P8B0_WD-WCAVU0126028
rdevNumber.1=1
rdevStatus.1=DISK_OK
rdevName.1=sde
rdevSize.1=1465138552
rdevModel.1=WDC WD15EADS-00P8B0
rdevSerial.1= WD-WCAVU0126028
rdevId.1=ata-WDC_WD15EADS-00P8B0_WD-WCAVU0126028
diskNumber.2=2
diskName.2=md2
diskState.2=7
diskSize.2=1465138552
diskModel.2=WDC WD15EADS-00P8B0
diskSerial.2= WD-WCAVU0125530
diskNumReads.2=44707283
diskNumWrites.2=1129
diskNumErrors.2=0
diskId.2=ata-WDC_WD15EADS-00P8B0_WD-WCAVU0125530
rdevNumber.2=2
rdevStatus.2=DISK_OK
rdevName.2=sdg
rdevSize.2=1465138552
rdevModel.2=WDC WD15EADS-00P8B0
rdevSerial.2= WD-WCAVU0125530
rdevId.2=ata-WDC_WD15EADS-00P8B0_WD-WCAVU0125530
diskNumber.3=3
diskName.3=md3
diskState.3=7
diskSize.3=1465138552
diskModel.3=WDC WD15EADS-00S2B0
diskSerial.3= WD-WCAVY0862483
diskNumReads.3=44707228
diskNumWrites.3=722
diskNumErrors.3=0
diskId.3=ata-WDC_WD15EADS-00S2B0_WD-WCAVY0862483
rdevNumber.3=3
rdevStatus.3=DISK_OK
rdevName.3=sdh
rdevSize.3=1465138552
rdevModel.3=WDC WD15EADS-00S2B0
rdevSerial.3= WD-WCAVY0862483
rdevId.3=ata-WDC_WD15EADS-00S2B0_WD-WCAVY0862483
diskNumber.4=4
diskName.4=md4
diskState.4=7
diskSize.4=1465138552
diskModel.4=WDC WD15EADS-00P8B0
diskSerial.4= WD-WCAVU0125295
diskNumReads.4=44707424
diskNumWrites.4=1403
diskNumErrors.4=0
diskId.4=ata-WDC_WD15EADS-00P8B0_WD-WCAVU0125295
rdevNumber.4=4
rdevStatus.4=DISK_OK
rdevName.4=sdi
rdevSize.4=1465138552
rdevModel.4=WDC WD15EADS-00P8B0
rdevSerial.4= WD-WCAVU0125295
rdevId.4=ata-WDC_WD15EADS-00P8B0_WD-WCAVU0125295
diskNumber.5=5
diskName.5=md5
diskState.5=7
diskSize.5=1465138552
diskModel.5=WDC WD15EADS-00S2B0
diskSerial.5= WD-WCAVY0839015
diskNumReads.5=44707325
diskNumWrites.5=1037
diskNumErrors.5=0
diskId.5=ata-WDC_WD15EADS-00S2B0_WD-WCAVY0839015
rdevNumber.5=5
rdevStatus.5=DISK_OK
rdevName.5=sda
rdevSize.5=1465138552
rdevModel.5=WDC WD15EADS-00S2B0
rdevSerial.5= WD-WCAVY0839015
rdevId.5=ata-WDC_WD15EADS-00S2B0_WD-WCAVY0839015
diskNumber.6=6
diskName.6=md6
diskState.6=7
diskSize.6=1465138552
diskModel.6=WDC WD15EADS-00S2B0
diskSerial.6= WD-WCAVY0903672
diskNumReads.6=44706866
diskNumWrites.6=117
diskNumErrors.6=0
diskId.6=ata-WDC_WD15EADS-00S2B0_WD-WCAVY0903672
rdevNumber.6=6
rdevStatus.6=DISK_OK
rdevName.6=sdb
rdevSize.6=1465138552
rdevModel.6=WDC WD15EADS-00S2B0
rdevSerial.6= WD-WCAVY0903672
rdevId.6=ata-WDC_WD15EADS-00S2B0_WD-WCAVY0903672
diskNumber.7=7
diskName.7=md7
diskState.7=7
diskSize.7=1465138552
diskModel.7=WDC WD15EADS-00P8B0
diskSerial.7= WD-WMAVU0501410
diskNumReads.7=44707800
diskNumWrites.7=6529
diskNumErrors.7=0
diskId.7=ata-WDC_WD15EADS-00P8B0_WD-WMAVU0501410
rdevNumber.7=7
rdevStatus.7=DISK_OK
rdevName.7=sdf
rdevSize.7=1465138552
rdevModel.7=WDC WD15EADS-00P8B0
rdevSerial.7= WD-WMAVU0501410
rdevId.7=ata-WDC_WD15EADS-00P8B0_WD-WMAVU0501410
-
Ok, thanks Joe.
I'm wondering where it got corrupted from when it shutdown to when it started up.
-
Ok, I left for the weekend and I "powerdown"ed my machine using the powerdown script.
I came back home, and realized the power had been interrupted at my place at some point (don't know for how long, though).
I powered on my unRAID machine and got this:
NEW_ARRAY, unRAID ARRAY is STOPPED 8 disks in array. PARITY NOT VALID: DISK_NEW
This sort of alarms me, as the array was fine when I powered it down earlier.
Is it ok to start the array? I want to make sure I don't lose any of the data on any of the disk(s).
Attached is my syslog.
-
-
Couldn't find this anywhere, but does the mover do any sort of copy verification when it moves files from the cache disk?
The only reason I ask is that I normally transfer files across to a user share using a file copier that has data verification (such as TeraCopy) for my own sanity. If the verification fails I can be alerted to potential issues with the unRAID server.
-
What the heck....I unzipped it in Win7, maybe that's why? Umm... I'll try to do it directly through putty.
Hmmmmm... I don't have unzip installed, but I tried it in 7-zip (windows) and lo and behold, it's there.
Turns out it was hidden, forgot to check the obvious (windows default zip handler doesn't show it unless you have 'show hidden files/folders' on).
At any rate, I think I got it working... is it necessary to keep these lines in /boot/config/go, once they're installed, or can I remove them once I've rebooted once?
installpkg /boot/socat-1.7.0.0-i486-2bj.tgz (if you will be using Secure SMTP) installpkg /boot/unraid_notify-2.30-noarch-unRAID.tgz
-
Only, in his attachment, there is no file called "unraid_notify-2.30-noarch-unRAID.tgz".
When I unzip the attachment you linked, there is a .tgz file in there too.
I see 4 files
root@Atlas /tmp #unzip -v unraid_notify-2.3.0.zip
Archive: unraid_notify-2.3.0.zip
Length Method Size Ratio Date Time CRC-32 Name
-------- ------ ------- ----- ---- ---- ------ ----
8665 Stored 8665 0% 01-21-09 19:12 ff4b1866 unraid_notify-2.30-noarch-unRAID.tgz
18326 Defl:N 6942 62% 10-01-08 13:17 5b2bff86 LICENSE.txt
1306 Defl:N 588 55% 01-21-09 19:16 535afc8d README.txt
3198 Defl:N 1462 54% 10-01-08 12:42 b7914541 unraid_notify.cfg
-------- ------- --- -------
31495 17657 44% 4 files
What the heck....I unzipped it in Win7, maybe that's why? Umm... I'll try to do it directly through putty.
-
Hi guys,
I'm pretty much a linux noob, and I've been trying to follow the directions but was immediately stopped at this point in brainbone's first post instructions:
2) Place the following attached file on your unraid flash drive: unraid_notify-2.30-noarch-unRAID.tgz (the file included in the unraid_notify .zip)
Only, in his attachment, there is no file called "unraid_notify-2.30-noarch-unRAID.tgz". The only files are:
- LICENSE.txt
- README.txt
- unraid_notify.cfg
Am I missing something here?
- LICENSE.txt
Public Service Announcement - Check Your Ethernet Speed
in Hardware
Posted
I tried both:
and
Still reporting 100 Mb/s.
I even enabled "Load ethernet BIOS" on my GIGABYTE GA-MA74GM-S2 740G R (don't worry, HPA is disabled), but that didn't seem to help (I'm using the onboard NIC).
Anyone else have an idea?