November 9, 20241 yr Something got thrown way off with my drive identifications. I did a parity check and that seems to be okay. I have no clue what I'm doing and I don't want to lose my data. I tried doing a disk repair command this morning on one of my unmountable 8tb drive, and after 14 hours, I got "Sorry, could not find valid secondary superblock" in the terminal. I attached my diagnostics. Thanks all. valhalla-diagnostics-20241108-2308.zip
November 9, 20241 yr Community Expert 4 hours ago, JustinRampage said: I tried doing a disk repair command this morning on one of my unmountable 8tb drive Was this via the command line or via the GUI? When done via the command line users frequently get the device name wrong so it is much better to do it via the GUI.
November 9, 20241 yr Community Expert Reboot to clear the logs and post new diags after array start, also the output from blkid
November 9, 20241 yr Author 5 hours ago, itimpi said: Was this via the command line or via the GUI? When done via the command line users frequently get the device name wrong so it is much better to do it via the GUI. I did do it via the command line.
November 9, 20241 yr Author 5 hours ago, JorgeB said: Reboot to clear the logs and post new diags after array start, also the output from blkid I rebooted, but it changed the name of my two main drives again. 🤔
November 9, 20241 yr Author 11 minutes ago, JorgeB said: Looks like you are using USB? Post new diags. Yep! I’m using a ProBox usb 3.0 enclosure.
November 9, 20241 yr Author 13 minutes ago, JorgeB said: Looks like you are using USB? Post new diags. Here are my new diags. I did not start the array, due to the drives being re IDed. Thanks so much. valhalla-diagnostics-20241109-1019.zip
November 9, 20241 yr Community Expert Solution May be related to the v7 now using the faster UASP driver for USB devices that support it, try adding usb_storage.quirks=2109:0715:u to syslinux.cfg, after /bzroot, then reboot, that will force using the old USB storage driver.
November 9, 20241 yr Author 1 hour ago, JorgeB said: May be related to the v7 now using the faster UASP driver for USB devices that support it, try adding usb_storage.quirks=2109:0715:u to syslinux.cfg, after /bzroot, then reboot, that will force using the old USB storage driver. Hey! That got the original IDs back. I really wish that I didn't dive into the beta. Thank you SO much, @JorgeB! Do you recommend that I get a better setup for my drives? I have been switching my network over to UniFi. I saw that they have a UNAS Pro - https://techspecs.ui.com/unifi/integrations/unas-pro Now I have zero clue which drive goes where. Ugh. Edited November 9, 20241 yr by JustinRampage
November 9, 20241 yr Author I think that I got everything situated! I found an old system log from 2023 that had this: Sep 16 10:08:51 Valhalla kernel: mdcmd (1): import 0 sdb 64 7814026532 0 ST8000DM004-2U9188_ZR14W591 Sep 16 10:08:51 Valhalla kernel: md: import disk0: (sdb) ST8000DM004-2U9188_ZR14W591 size: 7814026532 Sep 16 10:08:51 Valhalla kernel: mdcmd (2): import 1 sda 64 7814026532 0 ST8000DM004-2U9188_ZR14VNNP Sep 16 10:08:51 Valhalla kernel: md: import disk1: (sda) ST8000DM004-2U9188_ZR14VNNP size: 7814026532 So I gathered that disk0 was parity and I'm doing a parity check right now. It's looking hopeful! @JorgeB Edited November 9, 20241 yr by JustinRampage
November 10, 20241 yr Community Expert 16 hours ago, JustinRampage said: Do you recommend that I get a better setup for my drives? Yes, USB is not recommended for array or pool devices, so I would recommend using SATA/SAS.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.