fastedd

Members
  • Posts

    6
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

fastedd's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Although the disk may have HPA, is there a chance that the sata cable to the drive could be loose. Have you been into the case recently while fixing the parity disk and possibly dislodged the cable. The following bit in the sys log shows the start of repeated attempts to connect to the drive: Mar 9 22:18:04 NAS kernel: ata3.00: exception Emask 0x10 SAct 0x0 SErr 0x4810000 action 0xe frozen Mar 9 22:18:04 NAS kernel: ata3.00: irq_stat 0x08400040, interface fatal error, connection status changed Mar 9 22:18:04 NAS kernel: ata3: SError: { PHYRdyChg LinkSeq DevExch } Mar 9 22:18:04 NAS kernel: ata3.00: failed command: READ DMA EXT Mar 9 22:18:04 NAS kernel: ata3.00: cmd 25/00:00:d8:7f:27/00:04:1f:00:00/e0 tag 0 dma 524288 in Mar 9 22:18:04 NAS kernel: res 50/00:00:d7:7f:27/00:00:1f:00:00/e0 Emask 0x10 (ATA bus error) Mar 9 22:18:04 NAS kernel: ata3.00: status: { DRDY } Mar 9 22:18:04 NAS kernel: ata3: hard resetting link Mar 9 22:18:10 NAS kernel: ata3: link is slow to respond, please be patient (ready=0) Mar 9 22:18:04 NAS kernel: ata3: hard resetting link Mar 9 22:18:10 NAS kernel: ata3: link is slow to respond, please be patient (ready=0) Mar 9 22:18:12 NAS kernel: ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Mar 9 22:18:12 NAS kernel: ata3.00: configured for UDMA/133 Mar 9 22:18:12 NAS kernel: ata3: EH complete Which repeats until the link is downgraded from 3.0 Gbps to 1.5 Gbps until eventually Mar 10 04:37:49 NAS kernel: ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Mar 10 04:37:49 NAS kernel: ata3.00: HPA detected: current 3907027055, native 3907029168 Mar 10 04:37:49 NAS kernel: ata3.00: ATA-8: WDC WD20EURS-63S48Y0, 51.0AB51, max UDMA/133 Mar 10 04:37:49 NAS kernel: ata3.00: 3907027055 sectors, multi 0: LBA48 NCQ (depth 31/32), AA Mar 10 04:37:49 NAS kernel: ata3.00: configured for UDMA/133 Mar 10 04:37:49 NAS kernel: ata3: EH complete Mar 10 04:37:49 NAS kernel: scsi 2:0:0:0: Direct-Access ATA WDC WD20EURS-63S 51.0 PQ: 0 ANSI: 5 Mar 10 04:37:49 NAS kernel: sd 2:0:0:0: Attached scsi generic sg0 type 0 Mar 10 04:37:49 NAS kernel: sd 2:0:0:0: [sdf] 3907027055 512-byte logical blocks: (2.00 TB/1.81 TiB) Mar 10 04:37:49 NAS kernel: sd 2:0:0:0: [sdf] 4096-byte physical blocks Mar 10 04:37:49 NAS kernel: sd 2:0:0:0: [sdf] Write Protect is off Mar 10 04:37:49 NAS kernel: sd 2:0:0:0: [sdf] Mode Sense: 00 3a 00 00 Mar 10 04:37:49 NAS kernel: sd 2:0:0:0: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Mar 10 04:37:49 NAS kernel: sdf: sdf1 Mar 10 04:37:49 NAS kernel: sd 2:0:0:0: [sdf] Attached SCSI disk Mar 10 04:41:04 NAS kernel: ata3: exception Emask 0x10 SAct 0x0 SErr 0x4010000 action 0xe frozen Mar 10 04:41:04 NAS kernel: ata3: irq_stat 0x00400040, connection status changed Mar 10 04:41:04 NAS kernel: ata3: SError: { PHYRdyChg DevExch } Mar 10 04:41:04 NAS kernel: ata3: hard resetting link Mar 10 04:41:10 NAS kernel: ata3: link is slow to respond, please be patient (ready=0) Mar 10 04:41:13 NAS kernel: ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Mar 10 04:41:13 NAS kernel: ata3.00: configured for UDMA/133 Mar 10 04:41:13 NAS kernel: ata3: EH complete Mar 10 04:41:13 NAS kernel: sdf: detected capacity change from 0 to 2000397852160 Mar 10 05:11:53 NAS kernel: md: disk2 read error Mar 10 05:11:53 NAS kernel: handle_stripe read error: 3625342960/2, count: 1 Mar 10 05:11:53 NAS kernel: REISERFS error (device md2): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [7885 12180 0x0 SD] Mar 10 05:11:53 NAS kernel: REISERFS (device md2): Remounting filesystem read-only Mar 10 05:11:53 NAS kernel: REISERFS error (device md2): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [7885 12180 0x0 SD] Mar 10 05:11:53 NAS kernel: md: disk2 read error The kernel picks up a read error. I would check the condition of the sata cables as well before doing anything else. HTH Ed
  2. Ok, both my desktop and laptop had credentials on each other machines, so i deleted them. Restarted router, unraid and PCs. No difference. I didn't want to change the local master to yes, because all the devices recognize the tower hostname and I have other servers (old ubuntu box) that are on the network and work. However I reckon that its probably the laptop's fault. Even if I attempt to map the drive using the use different credentials tick box, the laptop tries to log on using my works domain and username, while my unraid isn't using domains, its using workgroups. So I select log on as a different user and then it asks for username and password. I typed xyz into username, left the password blank and it maps the drive. So I reckon its all about my works laptop set up to use active directories as its the only device that gave grief. Since it lets me log on using anything typed into the username, I can leave that mapped to tower rather than the IP address. So happy to leave it be at that. Thank you for the help.
  3. Fair enough. Although its not a gigabyte, to these ignorant eyes it looks very much like you have a HPA issue: http://lime-technology.com/forum/index.php?topic=10858.0 the numbers match the signature as does the 2113 sectors difference. However I would still wait until someone more knowledgeable replies, sorry. Ed
  4. I'm a newbiew at unraid, but have been reading through the forums for the last six months or so trying to get familiar with the pitfalls. I had a quick look at your syslog and noticed this line: Mar 10 04:37:49 NAS kernel: ata3.00: HPA detected: current 3907027055, native 3907029168 I'd wait until someone more knowledgeable comes along, but is there a chance you have a gigabyte motherboard like this thread: http://lime-technology.com/forum/index.php?topic=26432.0 Ed
  5. Had a good read of the link, thought it was the same problem, but I don't think so. All my disks and shares are exported and public and don't require username or password from any other computer or media player, just my win 7 laptop and then only if I try to access via \\tower\share name. It works ok via \\ipaddress\share name. Its not a big deal as I know the IP address, just thought it was strange behaviour. Ed
  6. Hello, Came accross some puzzeling behaviour on my newbuild and wanted to check it was correct before plowing ahead. I'm running 5.0RC11 Its still new and I haven't added any passwords to root, nor any new users. I've added shares with split level 0 and all settings are export and public. I've got SMB set to Enable SMB = Yes(Workgroup) and Workgroup = WORKGROUP and Local Master = NP My Win7 Home desktop, shows tower under the Networks folder and I'm able to map all the disks and all the shares (top folder in each disk). All works perfectly and how I would expect it to. On my Win7 Proffessional laptop, it also sees tower under the Network yet whenever I try to access it, win pops up the dialogue for username and password, and I've read that the latest versions of Unraid cannot use root as a network username. If I type \\tower\disk1 for example it also asks for the username and password However if I type \\192.168.1.111\disk1 I get access no problem. Note on this laptop I can also access the webpage using //tower or //192.168.1.111 without a problem. So the questions are, why on one machine must I use the IP address rather than the name to avoid the password pop up and not on another PC. This makes me think its a laptop issure rather than an Unraid issue. The laptop is a company device so may have some funky settings locked down that I don't know about. Note that there is no one else on the network and I don't particulary want to have username and password access to all the disks so I did not intend adding users. cheers all, and BTW the reason I went the unraid route is partially due to the great communitiy support, reminds me a bit of slim devices before logitech screwed up squeezebox. Ed