PeterTheN00b

Members
  • Posts

    6
  • Joined

  • Last visited

PeterTheN00b's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Hi All; I just upgraded my Parity Drive from an 8TB to 10TB disk. Saved a backup of my config prior to swap Went to Main tab of Web GUI and did a shutdown of system. Physically swapped out 8TB Parity drive and replaced with new 10TB drive Powered on machine Changed Parity Drive to None Started Array - normal mode not Maintenance mode Stopped Array Updated Parity Drive info to point at new physical disk Started Array - normal mode not Maintenance mode Parity sync / data rebuild started Numerous instances of drives overheating so paused / resumed Parity sync / data rebuild multiple times (took 3 days) Noted that one data disk showed as Unmountable: Not mounted Upon completion of parity sync / data rebuild --> went to disk 1 page and ran Check with -n option - stupidly did not save output Ran Check with no options and got a long string of data (attached) Ran Check again with -n option and got a short report I don't understand what the check did/did not do so I need some guidance. Have attached: Output from Check command Diagnostics file produced after attempt to use Check to fix drive (previously stated I was a doofus and did not copy initial Check output) Supplementary data: screen snip of notifications from startup after swapping physical parity drive during parity rebuild - (I cleared all the ones about disks getting hot and returning to normal temperature). Notification messages: List of installed Docker Containers List of installed plugins (2) System Info Version: UNRAID 6.9.2 MOTHERBOARD ASRock B550M Pro4 American Megatrends International, LLC., Version P2.20 BIOS dated: Tue 03 Aug 2021 12:00:00 AM EDT Processor AMD Ryzen 5 5600G with Radeon Graphics @ 3900 MHz MEMORY 16 GiB DDR4 Utilization: 12% Maximum size: 128 GiB RAM 12% Flash 5% Usable size: 15.0 GiB Log 1% Docker 15% IDEALTower Disk 1 Check Output.txt idealtower-diagnostics-20211128-2305.zip IDEALTower Supplementary screenshots and check output.zip
  2. In the section of the manual on adding disks there is a minor typo as shown below WHOLE should in fact be WHILE. Adding disks Clear v Pre-Clear Under Unraid a 'Clear disk is one that has been completely filled with zeroes and contains a special signature to say that it is in this state. This state is needed before a drive can be added to a parity-protected array without affecting parity. If Unraid is in the process of writing zeroes to all of a drive then this is referred to as a 'Clear' operation. This Clear operation can take place as a background operation while using the array, but the drive in question cannot be used to store data until the Clear operation has completed and the drive been formatted to the desired File System type. A disk that is being added as a parity drive or one that is to be used to rebuild a failed drive does not need to be in a 'Clear' state as those processes overwrites every sector on the drive with new contents as part of carrying out the operation. In addition, if you are adding an additional data drive to an array that does not currently have a parity drive there is no requirement for the drive to be clear before adding it. You will often see references in the forum or various wiki pages to 'Preclear'. This refers to getting the disk into a 'Clear' state before adding it to the array. The Preclear process requires the use of a third-party plugin. Prior to Unraid v6, this was highly desirable as the array was offline whole while Unraid carried out the 'Clear' operation. but Unraid v6 now carries out 'Clear' as a background process with the array operational while it is running so it is now completely optional. Many users still like to use the Preclear process as in addition to putting the disk into a clear state it also performs a level of 'stress test' on the drive which can be used as a confidence check on the health of the drive. The Preclear as a result takes much longer than Unraid's more simplistic 'clear' operation. Many users like to Preclear new disks as an initial confidence check and to reduce the chance of a drive suffering from ‘what is known as infant mortality’ where one of the most likely times for a drive to fail is when it is first used (presumably due to a manufacturing defect). It is also important to note that after completing a 'Preclear' you must not carry out any operation that will write to the drive (e.g. format it) as this will destroy the 'Clear' state.
  3. Hi All; I used the USB Creator Tool to make a bootable UNRAID drive which I am trying to run on an old HP Mediasmart server (EX470) but when I start the machine up it skips right over the USB and starts windows home server (WHS 2003). I used UNRAID CD Creator Tool V 1.6 Windows X32 to install UNRAID Version 6.9.2 (Stable) I have checked the BIOS and I have USB-FDD selected as my first boot option. I am running an AMD Athlon 64 X2 3800+ (ADD3800IAA5CU) with 4GB of RAM. Any tips or ideas would be much appreciated...
  4. I too an trying to resurrect my HP Mediasmart server (EX470) as an Unraid box. I just upgraded to an Athlon X2 300+ CPU and 4GB of RAM after doing ymboc's bios hack. I used the CD Creator tool to make an Unraid USB stick. The Unraid USB is not booting on EX470. I have tried all the USB slots without success. It keeps starting up and then starts up Windows. Any suggestions would be appreciated. I have a VGA cable so I can get into and see the BIOS.