unRAID Server Release 5.0-beta3 Available


limetech

Recommended Posts

  • Replies 185
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Posted Images

upgrade from 5.0-beta2. as following screen captures shown unraid can not detect IDE disks, no issue at 5.0-beta2.

Device list from webGui shown no IDE disks however list from unmenu shown all disks.

 

MB : MSI P43 Neo3-F

 

Syslog shown system had successfully detcted both IDE disks, so looks like a presentation issue in webgui?

 

Jan 31 23:53:37 TestTower kernel: scsi6 : usb-storage 1-6:1.0

Jan 31 23:53:37 TestTower kernel: hda: WDC WD5000AAJB-00UHA0, ATA DISK drive

Jan 31 23:53:37 TestTower kernel: ata3: SATA link down (SStatus 0 SControl 300)

Jan 31 23:53:37 TestTower kernel: ata4: SATA link down (SStatus 0 SControl 300)

Jan 31 23:53:37 TestTower kernel: usb 4-2: new full speed USB device using uhci_hcd and address 2

Jan 31 23:53:37 TestTower kernel: ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

Jan 31 23:53:37 TestTower kernel: ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

Jan 31 23:53:37 TestTower kernel: ata5.00: ATA-8: ST3750330AS, SD35, max UDMA/133

Jan 31 23:53:37 TestTower kernel: ata5.00: 1465149168 sectors, multi 16: LBA48 NCQ (depth 31/32)

Jan 31 23:53:37 TestTower kernel: ata5.00: configured for UDMA/133

Jan 31 23:53:37 TestTower kernel: ata6.00: ATA-8: WDC WD5000AAKS-00YGA0, 12.01C02, max UDMA/133

Jan 31 23:53:37 TestTower kernel: ata6.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA

Jan 31 23:53:37 TestTower kernel: ata6.00: configured for UDMA/133

Jan 31 23:53:37 TestTower kernel: hdb: MAXTOR STM3500630A, ATA DISK drive

 

unraid-5.0b3-disk-list-1.gif.3267c461d8f29e7099796a2e3939df24.gif

unraid-5.0b3-disk-list-2.gif.16a77ee5b45afc3798b6f91ad8dab269.gif

Link to comment

CPU temperature reading is missing from "CPU info" at unmenu at 5.0-beta3, no problem at 5.0-beta2.

Syslog shown following messages, looks like sensor driver has been removed at 5.0beta3?

 

Feb 1 00:09:55 TestTower unmenu[1187]: Try sensors-detect to find out which these are.

Feb 1 00:10:02 TestTower unmenu[1187]: No sensors found!

Feb 1 00:10:02 TestTower unmenu[1187]: Make sure you loaded all the kernel drivers you need.

unraid-5.-beta3-cpu-temp.gif.c7720f1e12a5b679c56c8a4be1c4175e.gif

Link to comment

The advanced power management related features have been made modular.

 

Could you try logging in to a linux command prompt to issue a "sensors-detect", run through the prompts, then issuing "sensors" to see what your output is? Then if it tells you to modprobe any drivers, such as f71882fg, lm75, to give it go, then reissue a "sensors" command?

 

If you get any sort of reading out of that, then try reloading the webpage to see if you get any info from that as well.

 

Link to comment

mounting a hfs filesystem doesn't work anymore. it was no problem in 4.6, 4.7 and 5.0beta2.

 

mount -t hfs /dev/disk/by-id/scsi-SATA_WDC_WD15EARS-00_WD-WMAVU3106264-part2 /mnt/disk/Serien_I-part2
mount: unknown filesystem type 'hfs'

 

Try using HFSPLUS instead of HFS for the filesystem type.

mount -t hfsplus /dev/disk/by-id/scsi-SATA_WDC_WD15EARS-00_WD-WMAVU3106264-part2 /mnt/disk/Serien_I-part2

 

To see the list of supported filesystems look at /proc/filesystems.

cat /proc/filesystems

Link to comment

ok, my bad. of course it has to be hfsplus

 

indeed i have an other problem.

i use snap to mount these extra drives and snap uses the "vol_id" command to get the filesystem for each drive. this command is no longer supported, it seems.

 

Correct. The vol_id program was removed and replaced with other means when the udev subsystem was upgraded. It is no longer supported on current udev subsystems. The replacement for 'vol_id' is 'blkid' and "vol_id --export" becomes "blkid -o udev". The user community addon SNAP will need to be updated if it wants to support the final 5.0 series.

Link to comment

ok, my bad. of course it has to be hfsplus

 

indeed i have an other problem.

i use snap to mount these extra drives and snap uses the "vol_id" command to get the filesystem for each drive. this command is no longer supported, it seems.

 

Correct. The vol_id program was removed and replaced with other means when the udev subsystem was upgraded. It is no longer supported on current udev subsystems. The replacement for 'vol_id' is 'blkid' and "vol_id --export" becomes "blkid -o udev". The user community addon SNAP will need to be updated if it wants to support the final 5.0 series.

And unMENU's disk management page will also need to be updated before it will show the file system type (and, as a result, will not show the "mount" button until it has been modified.  I guess I need to download and install the 5.0-beta3 release to my second server.  ;D).
Link to comment

very nice! i think i will be moving soon to v.5.

Just one question: do you have any idea as to when there will be a non-beta/final version 5 available?

 

 

The time it takes for a beta to become a release varies.  According to the roadmap, there is one more scheduled beta (5.0b4) before the the offiical 5.0 release.  5.0b4 will include support for >2T drives.  There has been no official word from Tom about the timeline for this beta nor the release, but would not expect to see a 5.0 final before March - and that could be optimistic.

 

Might want to hold off this type of question until the beta matures.  After spending many many days and weeks getting this ready for beta release, and releasing a long anticipated beta with significant new functionality, getting questions the official release date before anyone has even installed the beta would be annoying.  :o

Link to comment

Working AFP also makes me interested in moving to v5.  Having a root around the forums leads me to believe I need to remove the HPA created by my old GB motherboard, then upgrade to 4.7, then upgrade to v5b3.  Screwing around with this HPA thing makes me nervous, pretty sure it'll make people less techy than me even more nervous.

Link to comment

upgrade from 5.0-beta2. as following screen captures shown unraid can not detect IDE disks, no issue at 5.0-beta2.

Device list from webGui shown no IDE disks however list from unmenu shown all disks.

 

MB : MSI P43 Neo3-F

 

Syslog shown system had successfully detcted both IDE disks, so looks like a presentation issue in webgui?

 

Jan 31 23:53:37 TestTower kernel: scsi6 : usb-storage 1-6:1.0

Jan 31 23:53:37 TestTower kernel: hda: WDC WD5000AAJB-00UHA0, ATA DISK drive

Jan 31 23:53:37 TestTower kernel: ata3: SATA link down (SStatus 0 SControl 300)

Jan 31 23:53:37 TestTower kernel: ata4: SATA link down (SStatus 0 SControl 300)

Jan 31 23:53:37 TestTower kernel: usb 4-2: new full speed USB device using uhci_hcd and address 2

Jan 31 23:53:37 TestTower kernel: ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

Jan 31 23:53:37 TestTower kernel: ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

Jan 31 23:53:37 TestTower kernel: ata5.00: ATA-8: ST3750330AS, SD35, max UDMA/133

Jan 31 23:53:37 TestTower kernel: ata5.00: 1465149168 sectors, multi 16: LBA48 NCQ (depth 31/32)

Jan 31 23:53:37 TestTower kernel: ata5.00: configured for UDMA/133

Jan 31 23:53:37 TestTower kernel: ata6.00: ATA-8: WDC WD5000AAKS-00YGA0, 12.01C02, max UDMA/133

Jan 31 23:53:37 TestTower kernel: ata6.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA

Jan 31 23:53:37 TestTower kernel: ata6.00: configured for UDMA/133

Jan 31 23:53:37 TestTower kernel: hdb: MAXTOR STM3500630A, ATA DISK drive

 

 

 

I second this motion...

 

My Test Server with UnRaid 5.0_beta2 works great.

 

I upgraded it to 5.0_beta3 and no longer does it show the IDE drives.

 

All SATA are there but no IDE.  :P

 

Downgraded to 5.0_beta2 and all is perfect again. Good thing is only a test server...  ;D

Link to comment

i installed 5.0 beta 3 and had to reassign all the drives. it says that two are missing (out of 22). i assigned all that were available and then rebooted the system. upon reboot 7 of the drives i just assigned were assigned in different locations and 3 were missing.

 

any ideas?

 

 

Are the missing drives IDE?

Link to comment

i installed 5.0 beta 3 and had to reassign all the drives. it says that two are missing (out of 22). i assigned all that were available and then rebooted the system. upon reboot 7 of the drives i just assigned were assigned in different locations and 3 were missing.

 

any ideas?

 

Also, if you could post following it would be very helpful:

 

a) First assign all the drives, then type:

 

ls /dev/disk/by-path

 

b) Now reboot, and if drives have assigned in different locations, again type:

 

ls /dev/disk/by-path

 

Post results of both.

Link to comment

did a test with beta 3, I followed the instruction, after booting all my disk is missing and I have a blank web page?  :'(

 

 

Back to 4.7

 

 

Attached is my syslog

 

//Peter

 

 

 

 

 

Did you read the part in the Release Notes where it says:

 

"If any of your hard drives appear missing or wrong, you can either go to Settings/Disk Devices and re-assign all your hard drives, or you can go to Utils/New Slots and execute that utility to change the device assignments for you. Depending on your hardware configuration this step may not be necessary."

 

 

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.