Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Help! Missing disk after 4.5.3 upgrade!

Featured Replies

Sorry for the crosspost (I posted this in the announcements thread, but no response there yet...)

 

 

I Have a disk showing as missing after the 4.5.3 upgrade...(from 4.5)

 

Smells alot like the old disk missing issue, but doesn't seem to show the same way...

 

My syslog shows it's detecting the drive with a slightly different name, and the menu screen shows the disk as "Missing".

Nowhere does the different name show up in the user interface (not under devices either)...the drive shows with a red bullet.

 

The drive is a Hitachi, and I have 2 other Hitachi's in my setup and they're detected just fine...It almost looks like the newly detected name is corrupted somehow.

 

Downgrading to 4.5 shows everything alright.  I'm trying to upgrade to 4.5.3 in order to support the new supermicro board I'm about to install.

 

 

Here's what my main screen shows:

 

Version 4.5:

 

      Model / Serial No.    Temperature    Size    Free    Reads    Writes    Errors

parity    ata-Hitachi_HDS721010KLA330_GTJ100PAG0YG3C    42°C    976,762,552    -    105    122    0

disk1    ata-SAMSUNG_HD103UJ_S13PJDWS323320    34°C    976,762,552    36,868,312    54    6    0

disk2    ata-SAMSUNG_HD103UJ_S13PJ1BQ702829    33°C    976,762,552    15,414,156    55    6    0

disk3    ata-SAMSUNG_HD103UJ_S13PJDWS323304    30°C    976,762,552    38,589,180    52    6    0

disk4    ata-SAMSUNG_HD103UJ_S13PJ1BQ735050    34°C    976,762,552    140,416,300    52    6    0

disk5    ata-Hitachi_HDS721010KLA330_GTG000PAG17Z4C    39°C    976,762,552    85,548,068    53    6    0

disk6    ata-Hitachi_HDS721010KLA330_GTJ100PAG0HBSC    40°C    976,762,552    636,785,268    118    78    0

disk7    ata-Hitachi_HDT721010SLA360_STF604MR2MDJ6P    35°C    976,762,552    422,973,780    48    5    0

disk8    ata-Hitachi_HDT721010SLA360_STF604MR3GM8SP    34°C    976,762,552    937,514,212    52    7    0

disk9    Not installed

disk10    Not installed

 

 

 

 

-----------------------------------------

 

Post 4.5.3 upgrade

 

    Model / Serial No.    Temperature    Size    Free    Reads    Writes   

Errors

parity    Hitachi_HDS72101_GTJ100PAG0YG3C    42°C    976,762,552    -    -    -   

-

disk1    SAMSUNG_HD103UJ_S13PJDWS323320    34°C    976,762,552    -    -    -    -

disk2    SAMSUNG_HD103UJ_S13PJ1BQ702829    33°C    976,762,552    -    -    -    -

disk3    SAMSUNG_HD103UJ_S13PJDWS323304    30°C    976,762,552    -    -    -    -

disk4    SAMSUNG_HD103UJ_S13PJ1BQ735050    34°C    976,762,552    -    -    -    -

disk5    Hitachi_HDS72101_GTG000PAG17Z4C    38°C    976,762,552    -    -    -   

-

disk6    Hitachi_HDS72101_GTJ100PAG0HBSC    40°C    976,762,552    -    -    -   

-

disk7    Missing

Hitachi_HDT721010SLA360_STF604MR2MDJ6P    -    -

976,762,552    -    -    -    -

disk8    Hitachi_HDT72101_STF604MR3GM8SP    34°C    976,762,552    -    -    -   

-

disk9    Not installed

disk10    Not installed

 

 

I'm also attaching my syslogs...

...I think the entry of note in the 4.5.3 log is as follows:

Apr 26 13:21:18 Tower kernel: ata1.00: model number mismatch 'Hdtachi HQT721010^BLA360          0' != 'Hitachi HDT721010SLA360'

 

Not sure why this drive is being detected as a Hdtachi instead of Hitachi under 4.5.3

 

 

 

 

 

 

Any ideas?

 

David

syslog.45.zip

syslog.453.zip

  • Author

The only thing interesting about this, is it's the first drive that's detected that seems to have the name corruption problem...

 

it appears to be on a controller using the SIL24 driver...so this isn't a SAS issue (I think?)....

 

From what I can tell by the syslog, there's another drive on this controller as well, and it's also a hitachi and it reports just fine...

 

I'm at a loss....could this be a cabling issue?...strange that it doesn't manifest itself with 4.5, only 4.5.3 (I haven't tried anything in between [should i?])

 

I've no idea what to try next...I don't want to go ripping things apart without having any idea what the best systematic approach would be from here...

 

Should I:

Try swapping ports with another drive?

Try resetting my configuration and rebuilding parity using the "bad" drive name that's registering under 4.5.3 (and risk the name fixing itself later?)

Wait for 4.5.4?

 

 

I've got the supermicro board I'd like to install, and 2 brand new drives I'm ready to deploy...so waiting is probably my last choice...but all the others seem to carry some risk...

 

Any suggestions/ideas/comments?

 

David ???

Did you try rebooting a second time with 4.5.3 and does the troubled harddisk detect the exact same way ?

 

A bad cable would probably give you a different string each time.

  • Author

Yes, the name came back the same (wrong way) after every reboot....

 

I've moved the drives off the sil controller card and all is well again....I still have no idea why one of the drives is reporting wrong on this controller....

 

David

freak of nature, or controller is fried :)

 

i was going ot suggest you change sata ports then reassign but look slike youve done that.

 

might want to try another disk on your sata card to see if the problem exists with the card itself.

Le sigh.  This ^ spamming is getting old.

  • 2 weeks later...
  • Author

@terrastrife:

Yea, I've moved the drive...I can't believe it's a fried controller, since it works with one version (4.5.2), but not another (4.5.3)...I see that there's a new release...perhaps I'll try it again on that controller to see how it behaves...otherwise, the drives are running fine on the supermicro controller I put in.

 

to everyone else who replied to my thread, thanks very much...still no actual solution, but the work-around is to not use that controller.

 

I'll follow up after I try the latest release if anyone is curious...

 

 

Archived

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

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.