• Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About eweitzman

  • Rank


  • Gender

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. @omnicorp How does unraid verify the drive's "signature" against the key file without being a flash drive? Thanks, - Eric
  2. @mattie112 I've created a bootable VHDX with a copy of my flash drive's contents. unraid's boot menu displays, and unraid will start to boot, but it fails while creating the virtual file system with these messages: /dev/root: Can't open blockdev VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6 Please append a correct "root=" boot option: here are the available partitions: [no partitions are listed] Kernel panic - no syncing: VFS: Unable to mount root fs on unknown-block(0,0) How were you able to boot an unraid guest under hyper-v? Thanks,
  3. Hi. I built a new system around a Supermicro M12SWA-TF motherboard and threadripper pro CPU. It's been running headless for a week now with video and keyboard on the BMC controller to access IPMI and unraid's boot screen. I just installed an RTX 3060 PCIe video card and am trying to get the system working with it. The UEFI bios is set to send VGA to the PCIe video card. The system and unraid work with the video card: during boot, diagnostics come to the monitor connected to the 3060 and the login prompt displays. When I choose to boot unraid in GUI mode, however, after
  4. As I documented in this general support thread, unraid 6.9.1 requires the root account to have a password for many functions to work. I've been able to run unraid with no root password (and without the friction this causes) for over a decade. Nothing in my circumstances or practices has required changing this now. A root password is required by ssh samba connections from windows 10 web UI Root passwords are not required by telnet console access Please either revert to the behavior of previous unraid builds that don't requi
  5. There's no good reason to force security enhancements on users who do not want/need them. I've been able to run unraid with no root password (and no friction) for over a decade. Nothing in my circumstances or practices has required changing this now.
  6. @John_M - Thanks for taking the time to point this out in the release notes. (They've moved to https://wiki.unraid.net/Manual/Release_Notes/Unraid_OS_6.9.0#SSH_Improvements now.) This explains what I've discovered re ssh requiring that root have a password, but doesn't explain either why this is now required nor why other avenues of access (telnet, web UI, samba) do or don't require it. I'll have to find out how to register a complaint with management. Thanks, - Eric
  7. I've just found another use case where a non-existent root password is required: browsing samba drives from windows. Arg!
  8. Thanks. I'll check it out tomorrow after a parity check completes.
  9. It's only required by 6.9.1's build or config of rsh/ssh, and not required in other places. Can this be configured by the user? Why the change?
  10. I have no password on the unraid root account. rsh/ssh prompt for the password and will not log in when the enter key is pressed. This is new behavior in 6.9.1: I have been using ssh for root without a password successfully like forever. telnet connects without requiring a password. The GUI itself opens without requiring a password. The web GUI console opens without requiring a password. Any suggestions? Thanks, - Eric
  11. The os returns "No such file or directory" when I try to put unraid to sleep by this command: echo 3 > /proc/acpi/sleep The directory is there and appears to be writable. The file "wakeup" is there. I can cd to /proc/acpi. I get the same error trying to create any file in /proc/acpi. User is root: sudo shows no difference. This is behaving as if the directory or partition is read-only. root@unraid:/proc/acpi# pwd /proc/acpi root@unraid:/proc/acpi# whoami root root@unraid:/proc/acpi# echo 3 > sleep bash: sleep: No such file or directory root@unr
  12. Hi. I'm a longtime developer, new to development on slackware. Discovered pkgtools is the package manager. But it seems that the gui program pkgtool is missing from unraid 4.7.2. The other pkg commands {remove, install, etc}pkg are here and running. So I pulled pkgtool out of the lastest package distibution at http://ftp.slackware.com/pub/slackware/slackware64-current/slackware64/a/pkgtools-15.0-noarch-28.txz, put it in /sbin with the other *pkg files, chmod +x, installed dialog, et voila, I have pkgtool for the moment -- at least until the next reboot. pkgtools-15.0-no-arch-23 is
  13. I skipped 6.4.1 and went to 6.5 and have two drives with crc errors. Would you mind describing how to acknowledge them? I see the crc counts in the smart listing on the affected drives' pages highlighted in orange, but there are no buttons, etc, to acknowledge the error. Thanks, - Eric
  14. Will updating a drive's firmware cause any data loss? If not, is it safe to update the firmware if the drive is part of the array? That is, will any portions of the disk be changed (such as a signature) that would invalidate parity? In case the answer depends on the drive/manufacturer, I'd like to update a WD Red WD60EFRX from version 68MYMN0 to 68MYMN1. Thanks, - Eric
  15. Interesting advice, but has rfs really rotted such that it's no longer usable? This 6TB drive has 750GB free so the "nearly full" theory doesn't apply. I have several other 6TB drives that *are* nearly full but have never had rfs problems. In fact, this is the only time I've seen this problem in seven years of using rfswith unRAID. The array has been up and moving data around, including from/to this disk, for about 12 hours now. Mystery.