Hard disk problems

[sympton]

Hi

I have 2 x 2tb hdd´s mounted. After a day or so, cannot access drives anymore. It seems they are mounted, but when i ls mount point, it doesnt list anything...

df shows how much space is used etc.. After reboot everything works again ?

What can be the problem here ?

 

[matthewowen01]

Next time run 'zpool status' and let us know.

 

[ProtoSD]

sympton, it's not just you, but it would help if everyone would post what version of FreeNAS they're using when they ask a question like this. Are you using FreeNAS 8.0, 8.01 beta 1/2/3/4? AMD64 or i386?

I've seen this same question asked a lot here lately, try to search some more and add your post to an existing one, you'll have a much better chance at getting an answer instead of people answering the same question in 6 different places, or not answering the 6th one because they already answered 5 other times. I'm not trying to pick on you, this is just for people in general.

Anyway, sorry about that. I haven't seen an answer about this problem yet, but please post back your info.

 

[sympton]

sympton, it's not just you, but it would help if everyone would post what version of FreeNAS they're using when they ask a question like this. Are you using FreeNAS 8.0, 8.01 beta 1/2/3/4? AMD64 or i386?

I've seen this same question asked a lot here lately, try to search some more and add your post to an existing one, you'll have a much better chance at getting an answer instead of people answering the same question in 6 different places, or not answering the 6th one because they already answered 5 other times. I'm not trying to pick on you, this is just for people in general.

Anyway, sorry about that. I haven't seen an answer about this problem yet, but please post back your info.

Yeah sorry about that, i didnt exactly know WHAT to search for so i started this thread ..

Code:

OS Version: 	FreeBSD 8.2-RELEASE-p1
Platform: 	Intel(R) Core(TM)2 Duo CPU E6550 @ 2.33GHz
System Time: 	Sat Aug 20 11:48:27 EEST 2011
Uptime: 	11:48AM up 12 days, 15:16, 1 user
Load Average: 	0.04, 0.02, 0.00
FreeNAS Build: 	FreeNAS-8.0-RELEASE-amd64 

I dont have any raid or such, just 2x2tb plain disks. Anyways, MOVIES disk looks empty again and not browsable but i can see it on the mount list and in df.

Code:

Filesystem          1K-blocks        Used     Avail Capacity  Mounted on
/dev/ufs/FreeNASs1a     468735     415051     16186    96%    /
devfs                        1          1         0   100%    /dev
/dev/md0                  4526       2356      1808    57%    /etc
/dev/md1                   686         10       622     2%    /mnt
/dev/md2                 76526      16560     53844    24%    /var
/dev/ufs/FreeNASs4       20263        632     18010     3%    /data
/dev/ufs/STORAGE    1922813972 1352251976 416736880    76%    /mnt/STORAGE
/dev/ufs/MOVIES     1922813972 1110895028 658093828    63%    /mnt/MOVIES

Code:

freenas# ls /mnt/MOVIES/
freenas#

Code:

Active Volumes: 2
Volume 	Path 	Used 	Available 	Size 	Status 	Available actions
STORAGE 	/mnt/STORAGE 	1.4 TB (78%) 	426.7 GB 	2.0 TB 	ONLINE 	
MOVIES 	/mnt/MOVIES 	1.1 TB (65%) 	673.9 GB 	2.0 TB 	ONLINE 	

HDD is allways on, no acoustic mode, no standby, SMART is on, but it worked fin in freenas7...

Code:

freenas# zpool status
no pools available
freenas#

I dont have any zpools so :) What can be the problem here ? What info do you require ?

-Tomi

 

[sympton]

Now whole disk has gone missing. Maybe its faulty ? In dmesg it says:

Code:

ada0 at ata2 bus 0 scbus1 target 0 lun 0
ada0: <WDC WD20EARS-00MVWB0 51.0AB51> ATA-8 SATA 2.x device
ada0: 150.000MB/s transfers (SATA, UDMA5, PIO 8192bytes)da0 at umass-sim0 bus 0 scbus3 target 0 lun 0
da0: <Kingston DataTraveler 2.0 1.00> Removable Direct Access SCSI-2 device
da0: 40.000MB/s transfers
da0: 3819MB (7823296 512 byte sectors: 255H 63S/T 486C)

ada0: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C)
ada1 at ata2 bus 0 scbus1 target 1 lun 0
ada1: <WDC WD20EARS-00MVWB0 51.0AB51> ATA-8 SATA 2.x device
ada1: 150.000MB/s transfers (SATA, UDMA5, PIO 8192bytes)
ada1: 1907729MB (3907029168 512 byte sectors: 10H 63S/T 16383C)
SMP: AP CPU #1 Launched!
GEOM: da0s1: geometry does not match label (16h,63s != 255h,63s).
(ada1:ata2:0:1:0): lost device
(ada1:ata2:0:1:0): removing device entry

Is there any repair commands ?

 

[ProtoSD]

That's a really bad feeling when a drive disappears like that....
It doesn't come back if you reboot?
What about during POST, does the BIOS see it?
If you can get FreeNAS to see it again, there's the 'fsck' command, but you need to make sure that the drive is not mounted before you use that command.
Since it's a UFS formatted drive, you could try booting with an Ubuntu rescue CD. If Ubuntu recognizes it, you may be able to mount it. I'm not sure if you can run an 'fsck' command on a UFS filesystem in Ubuntu. If you can, that's what I would try to do before trying to mount it. The syntax for mounting a UFS disk in Ubuntu can be a little tricky.

I'd try and get FreeNAS to recognize it again first, make sure to dismount it 'umount /dev/ada1', and then do 'fsck /dev/ada1. Of course if the BIOS doesn't see it, then the drive has probably gone bad...

 

[sympton]

I upgraded and managed to find the disk, but when i try to mount it it says "The selected disks were not verified for this import rules." What does this mean ?

 

[sympton]

Here is something to chew:

Code:

freenas# fdisk /dev/ad5p1
******* Working on device /dev/ad5p1 *******
parameters extracted from in-core disklabel are:
cylinders=3876020 heads=16 sectors/track=63 (1008 blks/cyl)

Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=3876020 heads=16 sectors/track=63 (1008 blks/cyl)

fdisk: invalid fdisk partition table found
Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
    start 63, size 3907028097 (1907728 Meg), flag 80 (active)
        beg: cyl 0/ head 1/ sector 1;
        end: cyl 179/ head 15/ sector 63
The data for partition 2 is:
<UNUSED>
The data for partition 3 is:
<UNUSED>
The data for partition 4 is:
<UNUSED>
freenas# mount /dev/ad5p1 /mnt/test
mount: /dev/ad5p1 : Invalid argument
freenas# mount -t UFS /dev/ad5p1 /mnt/test
mount: /dev/ad5p1 : Operation not supported by device
freenas#

Code:

freenas# fsck -t ufs /dev/ad5p1
** /dev/ad5p1
Cannot find file system superblock
ioctl (GCINFO): Inappropriate ioctl for device
fsck_ufs: /dev/ad5p1: can't read disk label

In some point i managed to actually mount the drive and data was there. But after i tried this through webinterface, it didnt succeed. And now i cannot moun on shell either :/

 

[sympton]

I tried to unmount another disk and then moun the other, and now both cannot be mounted. Both says:

"The selected disks were not verified for this import rules."

Code:

Hostname: 	freenas.local
OS Version: 	FreeBSD 8.2-RELEASE
Platform: 	Intel(R) Core(TM)2 Duo CPU E6550 @ 2.33GHz
System Time: 	Sun Aug 21 21:12:43 EEST 2011
Uptime: 	11:12AM up 3:25, 0 users
Load Average: 	0.00, 0.00, 0.00
FreeNAS Build: 	FreeNAS-8.0-RC5-amd64 

 

[ProtoSD]

FreeNAS Build: FreeNAS-8.0-RC5-amd64

Why are you using 8.0 RC5?

This could be a big part of you problem. Try upgrading to 8.01 beta4.

 

[sympton]

I tried upgrading. The same problem were present in 8.0-release too.

 

[Durkatlon]

Going from 8.0-RELEASE to 8.0-RC5 is actually a downgrade, not an upgrade! Note that RC stands for "Release Candidate". The RC builds came before the final RELEASE build.

Try upgrading to the 8.0.1-BETA4.

 

[sympton]

I will do that. I Know reinstalling solves this problem. Unless it happens again .. Is it possible to downgrade back to 7 ?

 

[sympton]

Code:

Hostname: 	freenas.local
OS Version: 	FreeBSD 8.2-RELEASE-p2
Platform: 	Intel(R) Core(TM)2 Duo CPU E6550 @ 2.33GHz
Memory: 	3303MB
System Time: 	Wed Aug 24 07:12:26 PDT 2011
Uptime: 	7:12AM up 2 mins, 0 users
Load Average: 	0.33, 0.41, 0.19
FreeNAS Build: 	FreeNAS-8.0.1-BETA4-amd64 

Problem remains same ...

 

[sympton]

I installed ubuntu to usb stick and did something i found from web:

Code:

root@Shuttle:/home/tontze# mount -t ufs /dev/sdb1 /mnt/hdd/
mount: wrong fs type, bad option, bad superblock on /dev/sdb1,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so

Code:

root@Shuttle:/home/tontze# dmesg |tail
[ 2226.109977] 
[ 2226.109978] mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ...
[ 2226.109979] 
[ 2226.109980] >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
[ 2226.110285] ufs_read_super: bad magic number
[ 2365.762425] ufs_read_super: bad magic number
[ 2690.677985] UFS-fs: Invalid option: "ufstypbsde=" or missing value
[ 2690.677989] wrong mount options
[ 2703.718417] ufs_read_super: bad magic number
[ 3533.953932] ufs was compiled with read-only support, can't be mounted as read-write

Code:

root@Shuttle:/home/tontze# mount -t ufs -o ro,ufstype=ufs2 /dev/sdb1 /mnt/hdd/
mount: wrong fs type, bad option, bad superblock on /dev/sdb1,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so

Code:

root@Shuttle:/home/tontze# dmesg |tail
[ 2690.677989] wrong mount options
[ 2703.718417] ufs_read_super: bad magic number
[ 3533.953932] ufs was compiled with read-only support, can't be mounted as read-write
[ 3702.421954] You didn't specify the type of your ufs filesystem
[ 3702.421957] 
[ 3702.421958] mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ...
[ 3702.421959] 
[ 3702.421960] >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
[ 3702.422255] ufs_read_super: bad magic number
[ 3774.786402] ufs_read_super: bad magic number

What now ? Whats "bad magic number" ?

 

[ProtoSD]

It means that it's not finding a valid filesystem.

What do you see on Ubuntu if you do 'fdisk -l /dev /dev/sdb' ?
I need to look up the syntax for mount UFS on Ubuntu, I think it's different than you have. I'll update when I find it.

EDIT: Here's how you do it:

mount -r -t ufs -o ufstype=44bsd /dev/sdb /mnt/hdd

 

[sympton]

Code:

root@Shuttle:/home/tontze# fdisk -l /dev /dev/sdb
last_lba(): I don't know how to handle files with mode 40755

WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1      243202  1953514583+  ee  GPT

Code:

root@Shuttle:/home/tontze# mount -r -t ufs -o ufstype=44bsd /dev/sdb /mnt/hdd
mount: wrong fs type, bad option, bad superblock on /dev/sdb,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so

Code:

root@Shuttle:/home/tontze# dmesg |tail
[ 4052.419039] sky2 0000:02:00.0: eth0: Link is down
[ 4076.792052] usb 4-2: USB disconnect, address 2
[41643.800018] usb 2-2: new low speed USB device using uhci_hcd and address 2
[41644.004123] input: Microsft Microsoft Wireless Desktop Receiver 3.1 as /devices/pci0000:00/0000:00:1d.0/usb2/2-2/2-2:1.0/input/input4
[41644.004242] microsoft 0003:045E:00F9.0003: input,hidraw0: USB HID v1.11 Keyboard [Microsft Microsoft Wireless Desktop Receiver 3.1] on usb-0000:00:1d.0-2/input0
[41644.092060] microsoft 0003:045E:00F9.0004: fixing up Microsoft Wireless Receiver Model 1028 report descriptor
[41644.144260] input: Microsft Microsoft Wireless Desktop Receiver 3.1 as /devices/pci0000:00/0000:00:1d.0/usb2/2-2/2-2:1.1/input/input5
[41644.144441] microsoft 0003:045E:00F9.0004: input,hidraw1: USB HID v1.11 Mouse [Microsft Microsoft Wireless Desktop Receiver 3.1] on usb-0000:00:1d.0-2/input1
[41801.997102] sky2 0000:02:00.0: eth0: Link is up at 1000 Mbps, full duplex, flow control both
[41940.136890] ufs_read_super: bad magic number
root@Shuttle:/home/tontze# 

bad magic number again ?

This is what parted said:

Code:

parted) print all                                                        
Model: ATA WDC WD20EARS-00M (scsi)
Disk /dev/sdb: 2000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number  Start   End     Size    File system  Name  Flags
 1      32.8kB  2000GB  2000GB               2


Model: ATA WDC WD20EARS-00M (scsi)
Disk /dev/sda: 2000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number  Start   End     Size    File system  Name  Flags
 1      32.8kB  2000GB  2000GB               1


Model: Verbatim STORE N GO (scsi)
Disk /dev/sdc: 16.0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number  Start   End     Size    Type      File system     Flags
 1      1049kB  12.5GB  12.5GB  primary   ext4            boot
 2      12.5GB  16.0GB  3478MB  extended
 5      12.5GB  16.0GB  3478MB  logical   linux-swap(v1)

 

[ProtoSD]

Use /dev/sdb1

When you did the fdisk -l /dev/sdb the results you got told you what the actual device name of the partition you need to mount was:

Device Boot Start End Blocks Id System
/dev/sdb1 1 243202 1953514583+ ee GPT

That *should* work...

 

[sympton]

Well, it didnt work :/

Code:

root@Shuttle:/home/tontze# mount -r -t ufs -o ufstype=44bsd /dev/sdb1 /mnt/hdd
mount: wrong fs type, bad option, bad superblock on /dev/sdb1,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so

Code:

root@Shuttle:/home/tontze# dmesg |tail
[42601.350508] sky2 0000:02:00.0: eth0: Link is down
[42619.712037] usb 2-2: USB disconnect, address 2
[75777.704021] usb 2-2: new low speed USB device using uhci_hcd and address 3
[75777.984130] input: Microsft Microsoft Wireless Desktop Receiver 3.1 as /devices/pci0000:00/0000:00:1d.0/usb2/2-2/2-2:1.0/input/input6
[75777.984272] microsoft 0003:045E:00F9.0005: input,hidraw0: USB HID v1.11 Keyboard [Microsft Microsoft Wireless Desktop Receiver 3.1] on usb-0000:00:1d.0-2/input0
[75778.071061] microsoft 0003:045E:00F9.0006: fixing up Microsoft Wireless Receiver Model 1028 report descriptor
[75778.123261] input: Microsft Microsoft Wireless Desktop Receiver 3.1 as /devices/pci0000:00/0000:00:1d.0/usb2/2-2/2-2:1.1/input/input7
[75778.123440] microsoft 0003:045E:00F9.0006: input,hidraw1: USB HID v1.11 Mouse [Microsft Microsoft Wireless Desktop Receiver 3.1] on usb-0000:00:1d.0-2/input1
[75785.193881] sky2 0000:02:00.0: eth0: Link is up at 1000 Mbps, full duplex, flow control both
[75835.151315] ufs_read_super: bad magic number
root@Shuttle:/home/tontze# 

Bad magic number again.