Jump to content

SamHill

Members
  • Posts

    31
  • Joined

  • Last visited

Posts posted by SamHill

  1. 31 minutes ago, JorgeB said:

    You can, but the same thing will happen again, format disk2, stop array, start array, disk2 should no longer mount, stop array, now copy the MBR the other way around, disk4 MBR to disk2, reboot and should be fixed.

     So I would run the command below correct?

     

    dd if=/dev/sdf of=/dev/sdc bs=512 count=1

  2. 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.

  3. 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.

    unRAID Snip.PNG

  4. 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.

  5. 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.

  6. 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?

     

     

     

  7. 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.

     

  8. 6 hours ago, jonathanm said:

    Probably need to enable SMB V1

    https://www.ionos.com/digitalguide/server/configuration/windows-smb/

    But you should plan to upgrade Unraid if you want to keep using it. I recommend budgeting for a new pair of hard drives at the same time, that way you can be sure of having enough free space to do the recommended file system conversion after you upgrade.

     

    thanks, but that didnt seem to work.

    *scratches head*

×
×
  • Create New...