nteau

Members
  • Posts

    10
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

nteau's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Experienced this issue.. uninstalled Dynamix System Stats and re-installed, error has since stopped
  2. solved: Each torrent's data dir was /mnt/user (unraid v5) and not /download (as per container unraid v6).. Updating each torrent individually and verifying - appears to be all good now!
  3. Downloaded and installplg. Initially had a SSL certificate area connecting to the https address to download images (device_status.png, new_config.png and information.png) so downloaded manually, and removed that code from the plg. Re-installplg and running sweeeeeeet as. Thank you
  4. [sOLVED] FYI, using Explorer I manually located each of the lowercase duplicate share folders within disk1 or disk2 or disk3 ie "apps" and cut/paste the contents to "Apps". deleted the "apps" dupe folder and 'included' disk1, disk2, disk3 under Settings>Share Settings Menu. this restarted SMB and I can now view the shares properly
  5. Hi Guys Had a brownout recently and the USB drive containing unRAID went corrupt. I've reinstalled and have completed the disks' first mount. It ran what looked like a parity check at that stage however, unMENU listed that there was "15123" days since last parity check - so I am running this parity check now. In the meanwhile, unRAID has detected user shares and automatically created these. Bizarrely enough, there are now a few dupes of my user shares ie "Apps" and "apps" - which have very different file contents. My Windows user share seems to only read the "apps" share with less files: Is this a simple issue which will be fixed once this parity check is done? Or is there more manual effort required in correcting this? Thanks in advance
  6. thanks for your quick response Helmonder I gave that a shot and unfortunately there was no (detected) corrupt data, however, i formatted the flash drive and tried a fresh copy of 5.0-rc8a - which worked a treat. i am rebuilding my parity as i type. thanks again for your help
  7. Hi there Last night I stopped my transmission daemon (via unmenu) and initiated a parity validation through Unmenu. Today, I proceeded with a further parity check and correction - both times no faults were detected and therefore, none corrected. It had been about a month since my last parity check/correct. I checked User scripts and for some reason the Transmission daemon was appearing as running (Unmenu gave me the option to 'Stop Transmission' rather than 'Start..'). I clicked 'Stop..' again and the screen refreshed after a moment and the daemon still appeared to be running (the button still displayed 'Stop Transmission'). I gave this a final shot and no success. I attempted to Stop Array, when the page refreshed and timed out immediately. I couldn't ping the server, nor could I load up the standard web interface via http. (Historically I have had similar occur, and a manual reset & parity check correct the issue.) I proceeded to manually reset and upon restart I received a REISERF error; (I'm unable to access unraid and unable to dump a SYSLOG, so I have transcribed what appear to be the error messages on screen) ###################### sd 0:0:0:0: [sda] Attached SCSI removable disk end request: I/O error, dev fd0, sector 0 REISERF warning (device fd0): sh2006 read_super_block: bread failed (dev, fd0, block 2, size 4096) REISERF warning (device fd0): sh2006 read_super_block: bread failed (dev, fd0, block 16, size 4096) end_request: I/O error, dev fd0, sector 0 end_request: I/O error, dev fd0, sector 2 EXT3-fs (fd0): error: unable to read superblock end_request: I/O error, dev fd0, sector 0 end_request: I/O error, dev fd0, sector 2 EXT2-fs (fd0): error: unable to read superblock end_request: I/O error, dev fd0, sector 0 end_request: I/O error, dev fd0, sector 2 EXT4-fs (fd0): error: unable to read superblock end_request: I/O error, dev fd0, sector 0 end_request: I/O error, dev fd0, sector 2 FAT-fs (fd0): unable to read boot sector VFS: Cannot open root device "(null)" or unknown-block(2,0): error -5 Please append a correct "root=" boot option; here are the available partitions: 0200 4 fd0 driver: floppy 0800 3907584 sda driver: sd 0801 3907552 sda1 00000000-0000-00000-000000000000 Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0) Pid: 1, comm: swapper/0 Not tainted 3.4.11-unRAID #1 Call Trade: [<c131dc20>] panic+0x7d/0x16a [<c1343b56>] mount_block_root+0x1d2/0x1e6 [<c108e794>] ? sys_mknod+0x15/0x17 [<c14542c2>] ? repair_env_string+0x53/0x53 [<c1454bd7>] mount_root+0x6d/0x75 [<c1454cf0>] prepare_namespace+0x111/0x138 [<c154390>] kernel_init+0xce/0xda [<c13208f6>] kernel_thread_helper+0x6/0xd ###################### system hangs at this point i have a parity drive and 3 data drives in my configuration. all disks appear in the bios and post screen. i believe i can feel movement on all disks at startup of the unit. i am unsure as where to go from here; i have searched the forums for advice and have noted kernel errors linked to hardware/cables, so have been through the system and unplugged/replugged everything. would anyone have any advice or guidance with this issue? i'd be most appreciative. cheers, nate