Hello,

I've been a Mythtv user since late 2005, previously Mythdora and the last year or so I've been using Linhes 7.3.

I really like Linhes, it is very well done.

I've been building a Linhes 8.0 Mythbox for a friend of mine. He has two 1 Terabyte drives in his machine so after the initial install I run the add_storage script to format and mount the second drive. It gets mounted and Mythtv sees it just fine to begin with. But after a reboot or two only the first drive is listed in Information Center: System Status: Machine Status.

When I run add_storage again it says that the drive is already mounted. Same thing if I type "sudo mount /dev/sdb"; already mounted.

I do not have this problem with Linhes 7.4, both drives are always listed in Machine Status. I was going to give him 7.4, but I couldn't get Mythwelcome to reliably start the machine up at the scheduled time to record anything. I spent the whole day yesterday trying to get Linhes 7.4 to wake up and record with no luck. I tried everything I could find here and with Google.

Linhes 8.0 wakes up, records, and shuts down perfectly every time.

So, the question is; is that drive really there and available to Mythtv? or If not, how do I make it show up on every boot?

Thank You,
Paul

Hello

I would check /etc/fstab and check out the mounts for the two drives. If you run you should be able to see the uuid for both drives. Make sure that info is correct.

Here is the output from blkid:

> blkid
/dev/sdb1: UUID="aebd398e-2e97-409d-a1a1-ea1d080bdf62" TYPE="xfs" PARTUUID="569e4455-2f3c-49d9-b1ac-2c1304cc8649"
/dev/sda1: UUID="5644259b-2bc3-46ce-89a5-97d1be86673f" TYPE="ext3"
/dev/sda2: UUID="4a43ed5f-1ee8-40de-9434-e08a7fddc725" TYPE="swap"
/dev/sda5: UUID="41605199-d2d1-41bf-b544-0cf0b0dccc13" TYPE="ext3"
/dev/sda6: UUID="059b4c76-fb05-476a-8d5f-d94ea7c264d6" TYPE="ext3"
/dev/sda7: UUID="70ddf6bf-b2ef-4f39-af81-f623269c9952" TYPE="xfs"

And here is the output from lsblk -f:

> lsblk -f
NAME FSTYPE LABEL UUID MOUNTPOINT
sda
|-sda1 ext3 5644259b-2bc3-46ce-89a5-97d1be86673f /
|-sda2 swap 4a43ed5f-1ee8-40de-9434-e08a7fddc725 [SWAP]
|-sda3
|-sda5 ext3 41605199-d2d1-41bf-b544-0cf0b0dccc13 /home
|-sda6 ext3 059b4c76-fb05-476a-8d5f-d94ea7c264d6 /data/srv/mysql
`-sda7 xfs 70ddf6bf-b2ef-4f39-af81-f623269c9952 /data/storage/WDCWD10EA
sdb
`-sdb1 xfs aebd398e-2e97-409d-a1a1-ea1d080bdf62 /data/storage/WDCWD10EZ
sr0


They both seem a little jumbled to me, but I'm no expert.



The fstab itself looks like it's run together at the bottom:

# <file system> <dir> <type> <options> <dump> <pass>

devpts /dev/pts devpts defaults 0 0

shm /dev/shm tmpfs nodev,nosuid 0 0

/dev/sr0 /media/cdrom auto ro,user,noauto,unhide 0 0

UUID=5644259b-2bc3-46ce-89a5-97d1be86673f / ext3 defaults,noatime,acl 0 1

UUID=70ddf6bf-b2ef-4f39-af81-f623269c9952 /data/storage/disk0 xfs defaults,noatime 0 1

UUID=41605199-d2d1-41bf-b544-0cf0b0dccc13 /home ext3 defaults,noatime,acl 0 1

UUID=059b4c76-fb05-476a-8d5f-d94ea7c264d6 /data/srv/mysql ext3 defaults,noatime,acl 0 1

UUID=4a43ed5f-1ee8-40de-9434-e08a7fddc725 swap swap defaults 0 0

/data/storage/disk0 /data/storage/WDCWD10EARS-00Z5B1_WD-WCAVU0495310 none rw,bind 0 0
UUID=aebd398e-2e97-409d-a1a1-ea1d080bdf62 /data/storage/WDCWD10EZRX-00A8LB0_WD-WMC1U9070727 auto defaults,noatime 0 1
#STARTSCRUB --------------anything in this block will be scrubbed
#ENDSCRUB

Does this need to be cleaned up? The file "fstab.backup.pre_acl" is neater looking and has each UUID on it's own line, but it is also from before I ran add_storage.pyl; hence the "backup" in the name.

Thanks for any insight you can give,
Paul

The whole point of



Is to get the UUID numbers for your FSTAB

That PARTUUID statement is strange ... old way get rid of it

On the good side the numbers for UUID look fine

but the FSTAB for drive sdb1 should be



Also if you muck up FSTAB it will hang when you reboot be careful and ask questions before you do this

Well, I cleaned up the Fstab to look neater, but it didn't make any difference.

Linux would still think the drive was already mounted when I issued the "mount /dev/sdb" command, but Mythtv
wouldn't see the drive.

The two drives I had installed were 1 Terabyte Western Digital Greens, Models WD10EARS and WD10EZRX.

Maybe there's something in Linhes 8 that gets confused with two almost identical drives installed. Having both drives installed in Linhes 7.4 isn't a problem though.

I added a different second drive, a Seagate 1.5 terabyte and it survives rebooting just fine.

My friend will be getting 2.5 terabytes of storage in his Mythbox now instead of 2.0, but I'd still like the to figure this out in case
he wants to add more drives in the future.

Thanks again,
Paul

Awww, crap. I spoke too soon.

After about 10 reboots the 1.5 Terabyte Seagate is no longer available to Mythtv.

But, I went back and tried my hand at editing the Fstab again and this time I got it right.

Thank you RacerX!

I'm curious why it can be rebooted several times before it no longer functions properly.

Sincerely,
Paul