SamHill

Members
  • Posts

    31
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

SamHill's Achievements

Noob

Noob (1/14)

2

Reputation

  1. All drives are on XFS now and okay. Thanks alot for the help.
  2. So I would run the command below correct? dd if=/dev/sdf of=/dev/sdc bs=512 count=1
  3. Think i found what your looking for. unaligned.disk4.mbr
  4. No problem. I ran the command. I assume it is on the thumbdrive? How do I access it. Do I need to shut it down and put the thumbdrive in a windows machine, or is there a way to access it another way?
  5. Sorry, here is the new diag, forgot to attach it. tower-diagnostics-20231228-1043.zip
  6. Awesome. Thank you so much. That seemed to work. Everything is fine. Now I can reformat my disk2. Here is how I have been doing it. Is this the correct way? I have been stopping the array changing file system to XFS for the needed disk Starting the array Formatting the drive stopping the array then starting the array again to make sure its good Just dont want another issue like this.
  7. Thank you for the help. I do have a spare 2TB drive and slot location if that will help with the process. So I have a few questions. Question 1 Is this the command to back up disk4 MBR? dd if=/dev/sdf of=/boot/disk4.mbr bs=512 count=1 Not sure how to find the disk4 identifier, but I haven't done anything since the diag but stop the array, so it should hopefully be the same. How do I check what the identifier is? I have attached an image and highlighted what I believe are the identifiers. Do I check with the array started or stopped. It is currently stopped. Question 2 Where does the back up go? Question 3 How do I implement those commands? I assume I just type the commands in the terminal? Do I have to start the array before doing these commands, or keep the array off? Thanks again.
  8. Correct, Disk 2 was the last drive I needed to format to XFS. Disk 2 has been emptied to disk 4. Disk 2 just needs to be formatted now. The issue is Disk 4 was formatted to XFS, and was fine, until I moved all Disk 2's data on it. Now, when I start the array to format Disk 2, now it shows Disk 2 AND Disk 4 needs a file system. Disk 4 was a valid drive formatted as XFS until I moved Disk 2 content to it and stopped the array.
  9. Thanks. Not sure if I did this right. Let me know. Thanks for the help, I truly appreciate it, as I would love to not lose the data. tower-diagnostics-20231227-2242.zip
  10. I was using unBalance to move the info if that makes a difference. Also, I dont know how to save and attach the log file, if that is needed. Drive 2 will come up if I put the format back to riserFS, but it is empty. Drive 4 that has about 1.5TB of data is still showing no format, but the drive has data on it still. Thanks for any help.
  11. I have been updating my ReiserFS to XPS file system. I successfully replaced drive 3 and it updated correctly. Issue was, I didn’t change the format as it was still RiserFS. I moved all the data off onto other drives and then when it was empty, I shut down the array, selected the drive 3 and chose the XFS format. Once I started the array, it told me to format Disk 3 which I did. It came up fine. Moved everything from Drive 4 which was RiserFS as well, and moved it to the newly XFS formatted drive 3. I shut down the array, selected the drive 4 and chose the XFS format. Once I started the array, it told me to format Disk 4 which I did. It came up fine. Now Here is the issue. Drive 2, which is my last RiserFS drive. I moved all the info onto the newly setup drives 3 and 4. I shut down the array, selected the drive 2 and chose the XFS format. Once I started the array, it told me to format Disk 2 AND Disk 4 as there is no known format. I found this snippet if it helps: Dec 27 17:32:27 Tower kernel: XFS (md4p1): Invalid superblock magic number Dec 27 17:32:27 Tower root: mount: /mnt/disk4: wrong fs type, bad option, bad superblock on /dev/md4p1, missing codepage or helper program, or other error. Dec 27 17:32:27 Tower root: dmesg(1) may have more information after failed mount system call. Dec 27 17:32:27 Tower emhttpd: shcmd (23097): exit status: 32 Dec 27 17:32:27 Tower emhttpd: /mnt/disk4 mount error: Unsupported or no file system Dec 27 17:32:27 Tower emhttpd: shcmd (23098): rmdir /mnt/disk4 Any ideas?
  12. Got the process going correctly. Your link above was exactly what I needed. Had to read it a few times to get comfortable with the process, but it is in the copy parity info stage at the moment. Thanks again for the help in this situation. Much appreciated.
  13. So I need to do the Parity swap to the larger new 4TB drive. Once that is done, I can replace the disabled 2TB drive with the other new 4TB drive. Is that correct?
  14. Current system: 2TB - Parity 2TB - Disk 1 Data 2TB - Disk 2 Data 2TB - Disk 3 Data (disabled due to failure) 2TB - Disk 4 Data Goal: I want to replace Disk 3 with a 4TB drive. I bought (2) 4TB drives. One to replace the failed drive The other I believe I need to upgrade the parity to match the 4TB size. Hopefully that makes more sense. Thanks for the help.
  15. So it seems I update the Parity first, then the data drive. I wasnt sure, since my bad drive is disabled. Thanks.