Re: F5-221 crashes / disconnects
Posted: 19 Jul 2020, 22:41
Welp, did some more testing and the system seems pretty messed up.
Installed just a laptop hard drive to see what's going on, and it ran reasonable well for around 20 hours as long as I didn't do anything. I installed my Ironwolf drives after that to check for bad blocks, and the system started hanging again.
When I restarted, my old drives got recognized somehow but the system was again unstable.
I removed my drives again and did a scan on a Linux PC, the drives seemed fine: https://dpaste.com/7NYH8AHFH. I doubt that a single failed checksum causes all these issues.
After backing up I formatted my Ironwolf drives and reinstalled the system again. Again, unstable, the system crashed right away when copying files.
As another test, I reinstalled the OS again, this time on my laptop drive, and started copying files with SMB. The system again crashed pretty quickly, but this time I got a juicy error from /var/log/messages: https://dpaste.com/GU8UGJ8MF
By the way, there seems to be no option during the installation process to completely wipe the drive and start over. I have the feeling that this causes part of the issue: often previously installed programs still appear on the desktop in a broken state.
So to recap what I've tried:
* Ironwolf drives with old TOS: crashes on streaming media
* Ironwolf drives with reinstalled TOS: stable for around 20 hours, then crashes
* Laptop drive with reinstalled TOS: stable for around 20 hours if you do nothing, crashes on blocks check.
* Formatted ironwolf drives with reinstalled TOS: crashes on copying files.
* Reinstalled laptop drive: crashes on copying files.
* Hard drives in Linux PC: work fine.
It seems like something about this OS just crashes whenever you do too much with the hard drives. I'm a pretty technical user and I'm open to working with the team, if you want we can open a remote session so you can see what's going on.
It's really disappointing that both of the devices I've had failed so quickly. They're not cheap machines. Please resolve this!
Installed just a laptop hard drive to see what's going on, and it ran reasonable well for around 20 hours as long as I didn't do anything. I installed my Ironwolf drives after that to check for bad blocks, and the system started hanging again.
When I restarted, my old drives got recognized somehow but the system was again unstable.
I removed my drives again and did a scan on a Linux PC, the drives seemed fine: https://dpaste.com/7NYH8AHFH. I doubt that a single failed checksum causes all these issues.
After backing up I formatted my Ironwolf drives and reinstalled the system again. Again, unstable, the system crashed right away when copying files.
As another test, I reinstalled the OS again, this time on my laptop drive, and started copying files with SMB. The system again crashed pretty quickly, but this time I got a juicy error from /var/log/messages: https://dpaste.com/GU8UGJ8MF
By the way, there seems to be no option during the installation process to completely wipe the drive and start over. I have the feeling that this causes part of the issue: often previously installed programs still appear on the desktop in a broken state.
So to recap what I've tried:
* Ironwolf drives with old TOS: crashes on streaming media
* Ironwolf drives with reinstalled TOS: stable for around 20 hours, then crashes
* Laptop drive with reinstalled TOS: stable for around 20 hours if you do nothing, crashes on blocks check.
* Formatted ironwolf drives with reinstalled TOS: crashes on copying files.
* Reinstalled laptop drive: crashes on copying files.
* Hard drives in Linux PC: work fine.
It seems like something about this OS just crashes whenever you do too much with the hard drives. I'm a pretty technical user and I'm open to working with the team, if you want we can open a remote session so you can see what's going on.
It's really disappointing that both of the devices I've had failed so quickly. They're not cheap machines. Please resolve this!