• Posts

  • Joined

  • Last visited


  • Gender
  • Location

Recent Profile Visitors

814 profile views

Freddie's Achievements


Apprentice (3/14)



  1. Yes, those are the instructions, but the formatting on the wiki makes it easy to misunderstand and try to delete one file called: "config/shadow config/smbpasswd" OP said "Shadow config folder didn't exist"
  2. Perhaps the password reset instructions need an edit. @Kastro you seem to have tried to delete a single file called: "config/shadow config/smbpasswd" I think the instruction should be to delete two files: "config/shadow" "config/smbpasswd"
  3. The file modified time stamps do not change, but the directory time stamps do change. The consld8 script uses diskmv which in turn uses rsync to copy files with the -t option flag. The -t option flag preserves the modification times on all files, however, when files are copied to the destination disk and removed from the source disk, the parent directory's modification time is updated by the filesystem.
  4. It breaks down at the first requirement: In unRAID, the virtual device (/dev/md#) is underneath the filesystem and the virtual device does not support FITRIM. unRAID would need to update the parity drive when the actual data drive (/dev/sdX) is trimmed. There was a little discussion about a year ago in this very thread if you want to think more about the details: This wikipedia article helped me differentiate between TRIM and garbage collection: The only part that concerns me is the section about Filesystem-aware garbage collection. From the referenced paper (pdf) and another one (pdf), it appears that some SSD devices did garbage collection after a Windows XP format operation. Windows XP did not have TRIM support but it appears some devices where aware of the format operation anyway and proceeded to do garbage collection. So the question remains, are there any SSD devices that will do garbage collection on data that is still valid in unRAID? I think it is very unlikely but impossible to prove. My little piece of anecdotal evidence: I've been running for over a year with an SSD accelerator drive (Silicon Power 240GB S60). I've run monthly parity checks and once did checksums on parity reconstructed data and found no issues. Some data has been cycled off and on and it has generally been over 95% full. I have no plans to stop using the SSD but I also have full backups.
  5. So my question is what if there isn't enough space on disk8? I have a couple of tasks I would like to perform. [*]Move a bunch of TV shows I have spread across disks 4, 5, 8 & 10 to disks 1, 2, & 3, according to the allocation method I have chosen (high water.) [*]Move a bunch of movies from disks 4, 5, 6 & 7 to disks 5 & 6, again, according to the high water allocation method. Is there a way to achieve this using your tools? Or is there a better way? Sorry, no, my tools completely bypass the allocation method and you have to specify a single destination disk.
  6. I'm sorry you are having troubles Dave. I read through your thread and it looks painful. The next time I mess with consld8 I will consider adding an option to keep the source files.
  7. Thanks Freddie, I really appreciate the info. My 5TB drive should accomodate all of my Movies (at the moment) and then some. As presently configured w/o "usr" directories/shares would the command be "consld8 -f /mnt/Movies disk5" or do I need the "/usr/" in the the command line? Thanks so much for your response and wonderful work! Dave Both diskmv and consld8 are designed to act on user share directories. You must specify a valid user share path. I expect you can simply enable user shares, then /mnt/user/Movies will be a valid user share path and you should be able to run [color=blue]diskmv -f -k /mnt/user/Movies disk1 disk5[/color] .
  8. No need to run diskmv first. When you run consld8, it will call diskmv as many times as needed to consolidate your source directory to the destination disk. For example: [color=blue]consld8 -f /mnt/user/Movies disk8[/color] will move the Movies user share from all other disks to disk8 (if there is enough space).
  9. One of my drives has an increasing Current_Pending_Sector count and it also failed the short SMART test. The Dashboard page still shows a green thumbs up for the SMART status. I would expect see a red or orange thumbs down icon with a drive in this state. Is this a defect that should be changed? This is a test system that has no parity, one cache ssd and a single data drive with problems.
  10. The email account used to log in to windows 10 is not the same as the windows 10 username. To get your windows username, enter 'whoami' at the windows command prompt. That should print your computername\username.
  11. Definitely related. You need valid ssh host keys to do anything over ssh. Did you rename or remove the config/ssh directory on the flash drive and then reboot? No. Maybe. Especially if you continue to see problems with files stored on the usb stick.
  12. SSH is a way to log in to the server from another computer (client) and get a command prompt. Like telnet but newer and more secure. If you haven't used ssh then deleting the directory will not matter. If you have used ssh you might get some warnings when you try to login over ssh again.
  13. These key files are copied from the flash drive during startup. You can rename or remove the config/ssh directory on the flash drive, then reboot and unRAID will generate new key files. This should take care of these error messages, but it will also make the server look different to any SSH clients. Don't know how the files became invalid, maybe points to corrupt flash drive.
  14. I had the same symptoms after changing cache drive from one SSD to another. Seems like unRAID doesn't want to forget about the first cache device. I had to stop array, un-assign cache device, start array, stop array, assign new cache, and start array again. I don't think I had this plugin installed, but I'm not absolutely sure.
  15. I came to the conclusion they are totally harmless. See here for discussion: