cdoublejj

ok, new matching exact model HBA card fixed it!

OKAY! Would you believe it? I was looking at this here IPMI screenshot and my bios boot screen and the actual servers it's self, one of the HBAs isn't showing up/

EDIT: ANY AND ALL CONTROLLERS ARE NON RAID AND ARE IT MODE! or atleast as far as i can tell, they are. rolling back did not help. for all i know i could loose a cable. i though hardware profiler might help but, their are what feels like thousands of lines of code. i'm just trying to see if maybe a driver for a controller card got dumped or killed i've attached a copy paste of profiler because there is no download a text file option. maybe if it hardware i get lucky and it's a loose cable but, its wierd because it was running for 13 months up time EDIT: normally i'd start shaking wires and all that but, it's 4f out and icey getting to it will be a challenge, i plan on updating this thread if i some how get lucky to figure something out. EDIT: Remembered i have IPMI, I doubt a shutdown will help but, i'm trying also i found this device listing [INSERT IMG] Please attached not insert image gui element found in forum posting ui. HP.txt

FYI it doesn't complain to me that ti's trial mode and I DID NOTHING AT ALL to fix it. issue just went away on it's own. how the hell does that figure?

wierd. i think i still have the email the license file, should i try dropping the license file on to "flash" again (as per guide of course)?

Oh thank you for reminding me about that. see attached tower-diagnostics-20220618-0017.zip

all my stuff was there minus the passwords and permissions levels, all my shares even showed up as public shares, good enough for the girls i go out with but, month or two later, aka tonight i noticed this:

a while back my flash drive died, i installed a new one. i followed the guides, got my new drive setup, got my key requested, got unraid activated and setup cloud back up. today a month or 2 later i logon and it says trial mode? what gives?

a checkdisk is only possible if the flash drive powers up and is seen the by the PC. i'll try that first. HOWEVER i have been told i plug my data drives in to a linux PC and pull my data off my drives since they are XFS? This would impliy i can simply get my data THEN blow the whole thing away like a gun fight in an 80s movies and start over as i please!

guess i just need to find a 16gb sata SSD and put it in a sata to USB enclosure. i'm done with flash. every flash drive in my ESXi host bit the dust, one by one. i got some loose ideas. it sounds like i can image a new flash device and i can remount my existing drives with data? something about boot up will auto start array and wipe the data? don't mount the parity drive?

running ls in boot folder brings nothing var/logs is there and so i see file names when looking in disks under mnt EDIT: can i pull the flash drive out of the running server to see how bad it's fried? EDIT: no dockers or any of that who-ha, just data shares EDIT: i know that my parity drive is the only drive that is 8tb the rest are data. Apr 5 10:16:30 unraid1 avahi-daemon[28440]: Leaving mDNS multicast group on interface lo.IPv6 with address ::1. Apr 5 10:16:30 unraid1 avahi-daemon[28440]: Leaving mDNS multicast group on interface lo.IPv4 with address 127.0.0.1. Apr 5 10:16:30 unraid1 avahi-daemon[28440]: avahi-daemon 0.8 exiting. Apr 5 10:16:30 unraid1 kernel: sd 9:0:3:0: [sde] tag#4042 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=2s Apr 5 10:16:30 unraid1 kernel: sd 9:0:3:0: [sde] tag#4042 Sense Key : 0xb [current] Apr 5 10:16:30 unraid1 kernel: sd 9:0:3:0: [sde] tag#4042 ASC=0x44 ASCQ=0x0 Apr 5 10:16:30 unraid1 kernel: sd 9:0:3:0: [sde] tag#4042 CDB: opcode=0x88 88 00 00 00 00 00 ba fc 68 b8 00 00 00 08 00 00 Apr 5 10:16:30 unraid1 kernel: blk_update_request: I/O error, dev sde, sector 3137104056 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Apr 5 10:16:30 unraid1 kernel: md: disk0 read error, sector=3137102008 Apr 5 10:16:30 unraid1 root: Starting Avahi mDNS/DNS-SD Daemon: /usr/sbin/avahi-daemon -D Apr 5 10:16:30 unraid1 avahi-daemon[28646]: Found user 'avahi' (UID 61) and group 'avahi' (GID 214). Apr 5 10:16:30 unraid1 avahi-daemon[28646]: Successfully dropped root privileges. Apr 5 10:16:30 unraid1 avahi-daemon[28646]: avahi-daemon 0.8 starting up. Apr 5 10:16:30 unraid1 avahi-daemon[28646]: Successfully called chroot(). Apr 5 10:16:30 unraid1 avahi-daemon[28646]: Successfully dropped remaining capabilities. Apr 5 10:16:30 unraid1 avahi-daemon[28646]: Loading service file /services/sftp-ssh.service. Apr 5 10:16:30 unraid1 avahi-daemon[28646]: Loading service file /services/smb.service. Apr 5 10:16:30 unraid1 avahi-daemon[28646]: Loading service file /services/ssh.service. Apr 5 10:16:30 unraid1 avahi-daemon[28646]: Joining mDNS multicast group on interface br0.IPv4 with address 192.168.0.240. Apr 5 10:16:30 unraid1 avahi-daemon[28646]: New relevant interface br0.IPv4 for mDNS. Apr 5 10:16:30 unraid1 avahi-daemon[28646]: Joining mDNS multicast group on interface lo.IPv6 with address ::1. Apr 5 10:16:30 unraid1 avahi-daemon[28646]: New relevant interface lo.IPv6 for mDNS. Apr 5 10:16:30 unraid1 avahi-daemon[28646]: Joining mDNS multicast group on interface lo.IPv4 with address 127.0.0.1. Apr 5 10:16:30 unraid1 avahi-daemon[28646]: New relevant interface lo.IPv4 for mDNS. Apr 5 10:16:30 unraid1 avahi-daemon[28646]: Network interface enumeration completed. Apr 5 10:16:30 unraid1 avahi-daemon[28646]: Registering new address record for 192.168.0.240 on br0.IPv4. Apr 5 10:16:30 unraid1 avahi-daemon[28646]: Registering new address record for ::1 on lo.*. Apr 5 10:16:30 unraid1 avahi-daemon[28646]: Registering new address record for 127.0.0.1 on lo.IPv4. Apr 5 10:16:30 unraid1 emhttpd: shcmd (793855): /etc/rc.d/rc.avahidnsconfd restart Apr 5 10:16:30 unraid1 root: Stopping Avahi mDNS/DNS-SD DNS Server Configuration Daemon: stopped Apr 5 10:16:30 unraid1 root: Starting Avahi mDNS/DNS-SD DNS Server Configuration Daemon: /usr/sbin/avahi-dnsconfd -D Apr 5 10:16:30 unraid1 avahi-dnsconfd[28655]: Successfully connected to Avahi daemon. Apr 5 10:16:30 unraid1 kernel: sd 9:0:3:0: [sde] tag#4041 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=2s Apr 5 10:16:30 unraid1 kernel: sd 9:0:3:0: [sde] tag#4041 Sense Key : 0xb [current] Apr 5 10:16:30 unraid1 kernel: sd 9:0:3:0: [sde] tag#4041 ASC=0x44 ASCQ=0x0 Apr 5 10:16:30 unraid1 kernel: sd 9:0:3:0: [sde] tag#4041 CDB: opcode=0x88 88 00 00 00 00 00 be 5d 34 f0 00 00 00 08 00 00 Apr 5 10:16:30 unraid1 kernel: blk_update_request: I/O error, dev sde, sector 3193779440 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Apr 5 10:16:30 unraid1 kernel: md: disk0 read error, sector=3193777392 Apr 5 10:16:31 unraid1 avahi-daemon[28646]: Server startup complete. Host name is unraid1.local. Local service cookie is 2525190548.

server is still on but, the pages on the web gui are blank it says flash corrupted and failed. ain't no chance i can copy the config is there? I DO BELIEVE that with no config setting up a new flash drive will loose all my share in of and all the data on my drives. EDIT: oh yeah, the parity has been having some errors and one of the drives died thankfully that dead drive didn't have any important data on it. FYI, i'm posting in case there is any chance i can save my config before i power down my server. like many of my newer flash drives i believe history dictates that it probably died. (i'm flashing to a satadom or SSD this time forget flash drives) EDIT: bash/command line button on webgui seems to work. EDIT: SMB shows the flash folder but windows or ..unraid... keeps trying to auth against AD and i never succeeded at binding. i think windows login is being wierd EDIT:Version: 6.10.0-rc2

is there a way to make unraid re import/mount or use a drive that previously gave error after i swapped cables? EDIT: https://wiki.unraid.net/Manual/Storage_Management#Rebuilding_a_drive_onto_itself

EDIT: it's working now after replugging everything, heres to hoping the 8tb SSD i took a paypal credit loan on to buy off ebay isn't jacked. unraid1-syslog-20220129-0204.zip

unraid1-syslog-20220129-0149.zip attaching log file