Last weekend I tried to upgrade and failed.  A user here helped me identify a driver issue so I went back to v6.0 beta 10a.

 

I am raising this issue again so that I hope we can get a fix for the driver issue and I can upgrade to the latest version.

 

Attached is the failed diagnostics from v6.1.9.

 

Attached is the working syslog from v6.0 beta 10a.

 

Any help would be appreciated.

 

 

 

megatron-diagnostics-20160430-0824.zip

syslog-2016-04-30.txt

This is exactly why users are encouraged to particpate in the Betas and RCs early on so that issues can be resolved BEFORE the code is finalized and released.

 

 

You really should have been upgrading your software versions well beyond beta10 significantly earlier.

I understand.  I am happy to move to the latest beta.  But the reason why I never upgraded is everything was working just fine.  That's kind of good news.

 

I understand.  I am happy to move to the latest beta.  But the reason why I never upgraded is everything was working just fine.  That's kind of good news.

But the bad news is nobody can support 6.0b10a since nobody has it anymore. And I'm not sure all plugin authors are still supporting anything before 6.1 since the move from 6.0 to 6.1 broke many plugins.

 

Not sure you can count on anybody that can help with your driver issue to see this since the limited staff at Limetech may not read every thread on the forum. Maybe post it in Defect Reports or contact support directly by email.

Can't they just fix this driver on the latest 6.2 beta?

Can't they just fix this driver on the latest 6.2 beta?

If they know it needs fixing.

I don't see any driver issues.  Both PCI-X SAS cards initialized fine at first, assigned all ATA and SCSI channels, and initially identified the first drive on each card, and went on to setup all of the drives on the first card (so the driver seems fine).  However the Crucial 256GB drive on the second SAS card failed on SCSI setup, with evidence of kernel corruption, and its error handler was terminated (scsi_eh_11 does not appear in ps report).  At that point, the card was ignored from then on, no drives (including the Crucial) are added.  You could try swapping the Crucial for another, but I doubt it will help.

 

What I do see is some old software, a 10 year old BIOS, with a warning about that in the syslog.  I recommend updating your motherboard BIOS, then checking for firmware updates for the SAS cards too.  I don't know what else to advise, so I'm hoping the upgrades help.  Also, newer firmware might have better support for the SSD.

Thanks RobJ,

 

But that doesn't explain why v6.0beta10a works and the new versions do not. 

 

Is it because the crucial (cache drive) is formatted btrfs?  Is that still supported?

 

This is what I thought was a driver error:

 

kernel BUG at drivers/ata/sata_mv.c:2120!

 

I did miss that line, sorry.  I'm not completely convinced it's not a compatibility issue though, but a driver bug is certainly a possibility.  It seemed very unusual though that you would be the only one to be affected, so I Googled it, and found one other, also an unRAID user, found here.  There's a bit of good news, a workaround, in that moving the SSD off the card seems to work.  I still strongly recommend checking for BIOS and firmware updates.  Perhaps some day, the Linux community will patch the driver if that's what's needed, or Marvell will patch the firmware, if they haven't already.  I don't believe there's anything that LimeTech can do.

Fair enough. It's my cache drive that holds my dockers container so I should be able to rebuild without losing data.  I'm currently swapping my parity drive for a 5gb so I will try to tomorrow hopefully.

 

Thanks again.

Is it because the crucial (cache drive) is formatted btrfs?  Is that still supported?

 

I forgot to add that it had nothing to do with how it's formatted.  It died before it even read/opened the drive.

Fair enough. It's my cache drive that holds my dockers container so I should be able to rebuild without losing data.  I'm currently swapping my parity drive for a 5gb so I will try to tomorrow hopefully.

 

Thanks again.

You don't need to rebuild, just change controller.

This Super Micro was a beast to get set up.  I loathe the idea of opening it up.  I just go the the garage to swap out drives and do everything else headless.

 

Sent from my SM-N920V using Tapatalk

 

You do have one empty SATA port on the motherboard, where you could connect the Crucial.  But you would have to open it up, to connect it.  SSD's don't have to be in slots though, you can hang them loose in there, off to the side.

You do have one empty SATA port on the motherboard, where you could connect the Crucial.  But you would have to open it up, to connect it.  SSD's don't have to be in slots though, you can hang them loose in there, off to the side.

Oh yes, I know. I meant I did not want to switch controllers.  Swapping the Crucial is a breeze. I just wonder if it's all SSDS, or just this one in particular.  Either way, I'll be happy to be on the latest beta.  Frankly I was so happy with v6.0beta10a with my dockers running, it was doing everything I needed.  That was an exciting time. Unraid took a huge leap forward then.

 

But now that I have perfected up and down grading I'll stay up to date.

 

Btw... is there an easy way to clone my crucial ssd cache  including the dockers and their configurations?

 

Sent from my SM-N920V using Tapatalk

 

 

 

Btw... is there an easy way to clone my crucial ssd cache  including the dockers and their configurations?

 

Sent from my SM-N920V using Tapatalk

Outright Clone, you would install something like Clonezilla onto another flash drive.

 

Backup of docker configurations, use CA

You do have one empty SATA port on the motherboard, where you could connect the Crucial.  But you would have to open it up, to connect it.  SSD's don't have to be in slots though, you can hang them loose in there, off to the side.

Sorry,  I didn't read this well.  I am not sure there is a native sata port on my motherboard.  I really don't want to open this thing.  But I may have to.  I assume there is a performance improvement if I run my docker apps off the ssd vs a regular Hard drive?

 

Sent from my SM-N920V using Tapatalk

 

 

You do have one empty SATA port on the motherboard, where you could connect the Crucial.  But you would have to open it up, to connect it.  SSD's don't have to be in slots though, you can hang them loose in there, off to the side.

Sorry,  I didn't read this well.  I am not sure there is a native sata port on my motherboard.  I really don't want to open this thing.  But I may have to.

According to your syslog, there's one port set up without issue, but not in use.  It's possible for a maker to not hook up all of the ports, but that's not common.

 

I assume there is a performance improvement if I run my docker apps off the ssd vs a regular Hard drive?

It *usually* is faster, especially if shared access, no seek delays.

According to your syslog, there's one port set up without issue, but not in use.  It's possible for a maker to not hook up all of the ports, but that's not common.

 

Can you tell me which port is free from the syslog?  I am looking at manuals for the board and I am not sure what I could connect an SSD to on that board.  There is a PATA port that I use for the 512mb kicker disk (compact flash), but I am not sure what kind of performance a port like that would give an ssd... or if it would support trim, etc.

 

This is a link to the mother board manual.  http://www.supermicro.com/manuals/motherboard/A_8131/MNL-H8DA8.pdf 

I have the H8DAE shown on page 1-4. 

 

I am trying to figure out if I have to buy some kind of controller card I can put in one of the empty PCI-X slots or some kind of adapter cable, because I know there is no SATA connectors on this motherboard.

 

Any advice?

 

BTW:  For now, I hooked up a 250GB hard drive and I am running the latest beta.

 

 

I'm sorry, I was completely wrong, probably mixed up your system with someone else's.  As you said, the board has no SATA ports at all.  The first card has an empty port, the second one, which is what I saw earlier, but that's no help.  And you're right, you don't want the SSD on a PATA connection.

OK.  Well for now I am going to go with a Fast 1TB Cache Disk and see how she does.

 

This just arrived.  http://amzn.com/B008KXFEZK

 

Thanks again for all of your help.