Jump to content

Which is more important to you, unRAID 5.0 features or 3TB drive support?


Rajahal

Recommended Posts

I locked the voting, since the new beta 5.0b7 is out and opinions about the "next" release are moot.  People can still post.

 

This was an impressive poll - 318 poll responses.  This dwarfs the response to any prior poll!

 

Although not everyone will be thrilled that the focus of beta7 was on 3TB drive support, it really had to be (IMO) to continue to attract new customers.  And we are not just talking about 3T support - this change (in theory) should allow disks up to 16TB (which is the limit of an RFS partition) to be in an unRAID array.

 

A 5.0 stable release with 3T drive support will be a beautiful thing.  Hope that we will get there soon! :)

Link to comment
  • Replies 160
  • Created
  • Last Reply

couldn't agree more.

even if I personally don't need 3TB drives themselves just yet for anyone buying new hardware it is at this stage important to know what hardware supports 2TB+ .

without support it isn't really possible to test controllers and motherboards. i hope soon we can see what controller cards get a thumbs up.

 

Link to comment
  • 1 month later...

I've got a 3Tb Western Digital EZRX drive in my unRAID 5.0-beta8c box right now.  Doesn't need any special hardware, the mobo sees it just fine.  I pre-cleared it, and it's being detected properly as 3Tb by unRAID, however I'm not able to use it as a parity drive yet (red dot next to the drive).

Link to comment

I've got a 3Tb Western Digital EZRX drive in my unRAID 5.0-beta8c box right now.  Doesn't need any special hardware, the mobo sees it just fine.  I pre-cleared it, and it's being detected properly as 3Tb by unRAID, however I'm not able to use it as a parity drive yet (red dot next to the drive).

What version of unRAID are you running?  Version 5.0beta8d seems to work just fine with 3TB drives.  (as had several earlier 5.0beta versions, but with some minor issues in recognizing a pre-cleared 3TB drive.)
Link to comment

Here you go...

a few different issues:

 

ul 14 02:25:30 Tower emhttp: shcmd (125): sgdisk -Z /dev/sdb &> /dev/null
Jul 14 02:25:30 Tower emhttp: _shcmd: shcmd (125): exit status: 127
Jul 14 02:25:30 Tower emhttp: shcmd (126): sgdisk -o -a 64 -n 1:64:0 /dev/sdb |& logger
Jul 14 02:25:30 Tower logger: sgdisk: error while loading shared libraries: libicuio.so.44: cannot open shared object file: No such file or directory

and

 

Jul 14 02:14:01 Tower kernel: attempt to access beyond end of device
Jul 14 02:14:01 Tower kernel: sdb1: rw=1, want=4294967296, limit=4294967295
Jul 14 02:14:01 Tower kernel: attempt to access beyond end of device
Jul 14 02:14:01 Tower kernel: sdb1: rw=1, want=4294967304, limit=4294967295
Jul 14 02:14:01 Tower kernel: attempt to access beyond end of device
Jul 14 02:14:01 Tower kernel: sdb1: rw=1, want=4294967312, limit=4294967295
Jul 14 02:14:01 Tower kernel: attempt to access beyond end of device
Jul 14 02:14:01 Tower kernel: sdb1: rw=1, want=4294967320, limit=4294967295
Jul 14 02:14:01 Tower kernel: attempt to access beyond end of device
Jul 14 02:14:01 Tower kernel: sdb1: rw=1, want=4294967328, limit=4294967295
Jul 14 02:14:01 Tower kernel: attempt to access beyond end of device
Jul 14 02:14:01 Tower kernel: sdb1: rw=1, want=4294967336, limit=4294967295
Jul 14 02:14:01 Tower kernel: attempt to access beyond end of device
Jul 14 02:14:01 Tower kernel: sdb1: rw=1, want=4294967344, limit=4294967295
Jul 14 02:14:01 Tower kernel: attempt to access beyond end of device
Jul 14 02:14:01 Tower kernel: sdb1: rw=1, want=4294967352, limit=4294967295
Jul 14 02:14:01 Tower kernel: attempt to access beyond end of device
Jul 14 02:14:01 Tower kernel: sdb1: rw=1, want=4294967360, limit=4294967295
Jul 14 02:14:01 Tower kernel: attempt to access beyond end of device
Jul 14 02:14:01 Tower kernel: sdb1: rw=1, want=4294967368, limit=4294967295
Jul 14 02:14:01 Tower kernel: md: disk0 write error
Jul 14 02:14:01 Tower kernel: handle_stripe write error: 4294967288/0, count: 1
Jul 14 02:14:01 Tower kernel: md: md_do_sync: got signal, exit...
Jul 14 02:14:01 Tower kernel: md: disk0 write error
Jul 14 02:14:01 Tower kernel: handle_stripe write error: 4294967296/0, count: 1
Jul 14 02:14:01 Tower kernel: md: disk0 write error
Jul 14 02:14:01 Tower kernel: handle_stripe write error: 4294967304/0, count: 1
Jul 14 02:14:01 Tower kernel: md: disk0 write error
Jul 14 02:14:01 Tower kernel: handle_stripe write error: 4294967312/0, count: 1
Jul 14 02:14:01 Tower kernel: md: disk0 write error
Jul 14 02:14:01 Tower kernel: handle_stripe write error: 4294967320/0, count: 1
Jul 14 02:14:01 Tower kernel: md: disk0 write error
Jul 14 02:14:01 Tower kernel: handle_stripe write error: 4294967328/0, count: 1
Jul 14 02:14:01 Tower kernel: md: disk0 write error
Jul 14 02:14:01 Tower kernel: handle_stripe write error: 4294967336/0, count: 1
Jul 14 02:14:01 Tower kernel: md: disk0 write error

 

Version 5.0beta9 fixes the missing shared library.  That would be a good first step. upgrade to it.  Without it, there is no way to properly create the GPT partition on the 3TB drive.

Link to comment

Archived

This topic is now archived and is closed to further replies.


×
×
  • Create New...