newskin

Members
  • Posts

    14
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

newskin's Achievements

Noob

Noob (1/14)

1

Reputation

  1. OK, got it sorted. For anyone coming across this in a similar situation re their parity disk, I set the 'invalid' parity disk as a new array member which caused unRAID to format it. Then assign it back to parity. This will cause an error due to missing disks, but then via tools/new config you can reset it. Thanks itimpi for the guidance.
  2. OK, started the process - rebuilt the GPT hoping that would kick unRAID into recognising an unformatted disk and then I could format via gui. But it is still showing as invalid with no option to format. I am hesitant to format the xfs partition manually as I don't know what flags unRAID sets and assume that all drives need to be identical. Can I just mkfs.xfs /dev/sdc1 ?
  3. The device is question is sdc (id ending WMC4N0F79CZW). Unraid has marked it as faulty (red x in dashboard). Logs show status is DISK_DSBL. In the attached files, the output of 'smartctrl -s on --test=short /dev/sdc' is a result of a test I ran from the shell, the GUI options were ghosted. I don't know what test unRAID does to flag a disk as DISK_DSBL, but I can't see anything physically wrong with the device. Logs attached. nas-diagnostics-20151003-0913.zip
  4. Woke up this morning to find the gui showing my parity 'invalid' . Not sure how long it has been that way, but did a full reboot expecting at worse case I would have to simply rebuild it. On reboot unRaid insists it is invalid and offers no recovery options. I have ssh'd onto my nas and manually run smartctl on the device in question which passes, telling me the device is up and running as far as Linux is concerned. What is the best way to proceed from here? Can I just blow away the partitions and will unRaid rebuild for me, should I rebuild myself or is there a better way? Thanks!
  5. I've been having a bit of an issue with my build all night (6.14b). Started when I was trying to add a drive. Turned out my usb had errors so I fixed these, then battled with a whole load of weird issues which it turns out are caused by the same thing. I'm finding that every time there is a write to the UNRAID usb, it disconnects and reconnects under a different drive letter (increments up one). The os cannot track this by label either, so I manually mount it, cause something to write to it and presto - it drops. If I touch a file onto /boot, it stays ok. I was wondering if this means I have a rubbish usb stick or if anyone has ever come across this before?
  6. Ok, i'm back up and running. A lot my issues seems to be stemming from a bit of bad luck (usb drive constantly needing fixing!) and the fact that the entry in fstab to mount /boot by label does not seem to be working. my usb drive is hopping all over the place and i have finally got it running with a manual mount after double, triple checking for errors. Thanks for all the pointers though!
  7. Looks like /boot is still mounting as read only.. I've attached a log if that helps.
  8. thanks for that garycase - I think I have it set up ok but good to know that you can go that far without losing data. I've put the array online and on further digging I have the correct data in /mnt/user and can scp off my files - i just cant access them via SMB...
  9. Yup, I was able to get my config back with: mount -o noatime,nodiratime,umask=0,shortname=mixed -t vfat /dev/sde1 /boot the drive has changed from sdd to sde, config now recognised but when I start the array my shares are not accessible - worried it has mixed up my parity and data drive, any easy way to tell?
  10. Looks like /boot is not mounted correctly - in the log i see get_key_info returning 'no such file..' and same for read_tokens which would explain why it cannot properly read my drives, any idea why i have no /boot ?
  11. That was a simple fix - got the config loaded and gui back but none of my drives are recognised and I'm in trial mode. I noticed that the new drive is in /dev/sdc which is where my cache drive used to be and now that is sdc - dont know if that makes a difference?
  12. Hi, I just did what I thought was a routine addition of a new drive to the array - powered off nicely, added the new drive, powered on... Unraid will boot but it does not seem to be loading any of my config (I changed the hostname but it has reverted to TOWER, set a static IP but it is doing DHCP) and the webgui does not appear to be running. I checked the USB and all of my config settings are still there so how do I get them to be used? Thanks!
  13. I'm on build 9926 - first one I've used so can't comment on previous. This key isn't present in 9926 either, you have to create it. If you look at a network trace, windows is trying to do a SMB2 auth (using your local account as mentioned above) but as soon as Unraid starts to negotiate, windows sends a RST. Mirroring your win account to unraid sounds like it is a more secure fix but haven't tried it as I'm not fussed!
  14. Had this problem too - it's because Win10 insists on an authenticated SMB login. You can disable it by creating the following value (a DWORD): HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters\AllowInsecureGuestAuth Set the value to 1 , it should work straight away then.