External HDDs

[Sicilian]

OK so it doesn't matter how its been formatted when I first plug it in, the box itself will format the drive accordingly. Is that right?

Cheers,
Sonna

Yep should be fine. You may need to reboot your receiver in order for the HDD to recognised.

[sonna]

Thanks mate.

Sonna

[Silent]

Just a heads up, when I bought my Duo and I plugged in an NTFS HDD, it wouldn't boot up. I suppose the difference is with the Duo it's internal, it might be fine via USB.

[sonna]

Just another question sorry.

I've already got a USB stick in the back with bits n pieces on etc. Would I be able to just drag and drop these onto the USB HDD or will I need to use FTP to put these on.

[Rob van der Does]

Just another question sorry.

I've already got a USB stick in the back with bits n pieces on etc. Would I be able to just drag and drop these onto the USB HDD or will I need to use FTP to put these on.

Well, I would say trying this is much faster than asking and awaiting an answer........

[sonna]

Thanks.................

What I meant was am I safe just to do that no matter how the USB HDD is formatted i.e just drag and drop (this particular HDD is in NTFS). Will the box recognise NTFS or does it not matter at all. Don't think I'll be able to format a 500GB drive to FAT32.

Is there a guide available at all. I've tried looking but can't find one.

[Rob van der Does]

1- Drag & Drop (Windows) is safe, but it requires Samba to be installed to work;
2- NTFS is recognised for read only by defaoult. If you also want to write you have to install the NTFS-Utils (they are on the feeds, under ; Drivers');
3- A 500GB drive can be in FAT32, that's not the problem. And it will even be a fast drive, as there's no overhead. But: maximum file size is 4GB, which makes it utterly useless for recording.

[sonna]

Thanks a lot will let you know how I get on.

[sonna]

Hey,

Copied files over ok. Just connected the HDD up and it picked it up fine. Can pause, record, and playback fine no problem.

However, box crashes when a recording is deleted.

Have tried to copy a log but I can't make any sense of it (probably not even the right one). If someone wants to point me in the direction of finding the correct one etc. then please feel free.


SAMSUNG HM500JI PQ: 0 ANSI: 2 CCS
Oct 16 20:36:25 gb800se user.notice kernel: sd 1:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/465 GiB)
Oct 16 20:36:25 gb800se user.notice kernel: sd 1:0:0:0: Attached scsi generic sg0 type 0
Oct 16 20:36:25 gb800se user.warn kernel: scsi: killing requests for dead queue
Oct 16 20:36:25 gb800se user.notice kernel: sd 1:0:0:0: [sda] Write Protect is off
Oct 16 20:36:25 gb800se user.debug kernel: sd 1:0:0:0: [sda] Mode Sense: 28 00 00 00
Oct 16 20:36:25 gb800se user.warn kernel: scsi: killing requests for dead queue
Oct 16 20:36:25 gb800se user.err kernel: sd 1:0:0:0: [sda] No Caching mode page present
Oct 16 20:36:25 gb800se user.err kernel: sd 1:0:0:0: [sda] Assuming drive cache: write through
Oct 16 20:36:25 gb800se user.warn kernel: scsi: killing requests for dead queue
Oct 16 20:36:25 gb800se user.err kernel: sd 1:0:0:0: [sda] No Caching mode page present
Oct 16 20:36:25 gb800se user.err kernel: sd 1:0:0:0: [sda] Assuming drive cache: write through
Oct 16 20:36:25 gb800se user.warn kernel: scsi: killing requests for dead queue
Oct 16 20:36:25 gb800se user.info kernel: sda: sda1
Oct 16 20:36:25 gb800se user.warn kernel: scsi: killing requests for dead queue
Oct 16 20:36:25 gb800se user.warn kernel: scsi: killing requests for dead queue
Oct 16 20:36:25 gb800se user.err kernel: sd 1:0:0:0: [sda] No Caching mode page present
Oct 16 20:36:26 gb800se user.err kernel: sd 1:0:0:0: [sda] Assuming drive cache: write through
Oct 16 20:36:26 gb800se user.notice kernel: sd 1:0:0:0: [sda] Attached SCSI disk
Oct 16 20:36:26 gb800se user.warn kernel: scsi: killing requests for dead queue
Oct 16 20:36:29 gb800se user.warn kernel: UDF-fs: No partition found (1)
Oct 16 20:38:21 gb800se user.err kernel: sd 1:0:0:0: [sda] No Caching mode page present
Oct 16 20:38:21 gb800se user.err kernel: sd 1:0:0:0: [sda] Assuming drive cache: write through
Oct 16 20:38:21 gb800se user.info kernel: sda: unknown partition table
Oct 16 20:38:22 gb800se user.err kernel: sd 1:0:0:0: [sda] No Caching mode page present
Oct 16 20:38:22 gb800se user.err kernel: sd 1:0:0:0: [sda] Assuming drive cache: write through
Oct 16 20:38:22 gb800se user.info kernel: sda: unknown partition table
Oct 16 20:38:22 gb800se user.err kernel: sd 1:0:0:0: [sda] No Caching mode page present
Oct 16 20:38:22 gb800se user.err kernel: sd 1:0:0:0: [sda] Assuming drive cache: write through
Oct 16 20:38:22 gb800se user.info kernel: sda: sda1
Oct 16 20:38:49 gb800se user.err kernel: sd 1:0:0:0: [sda] No Caching mode page present
Oct 16 20:38:49 gb800se user.err kernel: sd 1:0:0:0: [sda] Assuming drive cache: write through
Oct 16 20:38:49 gb800se user.info kernel: sda: sda1
Oct 16 20:38:50 gb800se user.info kernel: EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
Oct 16 20:47:37 gb800se daemon.debug CCcam: EMM: not interested in 0960:000000
Oct 16 20:47:37 gb800se daemon.debug CCcam: EMM: not interested in 0961:000000
Oct 16 20:48:38 gb800se daemon.debug CCcam: EMM: not interested in 0960:000000
Oct 16 20:48:38 gb800se daemon.debug CCcam: EMM: not interested in 0961:000000