electron286

Not sure if you have had a chance to look at my reply posts yet or not. I expect there may not be much that can be done with the one server I am running a 9650SE-8LP controller on possibly, at least not with auto-identifying the drives. I would think it may still be possible to actually test the drives if it got past the identifying drive phase, which I think it is hanging/terminating at. The other server I really have no idea what is happening unless there is an issue with the program not liking that controller configuration also, as it does seem to be able to properly report the drive type with the "lshw -c disk" command.

Windows 7 64-bit (PRE-SP1 ISO) VM Install. It took a while, it was easy to get the 32-bit Windows 7 VM running with a pre-SP1 ISO, but I was not able to get the 64-bit to see a drive to install to. After reading many threads on many sites with many complaints of the same problem, this thread finally got me where I needed to go. Part of the problem I was having was I am running a much newer version of Unraid now compared with the age of the many threads I was reading. There are similarities, and also differences that was making it a little harder to try to figure out what to do next. I tied installing the drivers where all I could do was try to load drivers and hope for a drive to finally show up where I could install to, but this does not seem to work with the pre-SP1 ISO media. I then saw the posts about editing the XML to change the bus for the <disk><target> from 2015 August, I thought that sounded like it may do what I needed, but I kept reading on in case there was something about solutions for a newer Unraid version that would be closer to the 6.5.3 version I was working with. Then I lastly saw the post from "assassinmunky" posted 2017 May 05, about how he got it to work "by changing the vDisk bus to SATA (from VirtIO)"! I had tried so many combinations of things, I was no longer sure what I had or had not tried, so I did this, and IT WORKED! (the option was not quite in the same place, but I found it!) I am now happily installing a 64-bit Windows 7 VM! I had tried the 32-bit since that was all I could seem to install, made all the updates to it, then launched the software I need to run, only to then be shown again why I needed the 64-bit version... The software I need to run will only run under a 64-bit environment. So now after the new 64-bit VM is running, I can go through all the updates on it, then install my programs, and it should be all set to run! :-) Thanks everyone, even though I did not ask for help on this, as it was from all the great help provided over the years, that I was able to find the help I needed! My VM adventure has now officially begun! :-)

On the second system, It looks normal for what I would expect to see. Here is the output with the serial numbers anomonized. Running Unraid 6.6.7 # lshw -c disk *-disk:0 description: ATA Disk product: WDC WD40EZRZ-00G vendor: Western Digital physical id: 0.0.0 bus info: scsi@3:0.0.0 logical name: /dev/sdd version: 0A80 serial: WD-WCC********* size: 3726GiB (4TB) capacity: 3726GiB (4TB) capabilities: 15000rpm gpt-1.00 partitioned partitioned:gpt configuration: ansiversion=6 guid=dad24cf9-32fd-4f76-82ce-4141b844a1be logicalsectorsize=512 sectorsize=4096 *-disk:1 description: SCSI Disk product: ST4000NM0023 vendor: SEAGATE physical id: 0.1.0 bus info: scsi@3:0.1.0 logical name: /dev/sde version: GE09 serial: Z1Z***** size: 3726GiB (4TB) capabilities: 7200rpm gpt-1.00 partitioned partitioned:gpt configuration: ansiversion=6 guid=3bc3749a-8974-42e8-822a-2c8c91479016 logicalsectorsize=512 sectorsize=512 *-disk:2 description: SCSI Disk product: ST4000NM0023 vendor: SEAGATE physical id: 0.2.0 bus info: scsi@3:0.2.0 logical name: /dev/sdf version: GE09 serial: Z1Z***** size: 3726GiB (4TB) capabilities: 7200rpm gpt-1.00 partitioned partitioned:gpt configuration: ansiversion=6 guid=2b239099-face-4e70-87af-922b9c828b65 logicalsectorsize=512 sectorsize=512 *-disk:3 description: SCSI Disk product: HUS724040ALS640 vendor: HGST physical id: 0.3.0 bus info: scsi@3:0.3.0 logical name: /dev/sdg version: A280 serial: PCJ***** size: 3726GiB (4TB) capacity: 4859GiB (5217GB) capabilities: 7200rpm partitioned partitioned:dos configuration: ansiversion=6 logicalsectorsize=512 sectorsize=512 *-disk description: SCSI Disk product: Cruzer Glide vendor: SanDisk physical id: 0.0.0 bus info: scsi@0:0.0.0 logical name: /dev/sda version: 1.00 serial: ******************** size: 29GiB (31GB) capabilities: removable configuration: ansiversion=6 logicalsectorsize=512 sectorsize=512 *-medium physical id: 0 logical name: /dev/sda size: 29GiB (31GB) capabilities: partitioned partitioned:dos *-cdrom description: DVD reader product: DV-28E-V vendor: TEAC physical id: 0.0.0 bus info: scsi@1:0.0.0 logical name: /dev/sr0 version: 1.AB capabilities: removable audio dvd configuration: ansiversion=5 status=nodisc *-disk description: ATA Disk product: WDC WD1600AAJS-0 vendor: Western Digital physical id: 0.0.0 bus info: scsi@4:0.0.0 logical name: /dev/sdb version: 3A01 serial: WD-WCA********* size: 149GiB (160GB) capabilities: partitioned partitioned:dos configuration: ansiversion=5 logicalsectorsize=512 sectorsize=512 *-disk description: ATA Disk product: WDC WD1600AAJS-0 vendor: Western Digital physical id: 0.0.0 bus info: scsi@5:0.0.0 logical name: /dev/sdc version: 3A01 serial: WD-WCA********* size: 149GiB (160GB) capabilities: partitioned partitioned:dos configuration: ansiversion=5 logicalsectorsize=512 sectorsize=512

On the first system, I think the problem may be due to the controller that is in use. It masks the drive information. Here is the output with the serial numbers anomonized. Running Unraid 6.5.3 # lshw -c disk *-disk:0 description: SCSI Disk product: 9650SE-8LP DISK vendor: AMCC physical id: 0.0.0 bus info: scsi@1:0.0.0 logical name: /dev/sdb version: 3.08 serial: ********000000000000 size: 149GiB (160GB) capabilities: partitioned partitioned:dos configuration: ansiversion=5 logicalsectorsize=512 sectorsize=512 *-disk:1 description: SCSI Disk product: 9650SE-8LP DISK vendor: AMCC physical id: 0.1.0 bus info: scsi@1:0.1.0 logical name: /dev/sdc version: 3.08 serial: ********000000000000 size: 149GiB (160GB) capabilities: partitioned partitioned:dos configuration: ansiversion=5 logicalsectorsize=512 sectorsize=512 *-disk:2 description: SCSI Disk product: 9650SE-8LP DISK vendor: AMCC physical id: 0.2.0 bus info: scsi@1:0.2.0 logical name: /dev/sdd version: 3.08 serial: ********000000000000 size: 149GiB (160GB) capabilities: partitioned partitioned:dos configuration: ansiversion=5 logicalsectorsize=512 sectorsize=512 *-disk:0 description: SCSI Disk product: 9650SE-8LP DISK vendor: AMCC physical id: 0.0.0 bus info: scsi@4:0.0.0 logical name: /dev/sde version: 3.08 serial: ********000000000000 size: 1397GiB (1500GB) capabilities: partitioned partitioned:dos configuration: ansiversion=5 logicalsectorsize=512 sectorsize=512 signature=03c10c2e *-disk:1 description: SCSI Disk product: 9650SE-8LP DISK vendor: AMCC physical id: 0.1.0 bus info: scsi@4:0.1.0 logical name: /dev/sdf version: 3.08 serial: ********000000000000 size: 465GiB (500GB) capabilities: partitioned partitioned:dos configuration: ansiversion=5 logicalsectorsize=512 sectorsize=512 *-disk:2 description: SCSI Disk product: 9650SE-8LP DISK vendor: AMCC physical id: 0.2.0 bus info: scsi@4:0.2.0 logical name: /dev/sdg version: 3.08 serial: ********000000000000 size: 465GiB (500GB) capabilities: partitioned partitioned:dos configuration: ansiversion=5 logicalsectorsize=512 sectorsize=512 *-disk description: SCSI Disk product: Cruzer Fit vendor: SanDisk physical id: 0.0.0 bus info: scsi@0:0.0.0 logical name: /dev/sda version: 1.27 serial: ******************** size: 14GiB (16GB) capabilities: removable configuration: ansiversion=6 logicalsectorsize=512 sectorsize=512 *-medium physical id: 0 logical name: /dev/sda size: 14GiB (16GB) capabilities: partitioned partitioned:dos *-cdrom description: DVD reader product: DVD-ROM SR-8178 vendor: MATSHITA physical id: 0.1.0 bus info: scsi@2:0.1.0 logical name: /dev/sr0 version: PZ16 serial: [ capabilities: removable audio dvd configuration: ansiversion=5 status=nodisc

This looks like a great tool! I only have two systems that are running a somewhat recent version of Unraid however. I have loaded this into both of my newer installs, 6.5.3, and 6.6.7, and I see the same thing on both... DiskSpeed - Disk Diagnostics & Reporting tool Version: beta 6a Scanning Hardware 07:30:21 Spinning up hard drives 07:30:21 Scanning system storage 07:30:34 Scanning USB Bus 07:30:40 Scanning hard drives then it just sits there. How long does it sit there normally, and how long normally does it take for the cool screens to appear? Does it happen over time, what should we see as the data is being collected and the tests are running? I may have missed something, but I did not see anything that helps in this set of posts, at least that I noticed or stuck out.

I always preferred my nice warm Amber monitors over the harsh green ones myself.

Don't laugh... My two main servers on 24/7 used for adding to, editing and compressing video and active content sharing only have 1GB RAM each (total only 28TB of storage between the two). They work great and are really only file storage, and all work is done on other computers. Multiple drives are almost always being accessed either by me and my working data munching computers, or by family remotely watching content remotely somewhere using Plex. Plex is also running an a separate server looking at my unRAID shares. My main ARCHIVE server is a bit heftier, and much newer. It has 8GB of RAM, has 30TB of storage, and is also on 24/7, and is also seen by my Plex server. NOTE: I only use Plex outside the home, and always use XBMC or KODI internally. My other less used specialty backup servers I think are now all up to 1 GB of RAM, but some may have less. They are only powered up when I need to access much older data, files, and machine drive images and such. Many of these are not x64 capable either. I do not like upgrading, and feel if it is working well let it keep running as it is. If I need more, I look at what my future/new need is, and usually just build a new machine to add to the pool/farm. I did pick up a new (actually old surplus) server that has 4 CPUs, and I think 32GB of RAM, but I have not had a chance to really play much with it yet. I was planning on setting it up with all the new bells and whistles and run a Plex server on it after I get a new unRAID key for it.

Just figured out how to actually rename the thread I had started... of course if I had read this complete thread I would have known also before I tried it and scratched my head multiple times looking for a button to change subject/thread/subject name... Just a suggestion, since I had looked at this thread long ago, before the replies were placed here with details of how to actually do it... Could the very simple short instructions be placed in an edited version of the orignal post in this stickied thread? Somthing like this... to change the example, Drive error,to [sOLVED] Drive error. 1. You need to be logged in and be the originator of the thread. 2. Go to the original post. 3. Select Modify to edit the original post, Here you can also edit the original Topic Subject name.

I would really like to know how good the trayless one is... so yes I would like to see a review! :-)