hlidskialf

Members
  • Posts

    30
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

hlidskialf's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Thank you, that's exactly what I ended up doing. Worked the treat! Cheers!
  2. No, that's not it but you did figure the issue for me. Disk 1 now has all it's files as /mnt/disk 1/disk 1/ as opposed to /mnt/disk 1/. So I think what I need to do is just move everything up one level, correct? Does anyone know the command offhand? Any help would be appreciated. Cheers.
  3. So a bit of a weird one here. I was attempting to follow this guide: https://wiki.lime-technology.com/File_System_Conversion to convert my old disks to the XFS format. (Running UnRaid 6.35) Everything went fairly smooth. I copied the contents of disk1 to disk11, did the switch and prepared to move on. However, when the array started up again, the contents of the new disk1 were added as a new share! (Titled disk1) The files are there, but they are no longer in the other shares the files originally belonged too. Any ideas how I can rectify this? I don't have enough space to just copy the 3TB drive back onto the original shares.
  4. Glad to see you sorted it out. Always an awesome feeling when that happens, 'eh?
  5. I had a similar issue with XBMC a few weeks ago, I also had a drive going bad. It turned out that I also had the parity drive going bad at the same time so it was the replacement of both that fixed the issue. I know it's unlikely to help, but you never know what might be a clue.
  6. Greetings all. I was wondering if there's a command that will generate a file list for a specific drive that I can save to a txt file. I have unfortunately suffered a parity drive failure, which in of itself wouldn't be too much of an issue as I had a warm spare ready to go. However, it appears that I have another hard drive that is throwing up massive errors and the parity rebuild averages at less that 1GB/Sec. As that would take about 3 weeks to rebuild it, as well as various freezups and other issues while it's running it's not feasible. So, it's mostly media stuff that I can redownload if that drive fails it's just a matter of a lot of work/time to replace not irreplacable stuff. I have a new drive being shipped to me, so I'm hoping my dying drive will last until it's installed and precleared. Then I can copy it's contents, swap it for the good drive and rebuild the parity drive properly. Having said that, if it doesn't last and dies before then I was hoping to generate a list of what I'm going to lose before it happens if possible. Anyone know a command line that will take care of that? Cheers, hlid.
  7. So, working on the basis that something integral was corrupted I formatted the flash drive, copied over a pristine download of Unraid and treated it like an upgrade. (No packages, copied over configs, make-bootable script run.) It seems to have done the trick, so thanks for the feedback it pointed me in the right direction. Cheers!
  8. Either Bad/Incorrectly configured RAM (incorrect "timing", "clock speed", or voltage") or The file on the flash drive is corrupted. Well, the server has been running without mishap for a few years, I think the hardware is good. I was hoping it wasn't the flashdrive as I backed up the contents, and already tried recopying the files back with the same result. Any idea what file it might be?
  9. I'm stumped here folks. I did a proper shutdown of the server in order to add a couple more fans. Fired it back up and now right after bzroot is ready, it flashes to the above error then says --System Halted. Any ideas? :'(
  10. I'm going to agree that it's likely a power supply issue, but also going to add that you check 2 other things if the PSU replacement doesn't work. I've had two cases similar to this, in one case, there was a wire to the cpu fan that snagged the fan itself and prevented it from spinning. Basically resulted in an instant overheating situation. It didn't drift into the "snag" position until the unit had been running a fair while and heated up. (like your 20hr preclear scenario) The second and far more hair-pulling issue turned out to be a short of the case's power on switch. That started after the unit had been running for over a year, and drove me nuts to find. In the end, I wired the on/off lead to the reboot button and it's been good ever since. Hope you get lucky though and it's the PSU!
  11. Sorry for the confusion. What I meant was that on many boards, the usb drive will show up under hard drives, not removable media. So it becomes part of the hard drive stack. The hard drive stack has a priority list as well. So, you have to put the flash drive with UNRAID on it to the top of the stack. Then you have the other boot section which is by device type, ie) Removable Media, cd/dvd, hard drive, etc... Under that section, select your hard drive to boot from, which due to being the top of the priorty list of hard drives, your flashdrive will be the selection. Adding/removing drives can mess with your hard drive priorty, and often you'll have to go in and adjust the bios in order to boot after changing hardware. Hope that was less confusing, just had my first sip of coffee for the day.
  12. No, but if you migrate the data off the array, and then back onto it, it'll be added to the existing drives.