53 minutes ago, comet424 said:

i set them all sata drives to Enabled and Hot Swapable

 

the SSD  is connected to a LSI HBA card though

That only applies to the onboard SATA controller, LSI should also support hot swapping, if all the remaining hardware also supports it, try connecting them to the onboard SATA instead.

I've seen it mentioned a couple times in this thread, but are there any plans to introduce GUI support for reformatting 520-byte-sector SAS drives to 512 byte sectors? I was doing it last night via command line with 12 terminal windows open. It would be amazing to do this with a few clicks in the UI. I suppose I could try to get Parallel installed to be able to reformat all drives with a single command.

 

Also, I'm encountering issues with the /Tools/Preclear page in the GUI. 9 times out of 10, it never stops "loading," rendering the entire UI unusable. I will admit, this Preclear has my CPU pegged at 100% (2c/4t), but even before the Preclear it was doing this. Any ideas?

47 minutes ago, JohnnyGrey said:

Also, I'm encountering issues with the /Tools/Preclear page in the GUI. 9 times out of 10, it never stops "loading," rendering the entire UI unusable. I will admit, this Preclear has my CPU pegged at 100% (2c/4t), but even before the Preclear it was doing this. Any ideas?

Post diagnostics.  It may be a php warning or error.

1 hour ago, dlandon said:

Post diagnostics.  It may be a php warning or error.

Attached.

rapture-diagnostics-20241130-1237.zip

1 hour ago, JohnnyGrey said:

Attached.

rapture-diagnostics-20241130-1237.zip 360.59 kB · 0 downloads

It looks to me like you are having disk issues:

Nov 30 10:23:03 Rapture kernel: scsi 10:0:16:0: Power-on or device reset occurred

This occurs a lot in the log.

 

Disk /dev/sdr can't get SMART data:

Smartctl open device: /dev/sdr failed: INQUIRY failed

 

This I don't understand:

Nov 30 11:09:39 Rapture emhttpd: device /dev/sdaw has size zero
Nov 30 11:09:39 Rapture emhttpd: device /dev/sdae has size zero
Nov 30 11:09:39 Rapture emhttpd: device /dev/sdak has size zero
Nov 30 11:09:39 Rapture emhttpd: device /dev/sdah has size zero
Nov 30 11:09:39 Rapture emhttpd: device /dev/sdab has size zero
Nov 30 11:09:39 Rapture emhttpd: device /dev/sdat has size zero
Nov 30 11:09:39 Rapture emhttpd: device /dev/sdaf has size zero
Nov 30 11:09:39 Rapture emhttpd: device /dev/sdal has size zero
Nov 30 11:09:39 Rapture emhttpd: device /dev/sdai has size zero
Nov 30 11:09:39 Rapture emhttpd: device /dev/sdac has size zero
Nov 30 11:09:39 Rapture emhttpd: device /dev/sdz has size zero
Nov 30 11:09:39 Rapture emhttpd: device /dev/sdau has size zero
Nov 30 11:09:39 Rapture emhttpd: device /dev/sdag has size zero
Nov 30 11:09:39 Rapture emhttpd: device /dev/sdar has size zero
Nov 30 11:09:39 Rapture emhttpd: device /dev/sdao has size zero
Nov 30 11:09:39 Rapture emhttpd: device /dev/sdaa has size zero
Nov 30 11:09:39 Rapture emhttpd: device /dev/sdav has size zero
Nov 30 11:09:39 Rapture emhttpd: device /dev/sdas has size zero
Nov 30 11:09:39 Rapture emhttpd: device /dev/sdap has size zero
Nov 30 11:09:39 Rapture emhttpd: device /dev/sdaq has size zero
Nov 30 11:09:39 Rapture emhttpd: device /dev/sdan has size zero
Nov 30 11:09:39 Rapture emhttpd: device /dev/sdam has size zero
Nov 30 11:09:39 Rapture emhttpd: device /dev/sdad has size zero
Nov 30 11:09:39 Rapture emhttpd: device /dev/sdaj has size zero

 

6 hours ago, JohnnyGrey said:

I've seen it mentioned a couple times in this thread, but are there any plans to introduce GUI support for reformatting 520-byte-sector SAS drives to 512 byte sectors? I was doing it last night via command line with 12 terminal windows open. It would be amazing to do this with a few clicks in the UI. I suppose I could try to get Parallel installed to be able to reformat all drives with a single command.

 

No plan at this point.

3 hours ago, dlandon said:

It looks to me like you are having disk issues:

Nov 30 10:23:03 Rapture kernel: scsi 10:0:16:0: Power-on or device reset occurred

This occurs a lot in the log.

 

Disk /dev/sdr can't get SMART data:

Smartctl open device: /dev/sdr failed: INQUIRY failed

 

This I don't understand:

Nov 30 11:09:39 Rapture emhttpd: device /dev/sdaw has size zero
Nov 30 11:09:39 Rapture emhttpd: device /dev/sdae has size zero
Nov 30 11:09:39 Rapture emhttpd: device /dev/sdak has size zero
Nov 30 11:09:39 Rapture emhttpd: device /dev/sdah has size zero
Nov 30 11:09:39 Rapture emhttpd: device /dev/sdab has size zero
Nov 30 11:09:39 Rapture emhttpd: device /dev/sdat has size zero
Nov 30 11:09:39 Rapture emhttpd: device /dev/sdaf has size zero
Nov 30 11:09:39 Rapture emhttpd: device /dev/sdal has size zero
Nov 30 11:09:39 Rapture emhttpd: device /dev/sdai has size zero
Nov 30 11:09:39 Rapture emhttpd: device /dev/sdac has size zero
Nov 30 11:09:39 Rapture emhttpd: device /dev/sdz has size zero
Nov 30 11:09:39 Rapture emhttpd: device /dev/sdau has size zero
Nov 30 11:09:39 Rapture emhttpd: device /dev/sdag has size zero
Nov 30 11:09:39 Rapture emhttpd: device /dev/sdar has size zero
Nov 30 11:09:39 Rapture emhttpd: device /dev/sdao has size zero
Nov 30 11:09:39 Rapture emhttpd: device /dev/sdaa has size zero
Nov 30 11:09:39 Rapture emhttpd: device /dev/sdav has size zero
Nov 30 11:09:39 Rapture emhttpd: device /dev/sdas has size zero
Nov 30 11:09:39 Rapture emhttpd: device /dev/sdap has size zero
Nov 30 11:09:39 Rapture emhttpd: device /dev/sdaq has size zero
Nov 30 11:09:39 Rapture emhttpd: device /dev/sdan has size zero
Nov 30 11:09:39 Rapture emhttpd: device /dev/sdam has size zero
Nov 30 11:09:39 Rapture emhttpd: device /dev/sdad has size zero
Nov 30 11:09:39 Rapture emhttpd: device /dev/sdaj has size zero

 

These all may be related to the DS2426 that I fired up earlier this morning. I had some trays disconnected at some point. I got this shelf from work, and it contains 24x 900gb SAS drives that were formatted with 520-byte sectors. I am in the process of using sg3-utils to reformat them to 512-byte sectors. Until then I believe they report a capacity of 0. I'm still on the fence on whether I will actually utilize the drives due to power consumption, although it should improve once they are able to spin down.

so no matter what i do  i moved the SSD from the LSI to SATA slot

if i pull it out  it goes green in the historical section  when i shove back in it either doesnt show up

or when it does  it tells me to Reboot  

is there anything in my diagnostics  in the configuration  in  Plugins in something  that does it

i dont seem to have this issue with USB hard drives

just with hot swap SSDs i use  i dont have a hot swap hard drive today to test maybe tommmorow to test

 

but is there anything that could be doing this issue this is been going on for months for me

 

 

tardis-diagnostics-20241130-2007.zip

Today, after installing the latest release of UD, I'm always sent to the UD tab (within the Main tab) instead of the Array tab.

 

I'm using Page view=tabbed in Settings.

 

11 hours ago, comet424 said:

so no matter what i do  i moved the SSD from the LSI to SATA slot

if i pull it out  it goes green in the historical section  when i shove back in it either doesnt show up

or when it does  it tells me to Reboot 

That suggests the device (or other hardware) doesn't support hot plug correctly.

4 hours ago, hawihoney said:

Today, after installing the latest release of UD, I'm always sent to the UD tab (within the Main tab) instead of the Array tab.

 

I'm using Page view=tabbed in Settings.

 

If you click on the UD tab, then click on a link like the device settings, and then click 'Done', you will go back to the UD tab.

2 hours ago, dlandon said:

If you click on the UD tab, then click on a link like the device settings, and then click 'Done', you will go back to the UD tab.

Thats not what I try to report.

 

I open the Unraid GUI. This usually opens the Main tab. Within the Main tab the Array tab will be opened usually. Now the UD tab opens instead - always.

 

44 minutes ago, hawihoney said:

Thats not what I try to report.

 

I open the Unraid GUI. This usually opens the Main tab. Within the Main tab the Array tab will be opened usually. Now the UD tab opens instead - always.

 

I see an issue and I am working on it.

On 11/30/2024 at 12:23 AM, chrizzo said:

Hey @dlandon thx a lot, that did the trick.
I also changed 'Defaultvers=4' to 'Defaultvers=3'.

 

Thx a lot pal!

Unraid 7.0.0-rc.1 has this fixed.  Upgrade and try.

On 11/30/2023 at 1:43 PM, dlandon said:

I'm stuck!

I have had the same setup for some time now with no issues relating to shares but for some reason, after a system restart, I have lost all ability to mount an SMB share from my Unraid server to my Synology NAS on the same network. I'm getting a 

Device '//TH3NAS/data' failed to mount. Sys log show this for an error,

Tower kernel: CIFS: VFS: cifs_mount failed w/return code = -13

I have tried everything I could find for troubleshooting and now down to asking for help. 

I have included my diagnostics 

Any assistance would be greatly appreciated!

 

 

tower-diagnostics-20241209-1652.zip

54 minutes ago, H3is3nb3rg said:

 

tower-diagnostics-20241209-1652.zip 147.37 kB · 0 downloads

This is what I see in your log:
 

Dec  9 15:47:52 Tower unassigned.devices: Mounting Remote Share '//TH3NAS/data'...
Dec  9 15:47:52 Tower unassigned.devices: Mount SMB share '//TH3NAS.LOCAL/data' using SMB default protocol.
Dec  9 15:47:52 Tower unassigned.devices: Mount SMB command: /sbin/mount -t 'cifs' -o rw,hard,relatime,noserverino,nounix,iocharset=utf8,file_mode=0777,dir_mode=0777,uid=99,gid=100,actimeo=10,closetimeo=30,seal,credentials='/tmp/unassigned.devices/credentials_TH3NAS_data' '//TH3NAS.LOCAL/data' '/mnt/remotes/TH3NAS_data'
Dec  9 15:47:53 Tower kernel: CIFS: enabling forceuid mount option implicitly because uid= option is specified
Dec  9 15:47:53 Tower kernel: CIFS: enabling forcegid mount option implicitly because gid= option is specified
Dec  9 15:47:53 Tower kernel: CIFS: Attempting to mount \\TH3NAS.LOCAL\data
Dec  9 15:47:53 Tower kernel: CIFS: Status code returned 0xc000006d STATUS_LOGON_FAILURE
Dec  9 15:47:53 Tower kernel: CIFS: VFS: \\TH3NAS.LOCAL Send error in SessSetup = -13
Dec  9 15:47:53 Tower kernel: CIFS: VFS: cifs_mount failed w/return code = -13
Dec  9 15:47:53 Tower unassigned.devices: Remote Share '//TH3NAS.LOCAL/data' failed to mount.

 

The log messages strongly indicate a credential issue:

• STATUS_LOGON_FAILURE (0xc000006d): This status code explicitly states that the login attempt failed due to invalid credentials (username or password).
• cifs_mount failed w/return code = -13: The error code -13 corresponds to EACCES (Permission Denied), which is often seen when the provided credentials do not have sufficient rights or are incorrect.

Be sure you don't use any special characters in the user or password fields.

On 11/30/2023 at 1:43 PM, dlandon said:

I'm stuck!

I have had the same setup for some time now with no issues relating to shares but for some reason, after a system restart, I have lost all ability to mount an SMB share from my Unraid server to my Synology NAS on the same network. I'm getting a 

Device '//TH3NAS/data' failed to mount. Sys log show this for an error,

Tower kernel: CIFS: VFS: cifs_mount failed w/return code = -13

I have tried everything I could find for troubleshooting and now down to asking for help. 

I have included my diagnostics 

Any assistance would be greatly appreciated!

 

Got it resolved, had a special character in my password. Thank you for the help!

Hi guys,

I got a dire question.

 

My neighbor has a qnap with 4 disks and wont boot anymore. Ofc he did not make backup because "why do we need backups with raid 5 right" - despite the fact I told him many time to get an external 4T drive or something to at least backup personal data once a month.

 

Anyhow - I was already building an unraid server for time (trial key still) and added the 4 drivers to see if one or more failed. Extended smart test shows the drives are just fine but ofc I cannot mount a "linux_raid_member" fs using unassigned drives. I was thinking about using an other qnap (system just might eol as its been running 24/7 for the last 12 years - disk are replaced twice during that time so current set nowhere near end of their lifespan)  but all 2nd hand are almost the same cost as a new one - money they cannot spend.

 

So - and maybe I'm not at the right place here

- is it possible to somehow bring this linux_raid_member back to life on unraid (would be awesome)

- is it possible to somehow bring this linux_raid_member back to life on a "donor system" - I already prepped a bootable disk with ubuntu 24 but I have no experience with mdadm whatsoever - The only thing I know is in which order the disk must are.

 

 

On 11/21/2024 at 5:03 PM, dlandon said:

The 'cache=strict' is the best option for performance and consistency  If you do a 'sync -f {mountpoint}' when checking for the files on Unraid, this invalidates the cache and the files will then be made current.

 

Adding a cache setting will only complicate UD for a corner use case.

For log files being constantly read and pushed to graylog this means a sync -f every 10 seconds which would be unnecessary then. I see you point and will see what I can do cron-wise...

8 minutes ago, JPHobby said:

For log files being constantly read and pushed to graylog this means a sync -f every 10 seconds which would be unnecessary then. I see you point and will see what I can do cron-wise...

Sync does not help. New lines pop up but lines in the middle are missing etc. remounting with cache=none and actimeo=0 does help....

 

Unless there is an option I will then obviously have to mount this manually....

Are these types of BTRFS "Linux Raid Members" not mountable with unassigned devices? They were single disk standalone volumes.

 

9 hours ago, foo_fighter said:

Are these types of BTRFS "Linux Raid Members" not mountable with unassigned devices? They were single disk standalone volumes.

 

UD cannot mount disks with that format.

Hi, Im having some issues connecting my Terramaster NAS via Unassigned Devices (it was working perfectly a few days ago?).

I think it perhaps has something to do with Windows 24H2?, can anyone make any sense of these logs, have been Googling for hours getting nowhere, please help, thanks

 

8 minutes ago, archieboy72 said:

Hi, Im having some issues connecting my Terramaster NAS via Unassigned Devices (it was working perfectly a few days ago?).

I think it perhaps has something to do with Windows 24H2?, can anyone make any sense of these logs, have been Googling for hours getting nowhere, please help, thanks

 

The log messages strongly indicate a credential issue:

• STATUS_LOGON_FAILURE (0xc000006d): This status code explicitly states that the login attempt failed due to invalid credentials (username or password).
• cifs_mount failed w/return code = -13: The error code -13 corresponds to EACCES (Permission Denied), which is often seen when the provided credentials do not have sufficient rights or are incorrect.

Check your credentials.  Don't use special characters in the user name or password.